linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "A.s. Dong" <aisheng.dong@nxp.com>
To: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	"mturquette@baylibre.com" <mturquette@baylibre.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"thor.thayer@linux.intel.com" <thor.thayer@linux.intel.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"hdegoede@redhat.com" <hdegoede@redhat.com>
Subject: RE: [PATCH V6 0/4] clk: new APIs to handle all available clocks
Date: Thu, 6 Sep 2018 03:22:42 +0000	[thread overview]
Message-ID: <AM0PR04MB4211EF6D783562BA8C8D690380010@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1535690756-22234-1-git-send-email-aisheng.dong@nxp.com>

Gently ping...

> -----Original Message-----
> From: A.s. Dong
> Sent: Friday, August 31, 2018 12:46 PM
> To: linux-clk@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> sboyd@kernel.org; mturquette@baylibre.com; shawnguo@kernel.org;
> thor.thayer@linux.intel.com; dl-linux-imx <linux-imx@nxp.com>;
> hdegoede@redhat.com; A.s. Dong <aisheng.dong@nxp.com>
> Subject: [PATCH V6 0/4] clk: new APIs to handle all available clocks
>=20
> This patch series is a continue of discussion from here,
> https://patchwork.kernel.org/patch/9986293/
> that some users may want to handle all available clocks from device tree
> without need to know the detailed clock information likes clock numbers a=
nd
> names. This is useful in writing some generic drivers to handle clock par=
t.
>=20
> Note:
> This patch series is tested on MX6Q SDB cpufreq driver with a minor chang=
e to
> switch to use clk_bulk_get_all.
> But patch 4 only test compiling. Hopefully someone could help test the
> function.
>=20
> v3->v4:
>  * improve 'devres->clks =3D *clks' according to Stephen's suggestion
> v2->v3:
>  * address all comments from Stephen
>  * fix build warnings on other architectures.
> v1->v2:
>  * add clk_bulk_{get|put}_all() which only supports DT platform currently
>  * remove _all variants and the wrapper struct clk_bulk
>  * make of_clk_bulk_get and of_clk_bulk_get_all private until someone
>    proves they need it because they don't have a struct device pointer.
>=20
> Dong Aisheng (4):
>   clk: bulk: add of_clk_bulk_get()
>   clk: add new APIs to operate on all available clocks
>   clk: add managed version of clk_bulk_get_all
>   video: simplefb: switch to use clk_bulk API to simplify clock
>     operations
>=20
>  drivers/clk/clk-bulk.c         | 80
> ++++++++++++++++++++++++++++++++++++++++++
>  drivers/clk/clk-devres.c       | 24 +++++++++++++
>  drivers/video/fbdev/simplefb.c | 72 ++++++++++--------------------------=
-
>  include/linux/clk.h            | 65
> +++++++++++++++++++++++++++++++++-
>  4 files changed, 186 insertions(+), 55 deletions(-)
>=20
> --
> 2.7.4

  parent reply	other threads:[~2018-09-06  3:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  4:45 [PATCH V6 0/4] clk: new APIs to handle all available clocks Dong Aisheng
2018-08-31  4:45 ` [PATCH V6 1/4] clk: bulk: add of_clk_bulk_get() Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 2/4] clk: add new APIs to operate on all available clocks Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 3/4] clk: add managed version of clk_bulk_get_all Dong Aisheng
2018-10-16 22:44   ` Stephen Boyd
2018-08-31  4:45 ` [PATCH V6 4/4] video: simplefb: switch to use clk_bulk API to simplify clock operations Dong Aisheng
2018-08-31 10:09   ` Hans de Goede
2018-09-06  3:22 ` A.s. Dong [this message]
2018-09-16 13:24   ` [PATCH V6 0/4] clk: new APIs to handle all available clocks A.s. Dong
2018-09-19 14:47     ` Thor Thayer
2018-09-20  2:14       ` A.s. Dong
2018-10-08 10:43         ` A.s. Dong
2018-10-13 13:33           ` A.s. Dong

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=AM0PR04MB4211EF6D783562BA8C8D690380010@AM0PR04MB4211.eurprd04.prod.outlook.com \
    --to=aisheng.dong@nxp.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=thor.thayer@linux.intel.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;
as well as URLs for NNTP newsgroup(s).