From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: Use shmobile_init_late() on r8a7740
Date: Fri, 16 May 2014 04:45:52 +0000 [thread overview]
Message-ID: <20140516044548.GA7185@verge.net.au> (raw)
In-Reply-To: <CANqRtoSKosY3HLc-Hgbf2_ToDeL71QzqamWEd97xX9iaD=2oUQ@mail.gmail.com>
On Fri, May 16, 2014 at 01:39:11PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Fri, May 16, 2014 at 1:08 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, May 13, 2014 at 05:10:20PM +0900, Simon Horman wrote:
> >> On Mon, May 12, 2014 at 09:42:15AM +0200, Geert Uytterhoeven wrote:
> >> > On Mon, May 12, 2014 at 1:10 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> > > From: Magnus Damm <damm+renesas@opensource.se>
> >> > >
> >> > > Hook up ->init_late for r8a7740 to initialize Suspend-to-RAM
> >> > > and CPUIdle in case of C-code less board support for r8a7740.
> >> > >
> >> > > Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> >> >
> >> > Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> >>
> >> Thanks, I will queue this up.
> >
> > Hi Magnus, Hi Geert,
> >
> > As I am currently doing some work for the r8a7779
> > I am wondering if a change like this one is appropriate for that SoC.
> > If so I'll cook one up.
>
> Yes, we want all SoCs to be converted over. Please take care that some
> DTS change may be needed to specify maximum frequency, so this may
> require a DTB update for the user. Which makes it less nice user
> experience for legacy code - if we care about that at this point. But
> legacy code also often tends to use early devices and other stuff, so
> this probably affects DT SoC code and DT reference board code mostly.
Does CPU frequency affect this patch (shmobile_init_late) as
well as the ones to use shmobile_init_delay?
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: Use shmobile_init_late() on r8a7740
Date: Fri, 16 May 2014 13:45:52 +0900 [thread overview]
Message-ID: <20140516044548.GA7185@verge.net.au> (raw)
In-Reply-To: <CANqRtoSKosY3HLc-Hgbf2_ToDeL71QzqamWEd97xX9iaD=2oUQ@mail.gmail.com>
On Fri, May 16, 2014 at 01:39:11PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Fri, May 16, 2014 at 1:08 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, May 13, 2014 at 05:10:20PM +0900, Simon Horman wrote:
> >> On Mon, May 12, 2014 at 09:42:15AM +0200, Geert Uytterhoeven wrote:
> >> > On Mon, May 12, 2014 at 1:10 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> > > From: Magnus Damm <damm+renesas@opensource.se>
> >> > >
> >> > > Hook up ->init_late for r8a7740 to initialize Suspend-to-RAM
> >> > > and CPUIdle in case of C-code less board support for r8a7740.
> >> > >
> >> > > Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> >> >
> >> > Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> >>
> >> Thanks, I will queue this up.
> >
> > Hi Magnus, Hi Geert,
> >
> > As I am currently doing some work for the r8a7779
> > I am wondering if a change like this one is appropriate for that SoC.
> > If so I'll cook one up.
>
> Yes, we want all SoCs to be converted over. Please take care that some
> DTS change may be needed to specify maximum frequency, so this may
> require a DTB update for the user. Which makes it less nice user
> experience for legacy code - if we care about that at this point. But
> legacy code also often tends to use early devices and other stuff, so
> this probably affects DT SoC code and DT reference board code mostly.
Does CPU frequency affect this patch (shmobile_init_late) as
well as the ones to use shmobile_init_delay?
next prev parent reply other threads:[~2014-05-16 4:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:10 [PATCH] ARM: shmobile: Use shmobile_init_late() on r8a7740 Magnus Damm
2014-05-11 23:10 ` Magnus Damm
2014-05-12 7:42 ` Geert Uytterhoeven
2014-05-12 7:42 ` Geert Uytterhoeven
2014-05-13 8:10 ` Simon Horman
2014-05-13 8:10 ` Simon Horman
2014-05-16 4:08 ` Simon Horman
2014-05-16 4:08 ` Simon Horman
2014-05-16 4:39 ` Magnus Damm
2014-05-16 4:39 ` Magnus Damm
2014-05-16 4:45 ` Simon Horman [this message]
2014-05-16 4:45 ` Simon Horman
2014-05-16 4:48 ` Magnus Damm
2014-05-16 4:48 ` Magnus Damm
2014-05-16 6:13 ` Simon Horman
2014-05-16 6:13 ` Simon Horman
2014-06-06 6:15 ` [PATCH] ARM: shmobile: Use shmobile_init_late() on r8a7791 DT-only Magnus Damm
2014-07-30 23:45 ` [PATCH] ARM: shmobile: Use shmobile_init_delay() on APE6EVM Magnus Damm
2014-07-31 0:12 ` Simon Horman
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=20140516044548.GA7185@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.