From: Simon Horman <horms@verge.net.au>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: r7s72100: add power-domains to mmcif
Date: Wed, 25 Jan 2017 11:31:35 +0100 [thread overview]
Message-ID: <20170125103134.GC14751@verge.net.au> (raw)
In-Reply-To: <SG2PR06MB1165BD8C33491336E74AFE5A8A750@SG2PR06MB1165.apcprd06.prod.outlook.com>
On Tue, Jan 24, 2017 at 04:32:30PM +0000, Chris Brandt wrote:
> On Tuesday, January 24, 2017, Simon Horman wrote:
> > On Mon, Jan 23, 2017 at 04:12:16PM +0100, Geert Uytterhoeven wrote:
> > > On Mon, Jan 23, 2017 at 3:13 PM, Chris Brandt <chris.brandt@renesas.com>
> > wrote:
> > > > Signed-off-by: Chris Brandt <chris.brandt@renesas.com>
> > >
> > > Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > Should this be queued up as a fix for v4.10 with the following tag?
> >
> > Fixes: 887862227ba3 ("ARM: dts: r7s72100: add mmcif to device tree")
>
> I assume it can. I'm not sure how it effect the driver one way good or bad
> (that's a question for Geert I think).
> SDHI for r7s72100 needs it too, I just didn't send that yet because my other
> fix will cause a merge conflict because it is modifying the same line. But,
> that patch is taking longer than I expected.
>
> My guess is that power-domains is for runtime power management...which seems
> to be a sore subject for r7s72100 at this point.
Geert tells me that this should not have a runtime effect.
Accordingly, I will queued it up for v4.11.
prev parent reply other threads:[~2017-01-25 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 14:13 [PATCH] ARM: dts: r7s72100: add power-domains to mmcif Chris Brandt
2017-01-23 15:12 ` Geert Uytterhoeven
[not found] ` <CAMuHMdULpxoNaTUX2Dc7R=d+FUb_V45H9=XXfsW3RKBTowE4Uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-24 12:33 ` Simon Horman
[not found] ` <20170124123304.GC20529-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-01-24 16:32 ` Chris Brandt
2017-01-25 10: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=20170125103134.GC14751@verge.net.au \
--to=horms@verge.net.au \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).