From: Shawn Lin <shawn.lin@rock-chips.com>
To: Jaehoon Chung <jh80.chung@samsung.com>,
Jun Nie <jun.nie@linaro.org>,
shawn.guo@linaro.org, xie.baoyou@zte.com.cn
Cc: shawn.lin@rock-chips.com, ulf.hansson@linaro.org,
jason.liu@linaro.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH 3/5] Documentation: synopsys-dw-mshc: add binding for fifo quirks
Date: Tue, 25 Oct 2016 12:17:59 +0800 [thread overview]
Message-ID: <c7fea328-45a9-77cd-39a5-37681ea2bc7a@rock-chips.com> (raw)
In-Reply-To: <39dbfa10-03fc-0f8b-c947-0f8da5dae60b@samsung.com>
On 2016/10/25 10:16, Jaehoon Chung wrote:
> On 10/24/2016 09:19 PM, Shawn Lin wrote:
>> On 2016/10/24 17:11, Jun Nie wrote:
>>> Add fifo-addr-override property and fifo-watermark-quirk property to
>>> synopsys-dw-mshc bindings. It is intended to provide workarounds to
>>> support more SoCs that break current assumption.
>>>
>>> See Documentation/devicetree/bindings/reset/reset.txt for details.
>>>
>>> Signed-off-by: Jun Nie <jun.nie@linaro.org>
>>> ---
>>> Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt | 13 +++++++++++++
>>> 1 file changed, 13 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
>>> index 4e00e85..eb64921 100644
>>> --- a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
>>> +++ b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt
>>> @@ -76,6 +76,17 @@ Optional properties:
>>>
>>> * broken-cd: as documented in mmc core bindings.
>>>
>>> +* fifo-addr-override: Override fifo address with value provided by DT. The FIFO
>>> + reg offset of version 0x210A break current assumption that 0x100 (version < 0x240A)
>>> + and 0x200(version >= 0x240A) in some implementation. So this property serves as
>>> + workaround.
>>
>> Can we hardcode this to the code by checking the host version?
>
> I think it should be not workaround..According to TRM, Address is equal or greater than 0x100.
> It means address can be 0x200, right?
> If you needs to overwrite the DATA register offset for your target, just can add the property for this.
>
I can't follow yours here as I don't have 210A TRM. Do you mean the TRM
for 210A say: "Address is equal or greater than 0x100" ?
>>
>>> +
>>> +* fifo-watermark-quirk: Data done irq is expected if data length is less than
>>> + watermark in PIO mode. But fifo watermark is requested to be aligned with data
>>> + length in some SoC so that TX/RX irq can be generated with data done irq. Add the
>>> + watermark quirk to mark this requirement and force fifo watermark setting
>>> + accordingly.
>>
>> I would like to know if this limitation is *really* related to some
>> Socs or the version of 210A dw_mmc?
>>
>>
>>> +
>>> * vmmc-supply: The phandle to the regulator to use for vmmc. If this is
>>> specified we'll defer probe until we can find this regulator.
>>>
>>> @@ -103,6 +114,8 @@ board specific portions as listed below.
>>> interrupts = <0 75 0>;
>>> #address-cells = <1>;
>>> #size-cells = <0>;
>>> + fifo-addr-override = <0x200>;
>>> + fifo-watermark-quirk;
>>> };
>>>
>>> [board specific internal DMA resources]
>>>
>>
>>
>
>
>
>
--
Best Regards
Shawn Lin
next prev parent reply other threads:[~2016-10-25 4:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 9:11 [PATCH 0/5] Add intial support to DW MMC host on ZTE SoC Jun Nie
2016-10-24 9:11 ` [PATCH 1/5] mmc: dt-bindings: add ZTE MMC bindings Jun Nie
2016-10-24 9:11 ` [PATCH 2/5] mmc: zx: Initial support for ZX mmc controller Jun Nie
2016-10-24 12:29 ` Shawn Lin
2016-10-25 8:29 ` Jun Nie
2016-10-24 9:11 ` [PATCH 3/5] Documentation: synopsys-dw-mshc: add binding for fifo quirks Jun Nie
2016-10-24 12:19 ` Shawn Lin
2016-10-25 2:16 ` Jaehoon Chung
2016-10-25 4:17 ` Shawn Lin [this message]
2016-10-25 8:09 ` Jaehoon Chung
2016-10-25 8:33 ` Jun Nie
2016-10-24 9:11 ` [PATCH 4/5] mmc: dw: Add fifo address override property Jun Nie
2016-10-24 9:11 ` [PATCH 5/5] mmc: dw: Add fifo watermark quirk Jun Nie
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=c7fea328-45a9-77cd-39a5-37681ea2bc7a@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jason.liu@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=jun.nie@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=xie.baoyou@zte.com.cn \
/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