linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: "Conor Dooley" <conor+dt@kernel.org>,
	"Gregory CLEMENT" <gregory.clement@bootlin.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Théo Lebrun" <theo.lebrun@bootlin.com>
Cc: "Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
	linux-mips@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>,
	linux-gpio@vger.kernel.org,
	"Théo Lebrun" <theo.lebrun@bootlin.com>
Subject: Re: [PATCH v7 02/14] clk: fixed-factor: add fwname-based constructor functions
Date: Wed, 21 Feb 2024 22:13:16 -0800	[thread overview]
Message-ID: <654a33c729af90d8d5bd70d320fa6f6f.sboyd@kernel.org> (raw)
In-Reply-To: <20240221-mbly-clk-v7-2-31d4ce3630c3@bootlin.com>

Quoting Théo Lebrun (2024-02-21 10:22:10)
> Add four functions to register clk_hw based on the fw_name field in
> clk_parent_data, ie the value in the DT property `clock-names`.
> 
> There are variants for devm or not and passing an accuracy or not
> passing one:
> 
>  - clk_hw_register_fixed_factor_fwname
>  - clk_hw_register_fixed_factor_with_accuracy_fwname
>  - devm_clk_hw_register_fixed_factor_fwname
>  - devm_clk_hw_register_fixed_factor_with_accuracy_fwname
> 
> The `struct clk_parent_data` init is extracted from
> __clk_hw_register_fixed_factor to each calling function. It is required
> to allow each function to pass whatever field they want, not only index.
> 
> Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
> ---

Applied to clk-next

Hopefully these are all going to be used.

  reply	other threads:[~2024-02-22  6:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 18:22 [PATCH v7 00/14] Add support for Mobileye EyeQ5 system controller Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 01/14] clk: fixed-factor: add optional accuracy support Théo Lebrun
2024-02-22  6:12   ` Stephen Boyd
2024-02-21 18:22 ` [PATCH v7 02/14] clk: fixed-factor: add fwname-based constructor functions Théo Lebrun
2024-02-22  6:13   ` Stephen Boyd [this message]
2024-02-21 18:22 ` [PATCH v7 03/14] dt-bindings: clock: mobileye,eyeq5-clk: add bindings Théo Lebrun
2024-02-22  6:14   ` Stephen Boyd
2024-02-21 18:22 ` [PATCH v7 04/14] dt-bindings: reset: mobileye,eyeq5-reset: " Théo Lebrun
2024-02-22  6:14   ` Stephen Boyd
2024-02-21 18:22 ` [PATCH v7 05/14] dt-bindings: pinctrl: mobileye,eyeq5-pinctrl: " Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 06/14] dt-bindings: soc: mobileye: add EyeQ5 OLB system controller Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 07/14] clk: eyeq5: add platform driver, and init routine at of_clk_init() Théo Lebrun
2024-02-22  5:06   ` andy.shevchenko
2024-02-22 14:56     ` Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 08/14] reset: eyeq5: add platform driver Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 09/14] pinctrl: " Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 10/14] MAINTAINERS: Map OLB files to Mobileye SoCs Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 11/14] MIPS: mobileye: eyeq5: add OLB syscon node Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 12/14] MIPS: mobileye: eyeq5: use OLB clocks controller node Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 13/14] MIPS: mobileye: eyeq5: add OLB reset " Théo Lebrun
2024-02-21 18:22 ` [PATCH v7 14/14] MIPS: mobileye: eyeq5: add pinctrl node & pinmux function nodes Théo Lebrun

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=654a33c729af90d8d5bd70d320fa6f6f.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@kernel.org \
    --cc=tawfik.bayouk@mobileye.com \
    --cc=theo.lebrun@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=vladimir.kondratiev@mobileye.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).