[PATCH 2/2] arm64/apm: add dts for Gigabyte MP30-AR0 board

Janne Grunau
2015-09-03T22:28:04Z

On 2015-09-02 14:57:53 +0100, Mark Rutland wrote:
> > > > +};
> > > > diff --git a/arch/arm64/boot/dts/apm/mp30ar0.dts b/arch/arm64/boot/dts/apm/mp30ar0.dts
> > > > new file mode 100644
> > > > index 0000000..f7a9dae5
> > > > --- /dev/null
> > > > +++ b/arch/arm64/boot/dts/apm/mp30ar0.dts

[...]

> > > > + };
> > > > +
> > > > + poweroff_mbox: poweroff_mbox at 10548000 {
> > > > + compatible = "syscon";
> > > > + reg = <0x0 0x10548000 0x0 0x100>;
> > > > + };
> > > > +
> > > > + poweroff at 10548010 {
> > > > + compatible = "syscon-poweroff";
> > > > + regmap = <&poweroff_mbox>;
> > > > + offset = <0x10>;
> > > > + mask = <0x1>;
> > > > + };
> > > > +
> > > > + chosen {
> > > > + linux,stdout-path = "/soc/serial at 1c020000";
> > >
> > > Please use stdout-path rather than linux,stdout-path.
> > >
> > > No rate configuration?
> > >
> > > This would look nicer with an alias.
> >
> > I can change that but the bootloader will add a 'linux,stdout-path' and
> > the stdout-path will override it. OTOH the bootloader seems to always
> > add this exact string so it will be fine to "override" it from the dts.
> > The alternative would to remove it.
>
> I guess it doesn't fill in the rate, which is somewhat unfortunate.
>
> Does it override an existing linux,stdout-path? If not, we could add the
> rate.

yes, it overrides an existing linux,stdout-path and it looks like an
hardcoded string.

> I think we should have a comment about the bootlaoder filling in
> linux,stdout-path, but other than that I'm not really sure what the best
> option is.

I'll add the comment and a stdout-path with alias and rate. There is at
least some hope that Gigabyte or APM will realease a newer/fixed
bootloader. The installed bootloader doesn't clear x2/x3.

Thanks Janne