From: Ulf Hansson <firstname.lastname@example.org> To: Rob Herring <email@example.com> Cc: Jaehoon Chung <firstname.lastname@example.org>, Shawn Lin <email@example.com>, linux-mmc <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Doug Anderson <email@example.com>, "open list:ARM/Rockchip SoC..." <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps Date: Wed, 22 Jun 2016 14:30:22 +0200 [thread overview] Message-ID: <CAPDyKFquaUOUM+8UYBZhq=t0n6+v+cbTy8FotjYyysi6EGHx3A@mail.gmail.com> (raw) In-Reply-To: <20160608204848.GA3368@rob-hp-laptop> On 8 June 2016 at 22:48, Rob Herring <email@example.com> wrote: > 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. > According to patch4, this is a description of the mmc controller, perhaps together with some limitations as per SoC/platform and thus has nothing to do with the card. I have seen several drivers, which needs to validate every single piece of command to avoid execute those it cannot support. So, I personally thinks these new DT bindings would be nice to add. Kind regards Uffe
next prev parent reply other threads:[~2016-06-22 12:30 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 2016-06-22 12:30 ` Ulf Hansson [this message] 2016-06-22 15:06 ` Doug Anderson 2016-06-23 1:29 ` Shawn Lin 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='CAPDyKFquaUOUM+8UYBZhq=t0n6+v+cbTy8FotjYyysi6EGHx3A@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps' \ /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
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).