From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] sdhci-fujitsu: add support for setting the CMD_DAT_DELAY attribute
Date: Thu, 2 Nov 2017 10:49:42 +0000 [thread overview]
Message-ID: <CAKv+Gu8nd7i+iaL-B55WbutGrOKaCsCdrQtFZgFs1TJaSqx-xw@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFpaKdvnwL98UZKzNmR+yXtWJL6hPDPfTXtY8nqmDRsomQ@mail.gmail.com>
On 2 November 2017 at 10:48, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On 2 November 2017 at 01:12, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> On 2 November 2017 at 00:08, Rob Herring <robh@kernel.org> wrote:
>>> On Wed, Nov 01, 2017 at 12:21:32AM +0000, Ard Biesheuvel wrote:
>>>> The Socionext SynQuacer SoC inherits this IP from Fujitsu, but
>>>> requires the F_SDH30_CMD_DAT_DELAY bit to be set in the
>>>> F_SDH30_ESD_CONTROL control register.
>>>>
>>>> So let's add an optional property to this device's binding, and
>>>> set the attribute if it is present in the DT node.
>>>>
>>>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>>> ---
>>>> Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt | 2 ++
>>>> drivers/mmc/host/sdhci_f_sdh30.c | 18 +++++++++++++++++-
>>>> 2 files changed, 19 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt b/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt
>>>> index de2c53cff4f1..9ad02f743ad0 100644
>>>> --- a/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt
>>>> +++ b/Documentation/devicetree/bindings/mmc/sdhci-fujitsu.txt
>>>> @@ -15,6 +15,8 @@ Required properties:
>>>> Optional properties:
>>>> - vqmmc-supply: phandle to the regulator device tree node, mentioned
>>>> as the VCCQ/VDD_IO supply in the eMMC/SD specs.
>>>> +- cmd-dat-delay-select: boolean property indicating that this host requires
>>>> + the CMD_DAT_DELAY control to be enabled.
>>>
>>> Needs a vendor prefix unless this is a standard SDHCI bit (in which
>>> case it should be documented in a common spot).
>>>
>>
>> I suspect this is a non-standard thing, so I'll add the fujitsu prefix. Ulf?
>
> This is specific to the Fujitsu variant.
>
> However, what puzzles me is why this bit is needed for the Socionext
> SynQuacer SoC, but not for other SoCs that uses this IP. That seems
> weird (probably wrong).
>
> Moreover, the F_SDH30_CMD_DAT_DELAY register define is already there,
> so I would rather suspect that it's something that did got fully
> implemented. In other words, I don't think you need a new DT binding,
> but rather try to implement it generically for the sdhci-f_sdh30
> driver. Do you think that will work?
>
Do you mean set it unconditionally? That works for me, but I have no
way of testing whether it still works on other SoCs that use this IP.
next prev parent reply other threads:[~2017-11-02 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 0:21 [PATCH] sdhci-fujitsu: add support for setting the CMD_DAT_DELAY attribute Ard Biesheuvel
[not found] ` <20171101002132.13500-1-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-11-02 0:08 ` Rob Herring
2017-11-02 0:12 ` Ard Biesheuvel
[not found] ` <CAKv+Gu8UPpsobJ_d4+OCdufSkLLhGdRFxPO92X3YKvnyBY5b7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-02 10:48 ` Ulf Hansson
2017-11-02 10:49 ` Ard Biesheuvel [this message]
[not found] ` <CAKv+Gu8nd7i+iaL-B55WbutGrOKaCsCdrQtFZgFs1TJaSqx-xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-02 11:00 ` Ulf Hansson
[not found] ` <CAPDyKFpKe-TaUeuWdenGf9tHV8+UkGkkdcp8Z+Yu9Q-haHsYsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-03 3:29 ` Vincent Yang
[not found] ` <CAKR0VNJ0xzRebUEZprRfQVp1LGjPG4khyumSYKsRtxCPTGkxYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-06 2:54 ` Vincent Yang
2017-11-06 7:17 ` Ulf Hansson
2017-11-06 10:46 ` Ard Biesheuvel
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=CAKv+Gu8nd7i+iaL-B55WbutGrOKaCsCdrQtFZgFs1TJaSqx-xw@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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).