Message ID | 20210901091852.479202-1-maxime@cerno.tech |
---|---|
Headers | show |
Series | ARM: dts: Last round of DT schema fixes | expand |
Dne sreda, 01. september 2021 ob 11:18:39 CEST je Maxime Ripard napisal(a): > The name of our PMIC power supply names conflict with the generic > regulator supply check that matches anything called *-supply, including > the nodes, and then makes sure it's a phandle. > > A node is obviously not a phandle, so let's change our power supplies > names to avoid any conflict. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:40 CEST je Maxime Ripard napisal(a): > We've had a pinctrl node name convention for a while now, let's follow > it for the AXP pinctrl nodes as well. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:41 CEST je Maxime Ripard napisal(a): > Even though it translates to the same thing down to the binary level, we > should have an array of 2 number cells to describe each OPP, which in > turns create a validation warning. > > Let's fix this. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:42 CEST je Maxime Ripard napisal(a): > The operating-points-v2 nodes are named inconsistently, but mostly > either opp_table0 or gpu-opp-table. However, the underscore is an > invalid character for a node name and the thermal zone binding > explicitly requires that zones are called opp-table-*. Let's fix it. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:43 CEST je Maxime Ripard napisal(a): > According to the SPI NOR bindings, the flash node names are supposed to > be flash@<address>. Let's fix our users to use that new scheme. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Hi Maxime! Dne sreda, 01. september 2021 ob 11:18:44 CEST je Maxime Ripard napisal(a): > The crypto engine binding doesn't allow for any DMA property, yet the > v3s define some. Remove them. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > --- > arch/arm/boot/dts/sun8i-v3s.dtsi | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/arch/arm/boot/dts/sun8i-v3s.dtsi b/arch/arm/boot/dts/sun8i- v3s.dtsi > index b30bc1a25ebb..44382e36e825 100644 > --- a/arch/arm/boot/dts/sun8i-v3s.dtsi > +++ b/arch/arm/boot/dts/sun8i-v3s.dtsi > @@ -285,8 +285,6 @@ crypto@1c15000 { > interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>; > clocks = <&ccu CLK_BUS_CE>, <&ccu CLK_CE>; > clock-names = "ahb", "mod"; > - dmas = <&dma 16>, <&dma 16>; > - dma-names = "rx", "tx"; Since V3s documentation mentions those DMA channels, wouldn't be better to update bindings instead? Best regards, Jernej > resets = <&ccu RST_BUS_CE>; > reset-names = "ahb"; > }; > -- > 2.31.1 > >
Dne sreda, 01. september 2021 ob 11:18:45 CEST je Maxime Ripard napisal(a): > The edt,edt-ft5x06 compatible has never been a valid compatible > according to the binding. Let's change for one that is. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:46 CEST je Maxime Ripard napisal(a): > The dumb-vga-dac and adi,adv7123 compatibles are not supposed to be used > together according to the binding. > > Since the corpro gm7123 is a drop-in replacement for the adv7123, let's > remove dumb-vga-dac from our compatible list. > > Reviewed-by: Chen-Yu Tsai <wens@csie.org> > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:47 CEST je Maxime Ripard napisal(a): > The GPU thermal zone is named gpu_thermal. However, the underscore is > an invalid character for a node name and the thermal zone binding > explicitly requires that zones are called *-thermal. Let's fix it. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:48 CEST je Maxime Ripard napisal(a): > While it doesn't really matter from a functional point of view in this > driver's case, it's usually a good practice to list the clocks in a > driver in the same driver across all its users. > > The H6 is using the inverse order than all the other users, so let's > make it consistent. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:49 CEST je Maxime Ripard napisal(a): > The thermal zones one the A100 are called $device-thermal-zone. > > However, the thermal zone binding explicitly requires that zones are > called *-thermal. Let's fix it. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:50 CEST je Maxime Ripard napisal(a): > The fixed regulator clock name has a unit address, but no reg property, > which generates a warning in DTC. Change its name to remove its useless > unit address. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:51 CEST je Maxime Ripard napisal(a): > The anx6345 bridge mandates that the input port is named port@0. Since > we have a unit-address, this implies that we need a reg property with > the same value, but it was found to be missing in the Teres-I device > tree. Make sure it's there. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
Dne sreda, 01. september 2021 ob 11:18:52 CEST je Maxime Ripard napisal(a): > Neither the binding nor the driver make any use of the wakeup-source > property for the AXP803. Remove it. > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej
On Sun, Sep 05, 2021 at 11:02:44PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:39 CEST je Maxime Ripard napisal(a): > > The name of our PMIC power supply names conflict with the generic > > regulator supply check that matches anything called *-supply, including > > the nodes, and then makes sure it's a phandle. > > > > A node is obviously not a phandle, so let's change our power supplies > > names to avoid any conflict. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:03:11PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:40 CEST je Maxime Ripard napisal(a): > > We've had a pinctrl node name convention for a while now, let's follow > > it for the AXP pinctrl nodes as well. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:04:59PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:41 CEST je Maxime Ripard napisal(a): > > Even though it translates to the same thing down to the binary level, we > > should have an array of 2 number cells to describe each OPP, which in > > turns create a validation warning. > > > > Let's fix this. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks
On Sun, Sep 05, 2021 at 11:05:58PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:42 CEST je Maxime Ripard napisal(a): > > The operating-points-v2 nodes are named inconsistently, but mostly > > either opp_table0 or gpu-opp-table. However, the underscore is an > > invalid character for a node name and the thermal zone binding > > explicitly requires that zones are called opp-table-*. Let's fix it. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:06:45PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:43 CEST je Maxime Ripard napisal(a): > > According to the SPI NOR bindings, the flash node names are supposed to > > be flash@<address>. Let's fix our users to use that new scheme. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:11:58PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:45 CEST je Maxime Ripard napisal(a): > > The edt,edt-ft5x06 compatible has never been a valid compatible > > according to the binding. Let's change for one that is. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:12:27PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:46 CEST je Maxime Ripard napisal(a): > > The dumb-vga-dac and adi,adv7123 compatibles are not supposed to be used > > together according to the binding. > > > > Since the corpro gm7123 is a drop-in replacement for the adv7123, let's > > remove dumb-vga-dac from our compatible list. > > > > Reviewed-by: Chen-Yu Tsai <wens@csie.org> > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:12:51PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:47 CEST je Maxime Ripard napisal(a): > > The GPU thermal zone is named gpu_thermal. However, the underscore is > > an invalid character for a node name and the thermal zone binding > > explicitly requires that zones are called *-thermal. Let's fix it. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:13:25PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:48 CEST je Maxime Ripard napisal(a): > > While it doesn't really matter from a functional point of view in this > > driver's case, it's usually a good practice to list the clocks in a > > driver in the same driver across all its users. > > > > The H6 is using the inverse order than all the other users, so let's > > make it consistent. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:13:46PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:49 CEST je Maxime Ripard napisal(a): > > The thermal zones one the A100 are called $device-thermal-zone. > > > > However, the thermal zone binding explicitly requires that zones are > > called *-thermal. Let's fix it. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:14:08PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:50 CEST je Maxime Ripard napisal(a): > > The fixed regulator clock name has a unit address, but no reg property, > > which generates a warning in DTC. Change its name to remove its useless > > unit address. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:14:34PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:51 CEST je Maxime Ripard napisal(a): > > The anx6345 bridge mandates that the input port is named port@0. Since > > we have a unit-address, this implies that we need a reg property with > > the same value, but it was found to be missing in the Teres-I device > > tree. Make sure it's there. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Sun, Sep 05, 2021 at 11:24:48PM +0200, Jernej Škrabec wrote: > Dne sreda, 01. september 2021 ob 11:18:52 CEST je Maxime Ripard napisal(a): > > Neither the binding nor the driver make any use of the wakeup-source > > property for the AXP803. Remove it. > > > > Signed-off-by: Maxime Ripard <maxime@cerno.tech> > > Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Applied, thanks Maxime
On Wed, 1 Sep 2021 11:18:00 +0200, Maxime Ripard wrote: > Here's another round of schema warnings fixes for the Allwinner platform. > > There's a fair share of new schemas in there since the schema tools now warn > when a compatible is not documented in a schema. > > We don't have any warning anymore if we use the OPP binding Rob submitted, and > since that means we have all our devices properly validated I don't expect more > fixes now, aside from the usual bunch of regressions. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [01/52] ASoC: dt-bindings: Add WM8978 Binding commit: 5bd5699c494f42a3c23e377bb35be5d716b85012 [02/52] ASoC: dt-bindings: Convert Bluetooth SCO Link binding to a schema commit: 6ef239699102580b104bfca11d9b94abfbc8caec [03/52] ASoC: dt-bindings: Convert SPDIF Transmitter binding to a schema commit: 1c02b74ba20838ba194850beb0adfc6b5e11bb2a [04/52] ASoC: dt-bindings: Convert Simple Amplifier binding to a schema commit: 50a41ce8c56d07f42a97112077acbaeda8b86ed9 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark