Hi,
On 07-31 15:13, Florian Fainelli wrote:
> > +
> > +/* uarta communicates with the BT module */
> > +&uarta {
> > + uart-has-rtscts;
> > + auto-flow-control;
> > + status = "okay";
> > + clock-frequency = <96000000>;
>
> Would not the "clock-frequency" belong to the .dtsi node instead?
>
Perhaps.
> > + pinctrl-0 = <&uarta_24_pins &bt_shutdown_pins>;
> > + pinctrl-names = "default";
> > +
> > + bluetooth: bluetooth {
> > + compatible = "brcm,bcm43438-bt";
> > + max-speed = <3000000>;
> > + shutdown-gpios = <&gio 29 GPIO_ACTIVE_HIGH>;
> > + local-bd-address = [ 00 00 00 00 00 00 ];
> > + };
> > +};
> > diff --git a/arch/arm64/boot/dts/broadcom/bcm2712.dtsi b/arch/arm64/boot/dts/broadcom/bcm2712.dtsi
> > index 3c0663dc6712..e972f94d6828 100644
> > --- a/arch/arm64/boot/dts/broadcom/bcm2712.dtsi
> > +++ b/arch/arm64/boot/dts/broadcom/bcm2712.dtsi
> > @@ -305,6 +305,17 @@ gio: gpio@7d508500 {
> > brcm,gpio-direct;
> > };
> > + uarta: serial@7d50c000 {
> > + compatible = "brcm,bcm7271-uart";
> > + reg = <0x7d50c000 0x20>;
> > + reg-names = "uart";
> > + reg-shift = <2>;
> > + reg-io-width = <4>;
> > + interrupts = <GIC_SPI 276 IRQ_TYPE_LEVEL_HIGH>;
> > + skip-init;
>
> Also an undocumented property upstream, what does it do? Is this to set
> UPF_SKIP_TEST?
It is U-Boot thing [1]. I suppose I can drop it.
Thanks,
Ivan
[1] ... "
serial: pl01x: Add support for devices with the rate pre-configured.
For Raspberry Pi, we had the input clock rate to the pl011 fixed in
the rpi.c file, but it may be changed by firmware due to user changes
to config.txt. Since the firmware always sets up the uart (default
115200 output unless the user changes it), we can just skip our own
uart init to simplify the boot process and more reliably get serial
output.
..."
