public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Peng Fan (OSS) <peng.fan@oss.nxp.com>,
	aisheng.dong@nxp.com, bjorn.andersson@linaro.org,
	jbrunet@baylibre.com, linux-clk@vger.kernel.org,
	s.nawrocki@samsung.com, shawn.lin@rock-chips.com,
	ulf.hansson@linaro.org
Cc: linux-kernel@vger.kernel.org, van.freenix@gmail.com,
	Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] clk: bulk: export of_clk_bulk_get_all
Date: Wed, 05 Jan 2022 17:17:16 -0800	[thread overview]
Message-ID: <20220106011718.28688C36AE3@smtp.kernel.org> (raw)
In-Reply-To: <20211221031638.3499920-1-peng.fan@oss.nxp.com>

Quoting Peng Fan (OSS) (2021-12-20 19:16:38)
> From: Peng Fan <peng.fan@nxp.com>
> 
> There are cases that need to get the bulk clks of a device_node which not
> has device created, so export of_clk_bulk_get_all to let consumers could
> use it.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> 
> V1:
>      An example here, mediamix node has clocks property, but it will not

Sorry I don't get the example. What does a DT snippet have to do with
modular kernel code? What specific kernel module is calling this API?

>      have device of it, so we need of_X api to get the clks.
>      src: src@0x30390000 {
>           compatible = "fsl,imx[X]-src";
>           reg = <0x30390000 0x10000>;
> 
>           slice {

Is this upstream?

>                 #address-cells = <1>;
>                 #size-cells = <0>;
> 
>                 mediamix: slice@2400 {
>                    reg = <IMX93_POWER_DOMAIN_MEDIAMIX>;
>                    #power-domain-cells = <0>;

  reply	other threads:[~2022-01-06  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  3:16 [PATCH] clk: bulk: export of_clk_bulk_get_all Peng Fan (OSS)
2022-01-06  1:17 ` Stephen Boyd [this message]
2022-01-06  2:19   ` 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=20220106011718.28688C36AE3@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=jbrunet@baylibre.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=s.nawrocki@samsung.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@linaro.org \
    --cc=van.freenix@gmail.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