From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] mmc: sdhci-of-aspeed: Expose data sample phase delay tuning
Date: Fri, 11 Sep 2020 03:33:56 +0000 [thread overview]
Message-ID: <CACPK8XemZ2YG+nFBwy7sDoo8==YvnVYxt+1mx8QfBCxotG7K6g@mail.gmail.com> (raw)
In-Reply-To: <57d48d7a-7cea-4be7-92bd-8f3b93f84a06@www.fastmail.com>
On Fri, 11 Sep 2020 at 02:49, Andrew Jeffery <andrew@aj.id.au> wrote:
>
>
>
> On Fri, 11 Sep 2020, at 11:32, Joel Stanley wrote:
> > On Thu, 10 Sep 2020 at 10:55, Andrew Jeffery <andrew@aj.id.au> wrote:
> > >
> > > Allow sample phase adjustment to deal with layout or tolerance issues.
> > >
> > > Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
> > > ---
> > > drivers/mmc/host/sdhci-of-aspeed.c | 137 +++++++++++++++++++++++++++--
> > > 1 file changed, 132 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/mmc/host/sdhci-of-aspeed.c b/drivers/mmc/host/sdhci-of-aspeed.c
> > > index 4f008ba3280e..641accbfcde4 100644
> > > --- a/drivers/mmc/host/sdhci-of-aspeed.c
> > > +++ b/drivers/mmc/host/sdhci-of-aspeed.c
> > > +static void
> > > +aspeed_sdc_configure_phase(struct aspeed_sdc *sdc,
> > > + const struct aspeed_sdhci_phase_desc *phase,
> > > + uint8_t value, bool enable)
> > > +{
> > > + u32 reg;
> > > +
> > > + spin_lock(&sdc->lock);
> >
> > What is the lock protecting against?
> >
> > We call this in the ->probe, so there should be no concurrent access going on.
>
> Because the register is in the "global" part of the SD/MMC controller address
> space (it's not part of the SDHCI), and there are multiple slots that may have
> a driver probed concurrently.
That points to having the property be part of the "global" device tree
node. This would simplify the code; you wouldn't need the locking
either.
>
> >
> >
> > > + reg = readl(sdc->regs + ASPEED_SDC_PHASE);
> > > + reg &= ~phase->enable_mask;
> > > + if (enable) {
> > > + reg &= ~phase->value_mask;
> > > + reg |= value << __ffs(phase->value_mask);
> > > + reg |= phase->enable_value << __ffs(phase->enable_mask);
> > > + }
> > > + writel(reg, sdc->regs + ASPEED_SDC_PHASE);
> > > + spin_unlock(&sdc->lock);
> > > +}
> > > +
> > > static void aspeed_sdhci_set_clock(struct sdhci_host *host, unsigned int clock)
> > > {
> > > struct sdhci_pltfm_host *pltfm_host;
> > > @@ -155,8 +195,58 @@ static inline int aspeed_sdhci_calculate_slot(struct aspeed_sdhci *dev,
> > > return (delta / 0x100) - 1;
> > > }
> > >
> > > +static int aspeed_sdhci_configure_of(struct platform_device *pdev,
> > > + struct aspeed_sdhci *sdhci)
> > > +{
> > > + u32 iphase, ophase;
> > > + struct device_node *np;
> > > + struct device *dev;
> > > + int ret;
> > > +
> > > + if (!sdhci->phase)
> > > + return 0;
> > > +
> > > + dev = &pdev->dev;
> > > + np = dev->of_node;
> > > +
> > > + ret = of_property_read_u32(np, "aspeed,input-phase", &iphase);
> > > + if (ret < 0) {
> > > + aspeed_sdc_configure_phase(sdhci->parent, &sdhci->phase->in, 0,
> > > + false);
> >
> > Will this clear any value that eg. u-boot writes?
>
> No, see the 'enable' test in aspeed_sdc_configure_phase()
OK, so this branch will never cause any change in the register? Best
to drop it then.
>
> >
> > The register should be left alone if the kernel doesn't have a
> > configuration of it's own, otherwise we may end up breaking an
> > otherwise working system.
>
> Right, I can rework that.
next prev parent reply other threads:[~2020-09-11 3:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 10:54 [PATCH 0/3] mmc: sdhci-of-aspeed: Expose data sample phase delay tuning Andrew Jeffery
2020-09-10 10:54 ` [PATCH 1/3] dt: bindings: mmc: Add phase control properties for the Aspeed SDHCI Andrew Jeffery
2020-09-14 9:41 ` Ulf Hansson
2020-09-15 0:43 ` Andrew Jeffery
2020-09-10 10:54 ` [PATCH 2/3] mmc: sdhci-of-aspeed: Expose data sample phase delay tuning Andrew Jeffery
2020-09-11 2:02 ` Joel Stanley
2020-09-11 2:49 ` Andrew Jeffery
2020-09-11 3:33 ` Joel Stanley [this message]
2020-09-11 3:53 ` Andrew Jeffery
2020-09-10 10:54 ` [PATCH 3/3] ARM: dts: tacoma: Add data sample phase delay for eMMC Andrew Jeffery
2020-09-11 2:03 ` Joel Stanley
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='CACPK8XemZ2YG+nFBwy7sDoo8==YvnVYxt+1mx8QfBCxotG7K6g@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=adrian.hunter@intel.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).