All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: Abel Vesa <abel.vesa@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Aisheng Dong <aisheng.dong@nxp.com>,
	Anson Huang <anson.huang@nxp.com>
Cc: dl-linux-imx <linux-imx@nxp.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Abel Vesa <abel.vesa@nxp.com>
Subject: RE: [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only
Date: Tue, 17 Nov 2020 02:47:53 +0000	[thread overview]
Message-ID: <DB6PR0402MB276070853555160D0AB5641C88E20@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1603301815-24670-1-git-send-email-abel.vesa@nxp.com>

> Subject: [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only

Any follow up about this patchset?

Regards,
Peng.

> 
> On i.MX8M platforms the dram_apb and dram_alt are controlled from EL3.
> So in order to keep track of the actual clock tree in kernel, we need to
> actually declare the clocks but never write to any of their registes.
> We do that by registering the clocks with only the ops that read but never
> write the registers.
> 
> Abel Vesa (4):
>   clk: Add CLK_GET_PARENT_NOCACHE flag
>   clk: Add clk_gate_ro_ops for read-only gate clocks
>   clk: imx: composite-8m: Add DRAM clock registration variant
>   clk: imx8m: Use dram variant registration for dram clocks
> 
>  drivers/clk/clk-gate.c             |  5 +++++
>  drivers/clk/clk.c                  | 31 +++++++++++++++++--------------
>  drivers/clk/imx/clk-composite-8m.c | 12 +++++++++++-
>  drivers/clk/imx/clk-imx8mm.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mn.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mp.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mq.c       |  4 ++--
>  drivers/clk/imx/clk.h              |  7 +++++++
>  include/linux/clk-provider.h       |  2 ++
>  9 files changed, 50 insertions(+), 23 deletions(-)
> 
> --
> 2.7.4


WARNING: multiple messages have this Message-ID (diff)
From: Peng Fan <peng.fan@nxp.com>
To: Abel Vesa <abel.vesa@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Aisheng Dong <aisheng.dong@nxp.com>,
	Anson Huang <anson.huang@nxp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Abel Vesa <abel.vesa@nxp.com>, dl-linux-imx <linux-imx@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: RE: [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only
Date: Tue, 17 Nov 2020 02:47:53 +0000	[thread overview]
Message-ID: <DB6PR0402MB276070853555160D0AB5641C88E20@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1603301815-24670-1-git-send-email-abel.vesa@nxp.com>

> Subject: [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only

Any follow up about this patchset?

Regards,
Peng.

> 
> On i.MX8M platforms the dram_apb and dram_alt are controlled from EL3.
> So in order to keep track of the actual clock tree in kernel, we need to
> actually declare the clocks but never write to any of their registes.
> We do that by registering the clocks with only the ops that read but never
> write the registers.
> 
> Abel Vesa (4):
>   clk: Add CLK_GET_PARENT_NOCACHE flag
>   clk: Add clk_gate_ro_ops for read-only gate clocks
>   clk: imx: composite-8m: Add DRAM clock registration variant
>   clk: imx8m: Use dram variant registration for dram clocks
> 
>  drivers/clk/clk-gate.c             |  5 +++++
>  drivers/clk/clk.c                  | 31 +++++++++++++++++--------------
>  drivers/clk/imx/clk-composite-8m.c | 12 +++++++++++-
>  drivers/clk/imx/clk-imx8mm.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mn.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mp.c       |  4 ++--
>  drivers/clk/imx/clk-imx8mq.c       |  4 ++--
>  drivers/clk/imx/clk.h              |  7 +++++++
>  include/linux/clk-provider.h       |  2 ++
>  9 files changed, 50 insertions(+), 23 deletions(-)
> 
> --
> 2.7.4


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-11-17  2:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 17:36 [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only Abel Vesa
2020-10-21 17:36 ` Abel Vesa
2020-10-21 17:36 ` [RFC 1/4] clk: Add CLK_GET_PARENT_NOCACHE flag Abel Vesa
2020-10-21 17:36   ` Abel Vesa
2020-10-21 17:36 ` [RFC 2/4] clk: Add clk_gate_ro_ops for read-only gate clocks Abel Vesa
2020-10-21 17:36   ` Abel Vesa
2020-10-21 17:36 ` [RFC 3/4] clk: imx: composite-8m: Add DRAM clock registration variant Abel Vesa
2020-10-21 17:36   ` Abel Vesa
2020-10-21 17:36 ` [RFC 4/4] clk: imx8m: Use dram variant registration for dram clocks Abel Vesa
2020-10-21 17:36   ` Abel Vesa
2020-11-17  2:47 ` Peng Fan [this message]
2020-11-17  2:47   ` [RFC 0/4] clk: imx: Register the dram_apb and dram_alt as read-only Peng Fan

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=DB6PR0402MB276070853555160D0AB5641C88E20@DB6PR0402MB2760.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=abel.vesa@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=anson.huang@nxp.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=sboyd@kernel.org \
    --cc=shawnguo@kernel.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.