Messages in this thread |  | | Subject | Re: [PATCH v2 4/5] ARM: mstar: Add dts for msc313(e) based BreadBee boards | From | Andreas Färber <> | Date | Thu, 11 Jun 2020 15:45:29 +0200 |
| |
Am 10.06.20 um 11:04 schrieb Daniel Palmer: > BreadBee is an opensource development board based on the > MStar msc313(e) SoC. > > Hardware details, schematics and so on can be found at: > https://github.com/breadbee/breadbee > > Signed-off-by: Daniel Palmer <daniel@0x0f.com> > --- > arch/arm/boot/dts/Makefile | 3 +++ > .../dts/infinity-msc313-breadbee_crust.dts | 25 +++++++++++++++++++ > .../boot/dts/infinity3-msc313e-breadbee.dts | 25 +++++++++++++++++++ > 3 files changed, 53 insertions(+) > create mode 100644 arch/arm/boot/dts/infinity-msc313-breadbee_crust.dts > create mode 100644 arch/arm/boot/dts/infinity3-msc313e-breadbee.dts > > diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile > index e6a1cac0bfc7..4a5f8075a4f6 100644 > --- a/arch/arm/boot/dts/Makefile > +++ b/arch/arm/boot/dts/Makefile > @@ -1342,6 +1342,9 @@ dtb-$(CONFIG_ARCH_MEDIATEK) += \ > mt8127-moose.dtb \ > mt8135-evbp1.dtb > dtb-$(CONFIG_ARCH_MILBEAUT) += milbeaut-m10v-evb.dtb > +dtb-$(CONFIG_ARCH_MSTARV7) += \ > + infinity-msc313-breadbee_crust.dtb \ > + infinity3-msc313e-breadbee.dtb > dtb-$(CONFIG_ARCH_ZX) += zx296702-ad1.dtb > dtb-$(CONFIG_ARCH_ASPEED) += \ > aspeed-ast2500-evb.dtb \ > diff --git a/arch/arm/boot/dts/infinity-msc313-breadbee_crust.dts b/arch/arm/boot/dts/infinity-msc313-breadbee_crust.dts > new file mode 100644 > index 000000000000..8a827c8fd8b2 > --- /dev/null > +++ b/arch/arm/boot/dts/infinity-msc313-breadbee_crust.dts > @@ -0,0 +1,25 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* > + * Copyright (c) 2019 thingy.jp. > + * Author: Daniel Palmer <daniel@thingy.jp> > + */ > + > +/dts-v1/; > +#include "infinity-msc313.dtsi" > + > +/ { > + model = "breadbee-crust";
This is user-visible text, so "BreadBee Crust" or so?
> + compatible = "thingyjp,breadbee-crust", "mstar,infinity"; > + > + aliases { > + serial0 = &pm_uart; > + }; > + > + chosen { > + stdout-path = "serial0:115200n8"; > + }; > +}; > + > +&pm_uart { > + status = "okay";
Might this be a more suited place for temporary clock-frequency? For lack of clk driver it would seem to depend on the board's bootloader pre-configuring it rather than being a default of the SoC.
> +}; > diff --git a/arch/arm/boot/dts/infinity3-msc313e-breadbee.dts b/arch/arm/boot/dts/infinity3-msc313e-breadbee.dts > new file mode 100644 > index 000000000000..423bb32e6b74 > --- /dev/null > +++ b/arch/arm/boot/dts/infinity3-msc313e-breadbee.dts > @@ -0,0 +1,25 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* > + * Copyright (c) 2019 thingy.jp. > + * Author: Daniel Palmer <daniel@thingy.jp> > + */ > + > +/dts-v1/; > +#include "infinity3-msc313e.dtsi" > + > +/ { > + model = "breadbee";
Ditto, "BreadBee"?
> + compatible = "thingyjp,breadbee", "mstar,infinity3"; > + > + aliases { > + serial0 = &pm_uart; > + }; > + > + chosen { > + stdout-path = "serial0:115200n8"; > + }; > +}; > + > +&pm_uart { > + status = "okay";
Ditto, clock-frequency?
> +};
Regards, Andreas
-- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
|  |