Maybe there is a better solution; possibly others will respond too.
> With such a boolean we could also prevent the misleading
> "dma-names property of" error message and
> replace it with a hint that dma is disabled on purpose.
Given that you're now at least the 4th person trying this, I guess
a hint 'somewhere' would be beneficial.
I do not know if the error message itself would be considered misleading
and if something should be done about that.
Cheers,
Diederik
> >> Signed-off-by: Philipp Puschmann <p.puschmann@xxxxxxxxxxx>
> >> ---
> >>
> >> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 10 ++++++++++
> >> 1 file changed, 10 insertions(+)
> >>
> >> diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> >> b/arch/arm64/boot/dts/rockchip/rk356x.dtsi index
> >> d8543b5557ee..4ae40661ca6a
> >> 100644
> >> --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> >> +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
> >> @@ -489,6 +489,7 @@ uart0: serial@fdd50000 {
> >>
> >> clocks = <&pmucru SCLK_UART0>, <&pmucru PCLK_UART0>;
> >> clock-names = "baudclk", "apb_pclk";
> >> dmas = <&dmac0 0>, <&dmac0 1>;
> >>
> >> + dma-names = "tx", "rx";
> >>
> >> pinctrl-0 = <&uart0_xfer>;
> >> pinctrl-names = "default";
> >> reg-io-width = <4>;
> >>
> >> @@ -1389,6 +1390,7 @@ uart1: serial@fe650000 {
> >>
> >> clocks = <&cru SCLK_UART1>, <&cru PCLK_UART1>;
> >> clock-names = "baudclk", "apb_pclk";
> >> dmas = <&dmac0 2>, <&dmac0 3>;
> >>
> >> + dma-names = "tx", "rx";
> >>
> >> pinctrl-0 = <&uart1m0_xfer>;
> >> pinctrl-names = "default";
> >> reg-io-width = <4>;
> >>
> >> ...
--nextPart2410067.Ga172O2onJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit
-----BEGIN PGP SIGNATURE-----
iHUEABYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZo5oMAAKCRDXblvOeH7b
bmGoAQC1Ou//DJUMV1dx5LWCq4RXL2V3lrMo06IwIqmJHTl4ZAD9HLVblwDEpbkp
vfPu47lbOfgXiCzgq5osIraQlnRkcw4=
=8R71
-----END PGP SIGNATURE-----
--nextPart2410067.Ga172O2onJ--
