Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFT] ARM: dts: silk: Enable UHS-I SDR-50
Date: Tue, 18 Apr 2017 16:31:28 +0900	[thread overview]
Message-ID: <20170418073127.GC16340@verge.net.au> (raw)
In-Reply-To: <CAMuHMdV_L_Fpm0=WQkHgVn123G4X+cUSxECqw4yi3TYvdSSGCA@mail.gmail.com>

On Tue, Apr 18, 2017 at 09:22:24AM +0200, Geert Uytterhoeven wrote:
> On Tue, Apr 18, 2017 at 7:27 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > Add the "1v8" pinctrl state and sd-uhs-sdr50 property to SDHI1.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> > ---
> > * Compile tested only; no access to silk board
> > ---
> >  arch/arm/boot/dts/r8a7794-silk.dts | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/r8a7794-silk.dts b/arch/arm/boot/dts/r8a7794-silk.dts
> > index 4cb5278d104d..b0ef8ea75c29 100644
> > --- a/arch/arm/boot/dts/r8a7794-silk.dts
> > +++ b/arch/arm/boot/dts/r8a7794-silk.dts
> > @@ -226,6 +226,13 @@
> >         du1_pins: du1 {
> >                 groups = "du1_rgb666", "du1_sync", "du1_disp", "du1_clk0_out";
> >                 function = "du1";
> > +               power-source = <3300>;
> > +       };
> > +
> > +       sdhi1_pins_uhs: sd1_uhs {
> > +               groups = "sdhi1_data4", "sdhi1_ctrl";
> > +               function = "sdhi1";
> > +               power-source = <1800>;
> 
> Shouldn't this be inserted right after the existing sdhi1_pins?
> Yes, the list is only partially sorted.

Oh wow, I messed that up completely.
Let me post a v2.

      reply	other threads:[~2017-04-18  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  5:27 [PATCH/RFT] ARM: dts: silk: Enable UHS-I SDR-50 Simon Horman
2017-04-18  7:22 ` Geert Uytterhoeven
2017-04-18  7:31   ` Simon Horman [this message]

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=20170418073127.GC16340@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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