* [PATCH v2] ARM: dts: am33xx-l4: Add missing touchscreen clock properties
@ 2022-03-14 16:34 Miquel Raynal
2022-04-12 9:47 ` Tony Lindgren
0 siblings, 1 reply; 2+ messages in thread
From: Miquel Raynal @ 2022-03-14 16:34 UTC (permalink / raw)
To: Benoit Cousson, Tony Lindgren
Cc: Rob Herring, devicetree, linux-omap, Thomas Petazzoni,
Miquel Raynal, H . Nikolaus Schaller
When adding support for TI magadc (Magnetic Stripe Reader and ADC), the
MFD driver common to the touchscreen and the ADC got updated to ease the
insertion of a new DT node for the ADC, with its own compatible, clocks,
etc. Commit 235a96e92c16 ("mfd: ti_am335x_tscadc: Don't search the tree
for our clock") removed one compatible specific information which was
the clock name, because the clock was looked up from scratch in the DT
while this hardware block was only fed by a single clock, already
defined and properly filled in the DT.
Problem is, this change was only validated with an am437x-based board,
where the clocks are effectively correctly defined and referenced. But
on am33xx, the ADC clock is also correctly defined but is not referenced
with a clock phandle as it ought to be.
The touchscreen bindings clearly state that the clocks/clock-names
properties are mandatory, but they have been forgotten in one DTSI. This
was probably not noticed in the first place because of the clock
actually existing and the clk_get() call going through all the tree
anyway.
Add the missing clock phandles in the am33xx touchscreen description.
Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
Fixes: 235a96e92c16 ("mfd: ti_am335x_tscadc: Don't search the tree for our clock")
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
---
Changes in v2:
- Explained the "magadc" name
- s/out to be/ought to be/
- Added Nikolaus Tested-by
arch/arm/boot/dts/am33xx-l4.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx-l4.dtsi b/arch/arm/boot/dts/am33xx-l4.dtsi
index c9629cb5ccd1..7da42a5b959c 100644
--- a/arch/arm/boot/dts/am33xx-l4.dtsi
+++ b/arch/arm/boot/dts/am33xx-l4.dtsi
@@ -263,6 +263,8 @@ tscadc: tscadc@0 {
compatible = "ti,am3359-tscadc";
reg = <0x0 0x1000>;
interrupts = <16>;
+ clocks = <&adc_tsc_fck>;
+ clock-names = "fck";
status = "disabled";
dmas = <&edma 53 0>, <&edma 57 0>;
dma-names = "fifo0", "fifo1";
--
2.27.0
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH v2] ARM: dts: am33xx-l4: Add missing touchscreen clock properties
2022-03-14 16:34 [PATCH v2] ARM: dts: am33xx-l4: Add missing touchscreen clock properties Miquel Raynal
@ 2022-04-12 9:47 ` Tony Lindgren
0 siblings, 0 replies; 2+ messages in thread
From: Tony Lindgren @ 2022-04-12 9:47 UTC (permalink / raw)
To: Miquel Raynal
Cc: Benoit Cousson, Rob Herring, devicetree, linux-omap,
Thomas Petazzoni, H . Nikolaus Schaller
* Miquel Raynal <miquel.raynal@bootlin.com> [220314 18:33]:
> The touchscreen bindings clearly state that the clocks/clock-names
> properties are mandatory, but they have been forgotten in one DTSI. This
> was probably not noticed in the first place because of the clock
> actually existing and the clk_get() call going through all the tree
> anyway.
>
> Add the missing clock phandles in the am33xx touchscreen description.
>
> Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
> Fixes: 235a96e92c16 ("mfd: ti_am335x_tscadc: Don't search the tree for our clock")
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
Applying into fixes thanks.
Tony
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-04-12 10:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-03-14 16:34 [PATCH v2] ARM: dts: am33xx-l4: Add missing touchscreen clock properties Miquel Raynal
2022-04-12 9:47 ` Tony Lindgren
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).