linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: Re: [PATCH v3 5/5] clk: samsung: add exynos7870 CLKOUT support
Date: Mon, 24 Feb 2025 23:17:46 +0530	[thread overview]
Message-ID: <e2ebd4503100ddbbe8d7e21290329e38@disroot.org> (raw)
In-Reply-To: <20250219-discerning-affable-chital-1fdff4@krzk-bin>

On 2025-02-19 13:41, Krzysztof Kozlowski wrote:
> On Wed, Feb 19, 2025 at 12:20:32AM +0530, Kaustabh Chakraborty wrote:
>> Exynos7870's CLKOUT registers are the same as Exynos5's. Add the PMU
>> compatible to the existing CLKOUT ID list.
>> 
>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>> ---
>>  drivers/clk/samsung/clk-exynos-clkout.c | 3 +++
>>  1 file changed, 3 insertions(+)
>> 
>> diff --git a/drivers/clk/samsung/clk-exynos-clkout.c b/drivers/clk/samsung/clk-exynos-clkout.c
>> index 2ef5748c139b37ca5429b9071ee0e06f44fcf28e..9a31b1c311b45096f1d680b6724571854c08725c 100644
>> --- a/drivers/clk/samsung/clk-exynos-clkout.c
>> +++ b/drivers/clk/samsung/clk-exynos-clkout.c
>> @@ -75,6 +75,9 @@ static const struct of_device_id exynos_clkout_ids[] = {
>>  	}, {
>>  		.compatible = "samsung,exynos5433-pmu",
>>  		.data = &exynos_clkout_exynos5,
>> +	}, {
>> +		.compatible = "samsung,exynos7870-pmu",
>> +		.data = &exynos_clkout_exynos5,
> 
> I wonder why do we need to keep growing this list? All devices are
> compatible, aren't they?

Well, there are two variants of compatibility having different mask
values.

> Do you use clkout, BTW?

Using the clocks defined by clkout? No. I added it as downstream
had it too. And the devices work fine without it. If you want me
to remove this patch and send the PMU patch to its respective
series I'll do that then (unless you object or suggest something
else).

> Best regards,
> Krzysztof


  reply	other threads:[~2025-02-24 17:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 18:50 [PATCH v3 0/5] Introduce support for Exynos7870 clocks and PMU Kaustabh Chakraborty
2025-02-18 18:50 ` [PATCH v3 1/5] dt-bindings: clock: add clock definitions for exynos7870 CMU Kaustabh Chakraborty
2025-02-19  8:07   ` Krzysztof Kozlowski
2025-02-19  8:10     ` Krzysztof Kozlowski
2025-02-23  9:57   ` Krzysztof Kozlowski
2025-02-18 18:50 ` [PATCH v3 2/5] dt-bindings: clock: document exynos7870 clock driver CMU bindings Kaustabh Chakraborty
2025-02-19  8:05   ` Krzysztof Kozlowski
2025-02-19  8:10     ` Krzysztof Kozlowski
2025-02-18 18:50 ` [PATCH v3 3/5] dt-bindings: soc: samsung: exynos-pmu: add exynos7870-pmu compatible Kaustabh Chakraborty
2025-02-19  8:09   ` Krzysztof Kozlowski
2025-02-19  8:18     ` Krzysztof Kozlowski
2025-02-18 18:50 ` [PATCH v3 4/5] clk: samsung: add initial exynos7870 clock driver Kaustabh Chakraborty
2025-02-18 18:50 ` [PATCH v3 5/5] clk: samsung: add exynos7870 CLKOUT support Kaustabh Chakraborty
2025-02-19  8:11   ` Krzysztof Kozlowski
2025-02-24 17:47     ` Kaustabh Chakraborty [this message]
2025-02-24 19:13       ` Krzysztof Kozlowski
2025-02-25 18:33         ` Kaustabh Chakraborty
2025-02-28 19:07         ` David Virag

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=e2ebd4503100ddbbe8d7e21290329e38@disroot.org \
    --to=kauschluss@disroot.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@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 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).