devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Eduardo Valentin" <edubezval@gmail.com>,
	"Linux PM list" <linux-pm@vger.kernel.org>,
	devicetree@vger.kernel.org, "Magnus Damm" <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [1/2] arm64: dts: r8a7795: add thermal cooling management
Date: Wed, 3 Jan 2018 11:25:37 +0100	[thread overview]
Message-ID: <CAMuHMdWf76hNbQva_z9-2bCbBiGfA-veK9GdCqTyThaiBsNpMQ@mail.gmail.com> (raw)
In-Reply-To: <20180103101438.il5grrfihewiduqe@verge.net.au>

Hi Simon,

On Wed, Jan 3, 2018 at 11:14 AM, Simon Horman <horms@verge.net.au> wrote:
> On Wed, Jan 03, 2018 at 01:03:52AM +0100, Niklas Söderlund wrote:
>> On 2018-01-02 10:19:44 +0100, Simon Horman wrote:
>> > On Mon, Jan 01, 2018 at 10:13:35AM -0800, Eduardo Valentin wrote:
>> > > On Wed, Sep 13, 2017 at 12:59:08PM +0200, Niklas Söderlund wrote:
>> > > > Add nodes and properties for thermal cooling management support.
>> > > >
>> > > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>> > > > ---
>> > >
>> > > Just a reminder, this series should go via your arch tree. You may add
>> > > my acks.
>> >
>> > Ack.
>> >
>> > Niklas, could you comment on the readiness of these patches
>> > for the renesas tree?
>>
>> I think maybe the patches might have became a bit outdated since they
>> where posted due to all reg property fixup patches. The blocker for me
>> reposting this series is that the patches this depends
>> 'topic/rcar-gen3-cpufreq' on are not yet in the renesas tree next or
>> devel branches. Do you think it would be valuable for me to refresh
>> these patches before the dependencies are picked up?
>
> Probably not. I'll try to work on getting cpufreq upstream :)

I think it's working fine in renesas-drivers, isn't it?

As in the mean time the R-Car Gen3 CPG/MSSR drivers gained suspend/resume
support, the only missing part is support for restoring the Z* clocks during
system resume.  Unless that is handled automatically by the cpufreq core.
For secondary CPU cores, this may be handled by the CPU hotplug code.
For the primary CPU core, I don't know.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2018-01-03 10:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 10:59 [PATCH 0/2] arm64: dts: r8a7795: r8a7796: add thermal cooling management Niklas Söderlund
     [not found] ` <20170913105909.13230-1-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2017-09-13 10:59   ` [PATCH 1/2] arm64: dts: r8a7795: " Niklas Söderlund
     [not found]     ` <20170913105909.13230-2-niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>
2018-01-01 18:12       ` [1/2] " Eduardo Valentin
2018-01-01 18:13     ` Eduardo Valentin
2018-01-02  9:19       ` Simon Horman
2018-01-03  0:03         ` Niklas Söderlund
2018-01-03 10:14           ` Simon Horman
2018-01-03 10:25             ` Geert Uytterhoeven [this message]
2018-01-04 16:53               ` Simon Horman
2017-09-13 10:59   ` [PATCH 2/2] arm64: dts: r8a7796: " Niklas Söderlund
2018-01-01 18:11     ` [2/2] " Eduardo Valentin
2017-09-15  7:37   ` [PATCH 0/2] arm64: dts: r8a7795: " 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=CAMuHMdWf76hNbQva_z9-2bCbBiGfA-veK9GdCqTyThaiBsNpMQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=edubezval@gmail.com \
    --cc=horms@verge.net.au \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=niklas.soderlund@ragnatech.se \
    /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).