Linux dev-4.7 tree: Request for testing

Rick Altherr raltherr at google.com
Tue Aug 23 10:53:48 AEST 2016


I remember a discussion in IRC about how to modify obmc-console for
multiple vuarts, etc.  I asked then if it made sense to entirely define the
vuart in the dts (specify sirq and lpc_addr) instead of having obmc-console
do it.  If we need to setup vuart aliases in the dts anyway, that seems to
make even more sense.

On Tue, Aug 16, 2016 at 5:15 PM, Joel Stanley <joel at jms.id.au> wrote:

> Hey Xo,
>
> On Wed, Aug 17, 2016 at 9:55 AM, Xo Wang <xow at google.com> wrote:
> >
> >> We need to use a mechanism to tell userspace which device is the
> >> vuart. udev? systemd?
> >
> > I think that's covered by this userspace configuration file:
> > https://github.com/openbmc/openbmc/blob/master/meta-
> phosphor/common/recipes-phosphor/obmc-console/obmc-
> console/obmc-console.conf
>
> Yeah. Ideally we would have systemd/udev populate this configuration
> file. There has been some work in this area; I think there are a few
> prerequisites from our systemd setup to land before we can turn that
> on.
>
> > It specifies the VUART console device as ttyS5, which doesn't exist using
> > our current DTS for the EVB.
> >
> >> $ ls /sys/devices/platform/ahb/ahb:apb/1e787000.vuart/tty
> >> ttyS0
> >>
> >> We could also set an alias in the device tree?
> >
> > That's how I did my testing for AST2500 EVB connected to an LPC host.
> This
> > enabled and aliased the vuart for me (please note s/uart6/vuart/g for
> > dev-4.7):
>
> I had a similar idea. If we can't think of a better solution then I
> will commit a patch to this effect today.
>
> Cheers,
>
> Joel
>
> > diff --git a/arch/arm/boot/dts/aspeed-ast2500-evb.dts
> > b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
> > index 28b0045..51b032d 100644
> > --- a/arch/arm/boot/dts/aspeed-ast2500-evb.dts
> > +++ b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
> > @@ -8,6 +8,7 @@
> >
> >         aliases {
> >                 serial4 = &uart5;
> > +               serial5 = &uart6;
> >         };
> >
> >         chosen {
> > @@ -39,6 +40,10 @@
> >         status = "okay";
> >  };
> >
> > +&uart6 {
> > +       status = "okay";
> > +};
> > +
> >  &mac0 {
> >         status = "okay";
> >  };
> >
> >
> >
> >
> > cheers
> > xo
> >
> > _______________________________________________
> > openbmc mailing list
> > openbmc at lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160822/dd75bb1f/attachment.html>


More information about the openbmc mailing list