dts: arm: renesas: ra: fix incorrect node name for sci devices

[iandmorris]

The sci devices described in the device tree source for RA MCUs are incorrectly specified as being UARTs when they should be SCIs (serial communication interfaces) which can not only operate as UARTs but also as I2C, SPI etc.

[fabiobaltieri]

hey thanks, I think that status = <disable> should go as well since there's no driver backing renesas,ra-sci and the device is enabled by enabling the uart child node, otherwise you'd get in a weird config where the child is enabled but the parent is not, which is harmless but does not look quite right, what do you think?

[soburi]

@iandmorris

Thank you for catching my mistakes.

@fabiobaltieri

There is a similar implementation in stm32,

for example,

zephyr/dts/arm/st/f1/stm32f1.dtsi

Lines 243 to 258 in 21e3749

	timers1: timers@40012c00 {
	compatible = "st,stm32-timers";
	reg = <0x40012c00 0x400>;
	clocks = <&rcc STM32_CLOCK_BUS_APB2 0x00000800>;
	resets = <&rctl STM32_RESET(APB2, 11U)>;
	interrupts = <24 0>, <25 0>, <26 0>, <27 0>;
	interrupt-names = "brk", "up", "trgcom", "cc";
	st,prescaler = <0>;
	status = "disabled";
	pwm {
	compatible = "st,stm32-pwm";
	status = "disabled";
	#pwm-cells = <3>;
	};
	};

There is no driver corresponding to "st,stm32-timers" here.
yaml is defined as a common node for the timers.

zephyr/boards/arm/stm32f103_mini/stm32f103_mini.dts

Lines 105 to 114 in 21e3749

	&timers1 {
	st,prescaler = <10000>;
	status = "okay";
	pwm1: pwm {
	status = "okay";
	pinctrl-0 = <&tim1_ch1_pwm_out_pa8>;
	pinctrl-names = "default";
	};
	};

When using timer or pwm, set status="okay" for both parent and child.

It is certainly a strange configuration, and originally it would be desirable to check it with DTC, but the impact is too large.
In this case, we can consider checking the status of the parent node using the UART driver.
I'll think about it for a moment.

[fabiobaltieri]

@soburi fair enough, I'm happy with either.