From: Lucas Stach <l.stach@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] mci: arasan: fix build for non-ZynqMP
Date: Tue, 02 Apr 2024 10:43:24 +0200 [thread overview]
Message-ID: <f72418fa68eb9f944c2cea7ba5e8380417fec790.camel@pengutronix.de> (raw)
In-Reply-To: <ZgvCyRqmMUwfMbl2@pengutronix.de>
Am Dienstag, dem 02.04.2024 um 10:33 +0200 schrieb Sascha Hauer:
> On Tue, Mar 26, 2024 at 01:34:49PM +0100, Sascha Hauer wrote:
> > On Tue, Mar 26, 2024 at 12:50:42PM +0100, Steffen Trumtrar wrote:
> > > Registering sdclk only makes sense on the ZynqMP architecture. Guard
> > > calling the function with a IS_ENABLED()
> > >
> > > Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> > > ---
> > > drivers/mci/arasan-sdhci.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/mci/arasan-sdhci.c b/drivers/mci/arasan-sdhci.c
> > > index f01396d7ee..b7dd98049f 100644
> > > --- a/drivers/mci/arasan-sdhci.c
> > > +++ b/drivers/mci/arasan-sdhci.c
> > > @@ -772,7 +772,8 @@ static int arasan_sdhci_probe(struct device *dev)
> > >
> > > mci->f_min = 50000000 / 256;
> > >
> > > - arasan_sdhci_register_sdclk(&arasan_sdhci->clk_data, clk_xin, dev);
> > > + if (IS_ENABLED(CONFIG_ARCH_ZYNQMP))
> > > + arasan_sdhci_register_sdclk(&arasan_sdhci->clk_data, clk_xin, dev);
> >
> > CONFIG_ARCH_ZYNQMP being enabled doesn't necessarily mean the code
> > actually runs on Zynqmp. Does this need a runtime check for other
> > architectures?
>
> The arasan MMC driver is currently only used on ZynqMP, so it's OK for
> now.
>
That's not true. The driver is also used on the Zynq7000.
Regards,
Lucas
> In Linux the driver the ZynqMP specifics are only used with the "xlnx,zynqmp-8.9a"
> compatible whereas our driver binds to the "arasan,sdhci-8.9a"
> compatible. This makes it more clear that this is really a ZynqMP
> specific path that is taken here.
>
> Sascha
>
next prev parent reply other threads:[~2024-04-02 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 11:50 [PATCH 0/2] mci: fix warning and linker error Steffen Trumtrar
2024-03-26 11:50 ` [PATCH 1/2] mci: mci-core: fix mci_switch_status call Steffen Trumtrar
2024-03-26 11:50 ` [PATCH 2/2] mci: arasan: fix build for non-ZynqMP Steffen Trumtrar
2024-03-26 12:34 ` Sascha Hauer
2024-04-02 8:33 ` Sascha Hauer
2024-04-02 8:43 ` Lucas Stach [this message]
2024-04-02 8:59 ` Sascha Hauer
2024-04-02 8:20 ` [PATCH 0/2] mci: fix warning and linker error Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f72418fa68eb9f944c2cea7ba5e8380417fec790.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=s.trumtrar@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox