From: Rob Herring <robh@kernel.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps
Date: Wed, 8 Jun 2016 15:48:48 -0500 [thread overview]
Message-ID: <20160608204848.GA3368@rob-hp-laptop> (raw)
In-Reply-To: <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com>
On Wed, Jun 08, 2016 at 04:20:21PM +0800, Shawn Lin wrote:
> Let's add some basic description for cap-no-sdio,
> cap-no-sd and cap-no-mmc.
This doesn't say why.
If you know what is there, then there's a better way to do this. Look at
the child nodes because chances are if you have something soldered down
like SDIO or eMMC, then you have a child node already for resets,
regulators, etc.
Rob
next prev parent reply other threads:[~2016-06-08 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 8:19 [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence Shawn Lin
2016-06-08 8:20 ` [RFC PATCH 1/4] Documentation: mmc: add description for new caps Shawn Lin
2016-06-08 20:48 ` Rob Herring [this message]
2016-06-22 12:30 ` Ulf Hansson
[not found] ` <1465374021-2526-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-22 15:06 ` Doug Anderson
[not found] ` <CAD=FV=WNaTEDyVNyteLq3O-BL9KxR49W=44jbXogKXd2dkDWDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-23 1:29 ` Shawn Lin
[not found] ` <b479bc81-f72f-b4c0-b9eb-c8fc4dd71fbb-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-23 4:33 ` Doug Anderson
2016-06-08 8:20 ` [RFC PATCH 2/4] mmc: core: expose MMC_CAP2_NO_SDIO to dt-binding Shawn Lin
2016-06-08 8:20 ` [RFC PATCH 3/4] mmc: core: add cap-no-sd and cap-no-mmc properties Shawn Lin
2016-06-08 8:22 ` [RFC PATCH 4/4] mmc: core: improve initialization flow Shawn Lin
2016-06-22 12:37 ` [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence Ulf Hansson
2016-06-23 1:35 ` Shawn Lin
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=20160608204848.GA3368@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.com \
--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