Linux clock framework development
 help / color / mirror / Atom feed
From: Dong Aisheng <dongas86@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Dong Aisheng <aisheng.dong@nxp.com>,
	linux-clk@vger.kernel.org, leonard.crestez@nxp.com,
	ping.bai@nxp.com, anson.huang@nxp.com, viresh.kumar@linaro.org,
	mturquette@baylibre.com, rjw@rjwysocki.net,
	linux-kernel@vger.kernel.org, broonie@kernel.org,
	octavian.purdila@nxp.com, kernel@pengutronix.de,
	fabio.estevam@nxp.com, yibin.gong@nxp.com, shawnguo@kernel.org,
	sboyd@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/3] clk: introduce clk_bulk_get accessories
Date: Thu, 13 Apr 2017 21:58:28 +0800	[thread overview]
Message-ID: <20170413135828.GA24254@b29396-OptiPlex-7040> (raw)
In-Reply-To: <86200633-8349-f1c3-f4d8-a130a26381f7@gmail.com>

On Tue, Apr 11, 2017 at 10:01:29AM -0700, Florian Fainelli wrote:
...
> > This is a RFC patch intending to bring up the idea to discuss.
> > 
> > Comments are welcome and appreciated!
> 
> Thanks a lot for doing this, we have historically done something similar
> on ARCH_BRCMSTB platforms in our downstream tree with a concept of a
> "software" clock which has multiple parents (yikes), using the bulk
> accessors would essentially allow us to remove part of this hack, so I
> am all in favor of this!

Glad to see someone else has the same idea! :-)

Thanks for the supporting!

Regards
Dong Aisheng

  reply	other threads:[~2017-04-13 13:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  4:03 [RFC PATCH 0/3] clk: introduce clk_bulk_get accessories Dong Aisheng
2017-04-11 17:01 ` Florian Fainelli
2017-04-13 13:58   ` Dong Aisheng [this message]
2017-04-12  4:03 ` [RFC PATCH 1/3] clk: add " Dong Aisheng
2017-04-11 17:19   ` Leonard Crestez
2017-04-13 14:02     ` Dong Aisheng
2017-04-13 19:57     ` Geert Uytterhoeven
2017-04-13 14:25   ` Dong Aisheng
2017-04-13 19:56   ` Geert Uytterhoeven
2017-04-14 16:14     ` Dong Aisheng
2017-04-22  3:16   ` Stephen Boyd
2017-05-08 11:34     ` Dong Aisheng
2017-04-12  4:03 ` [RFC PATCH 2/3] clk: add managed version of clk_bulk_get Dong Aisheng
2017-04-13 14:37   ` Dong Aisheng
2017-04-22  2:58     ` Stephen Boyd
2017-05-08 11:41       ` Dong Aisheng
2017-04-22  2:55   ` Stephen Boyd
2017-05-08 11:37     ` Dong Aisheng
2017-04-12  4:03 ` [RFC PATCH 3/3] cpufreq: imx6q: refine clk operations Dong Aisheng
2017-04-11 17:48   ` Leonard Crestez
2017-04-13 14:21     ` Dong Aisheng
2017-04-22  3:04 ` [RFC PATCH 0/3] clk: introduce clk_bulk_get accessories Stephen Boyd
2017-05-08 11:07   ` Dong Aisheng

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=20170413135828.GA24254@b29396-OptiPlex-7040 \
    --to=dongas86@gmail.com \
    --cc=aisheng.dong@nxp.com \
    --cc=anson.huang@nxp.com \
    --cc=broonie@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=octavian.purdila@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=shawnguo@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=yibin.gong@nxp.com \
    /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