devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhangfei <zhangfei.gao@linaro.org>
To: Jaehoon Chung <jh80.chung@samsung.com>, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] Document: dw_mmc-k3: add document of hi6220 mmc
Date: Tue, 12 May 2015 15:59:35 +0800	[thread overview]
Message-ID: <5551B2E7.4030306@linaro.org> (raw)
In-Reply-To: <5551AD7E.2050200@samsung.com>



On 05/12/2015 03:36 PM, Jaehoon Chung wrote:
> Hi, Zhangfei.
>
> On 05/07/2015 04:56 PM, Zhangfei Gao wrote:
>> Add bindings for hi6220 mmc support
>>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> ---
>>   .../devicetree/bindings/mmc/k3-dw-mshc.txt         | 28 ++++++++++++++++++++++
>>   1 file changed, 28 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt
>> index 3b35449..df37058 100644
>> --- a/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt
>> +++ b/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt
>> @@ -13,6 +13,10 @@ Required Properties:
>>
>>   * compatible: should be one of the following.
>>     - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
>> +  - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
>> +
>> +Optional Properties:
>> +- hisilicon,peripheral-syscon: phandle of syscon used to control peripheral.
>>
> I'm not sure..
> but i think this patch could be added just the compatible and optional properties descriptions.
> If SoC will be added, it need not to add every example, doesn't it?
>
> how about removing the below example? This is just my opinion. :)
> If there is a special reason that add example...let me know, plz.

I am adding this example just for two reasons

1. There is still some components need to be upstreamed before we add to 
dts, like pinctrl and regulator, which still need some time.
So add here for quick reference after the component is enabled.
Had experience before that hip04_eth is merged but dts is delayed, 
thanks to the document, we can add it quickly.

2. sd has some special requirement of "hisilicon,peripheral-syscon", 
which used for controlling voltage


What do you think?

Thanks

  reply	other threads:[~2015-05-12  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  7:56 [PATCH v2 0/3] dw_mmc-k3 support hi6220 Zhangfei Gao
2015-05-07  7:56 ` [PATCH v2 1/3] Document: dw_mmc-k3: add document of hi6220 mmc Zhangfei Gao
2015-05-12  7:36   ` Jaehoon Chung
2015-05-12  7:59     ` zhangfei [this message]
2015-05-13 22:17       ` Jaehoon Chung
2015-05-07  7:56 ` [PATCH v2 2/3] mmc: dw_mmc: add switch_voltage Zhangfei Gao
     [not found] ` <1430985401-12202-1-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-05-07  7:56   ` [PATCH v2 3/3] mmc: dw_mmc: k3: support hi6220 Zhangfei Gao
2015-05-13 22:17     ` Jaehoon Chung
2015-05-14  5:52       ` zhangfei

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=5551B2E7.4030306@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.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).