public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: sudeep.holla@arm•com (Sudeep Holla)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] Move clk-sp810 to assigned clock parents
Date: Mon, 03 Aug 2015 11:18:43 +0100	[thread overview]
Message-ID: <55BF4003.3040708@arm.com> (raw)
In-Reply-To: <1438386285-5070-1-git-send-email-sboyd@codeaurora.org>

Hi Stephen,

On 01/08/15 00:44, Stephen Boyd wrote:
> This patch set converts this code to use the assigned-clock-parents
> property instead of doing some interesting stuff in the .prepare
> op. I can route the dts patches through arm-soc but I'd like to take
> the clk patch through clk tree because it removes some usage of the
> struct clk based provider APIs that we're trying to get rid of. Also,
> this is completely untested, so testing would be appreciated.
> Can this be tested with qemu? I haven't tried but I was thinking
> that might be an option.
>
> Cc: Pawel Moll <pawel.moll@arm•com>
> Cc: Linus Walleij <linus.walleij@linaro•org>
> Cc: Sudeep Holla <sudeep.holla@arm•com>
>

Tested-by: Sudeep Holla <sudeep.holla@arm•com>
(Tested the series on Juno R0 and Vexpress TC2 platform)

Regards,
Sudeep

      parent reply	other threads:[~2015-08-03 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55BBB2FC.9030102@codeaurora.org>
2015-07-31 23:44 ` [PATCH 0/3] Move clk-sp810 to assigned clock parents Stephen Boyd
2015-07-31 23:44   ` [PATCH 1/3] clk: versatile: Switch " Stephen Boyd
2015-08-03 14:01     ` Pawel Moll
2015-08-03 17:55       ` Stephen Boyd
2015-08-05 10:29         ` Pawel Moll
2015-08-05 17:56           ` Stephen Boyd
2015-08-06 15:05             ` Pawel Moll
2015-08-07 22:28               ` Stephen Boyd
2015-07-31 23:44   ` [PATCH 2/3] ARM: dts: vexpress: Use assigned-clock-parents for sp810 Stephen Boyd
2015-07-31 23:44   ` [PATCH 3/3] ARM64: " Stephen Boyd
2015-08-03 10:18   ` Sudeep Holla [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=55BF4003.3040708@arm.com \
    --to=sudeep.holla@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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