From: Stephen Boyd <sboyd@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, upstream@airoha.com
Cc: Christian Marangi <ansuelsmth@gmail.com>
Subject: Re: [PATCH v6 1/4] clk: en7523: Rework clock handling for different clock numbers
Date: Mon, 13 Jan 2025 15:54:43 -0800 [thread overview]
Message-ID: <9c40b220d699799b2bfaa75c3ef05f11.sboyd@kernel.org> (raw)
In-Reply-To: <20250113231030.6735-2-ansuelsmth@gmail.com>
Quoting Christian Marangi (2025-01-13 15:10:02)
> Airoha EN7581 SoC have additional clock compared to EN7523 but current
> driver permits to only support up to EN7523 clock numbers.
>
> To handle this, rework the clock handling and permit to declare the
> clocks number in match_data and alloca clk_data based on the compatible
> match_data.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2025-01-13 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 23:10 [PATCH v6 0/4] clk: en7523: cleanup + eMMC clk for EN7581 Christian Marangi
2025-01-13 23:10 ` [PATCH v6 1/4] clk: en7523: Rework clock handling for different clock numbers Christian Marangi
2025-01-13 23:54 ` Stephen Boyd [this message]
2025-01-13 23:10 ` [PATCH v6 2/4] dt-bindings: clock: drop NUM_CLOCKS define for EN7581 Christian Marangi
2025-01-13 23:55 ` Stephen Boyd
2025-01-13 23:10 ` [PATCH v6 3/4] dt-bindings: clock: add ID for eMMC " Christian Marangi
2025-01-13 23:55 ` Stephen Boyd
2025-01-13 23:10 ` [PATCH v6 4/4] clk: en7523: Add clock " Christian Marangi
2025-01-13 23:55 ` Stephen Boyd
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=9c40b220d699799b2bfaa75c3ef05f11.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=upstream@airoha.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 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.