linux-kernel - Re: [PATCH v3 5/5] clk: samsung: add exynos7870 CLKOUT support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5670d992-71f4-4791-94ff-4fadc1fb5993@kernel.org>
Date: Mon, 24 Feb 2025 20:13:38 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kaustabh Chakraborty <kauschluss@...root.org>
Cc: Sylwester Nawrocki <s.nawrocki@...sung.com>,
 Chanwoo Choi <cw00.choi@...sung.com>, Alim Akhtar <alim.akhtar@...sung.com>,
 Michael Turquette <mturquette@...libre.com>, Stephen Boyd
 <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski
 <krzk+dt@...nel.org>, linux-kernel@...r.kernel.org,
 linux-samsung-soc@...r.kernel.org, linux-clk@...r.kernel.org,
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 5/5] clk: samsung: add exynos7870 CLKOUT support

On 24/02/2025 18:47, Kaustabh Chakraborty wrote:
>>
>> 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).

clkout is a testing tool and I doubt you can use it on a phone - finding
the actual clkout pins to connect the oscilloscope is tricky.

If this is about to grow and be used, then we should fix the
compatibility and do not duplicate the ID table.

Best regards,
Krzysztof