Message ID | CACPK8XdG=wjKuAJJ7yzu320UPxKAGA-A2DYtrL5=CwCN2DNpBg@mail.gmail.com |
---|---|
State | New |
Headers | show |
Series | [GIT,PULL] ARM: dts: aspeed: Changes for v4.15 | expand |
On Fri, Oct 6, 2017 at 9:05 AM, Joel Stanley <joel@jms.id.au> wrote: > Hello ARM SoC maintainers! > > Here are some ASPEED device tree updates for v4.15. > > Sadly our clk driver is still under review, so I have not been able to > include all of the patches I intended to. Alas, these improvements are > still useful. Pulled into next/dt > ARM: dts: aspeed: Add aliases for UARTs Can you explain this one? It looks like you now have aliases for all uart and i2c entries on all machines, even when they don't actually expose the ports. The purpose of the aliases is to only list the ones that are actually usable, so they should normally go into the board specific .dts files. Arnd
On Fri, Oct 20, 2017 at 8:19 AM, Arnd Bergmann <arnd@arndb.de> wrote: > On Fri, Oct 6, 2017 at 9:05 AM, Joel Stanley <joel@jms.id.au> wrote: >> Hello ARM SoC maintainers! >> >> Here are some ASPEED device tree updates for v4.15. >> >> Sadly our clk driver is still under review, so I have not been able to >> include all of the patches I intended to. Alas, these improvements are >> still useful. > > Pulled into next/dt I noticed this didn't make it into Linus tree for 4.15 :( Was it because of your question below? > >> ARM: dts: aspeed: Add aliases for UARTs > > Can you explain this one? It looks like you now have aliases for > all uart and i2c entries on all machines, even when they don't > actually expose the ports. The purpose of the aliases is to > only list the ones that are actually usable, so they should normally > go into the board specific .dts files. Sorry for not responding to this at the time. I was on vacation. The idea was to maintain expectations for userspace where they assume the character devices match the numbering of the hardware. So /dev/ttyS4 is always the fifth uart, even when the board only has one or two wired up. If we don't do that, our userspace developers have trouble telling which UART is actually /dev/ttyS0, for example. Cheers, Joel
On Fri, Nov 17, 2017 at 1:27 PM, Joel Stanley <joel@jms.id.au> wrote: > On Fri, Oct 20, 2017 at 8:19 AM, Arnd Bergmann <arnd@arndb.de> wrote: >> On Fri, Oct 6, 2017 at 9:05 AM, Joel Stanley <joel@jms.id.au> wrote: >>> Hello ARM SoC maintainers! >>> >>> Here are some ASPEED device tree updates for v4.15. >>> >>> Sadly our clk driver is still under review, so I have not been able to >>> include all of the patches I intended to. Alas, these improvements are >>> still useful. >> >> Pulled into next/dt > > I noticed this didn't make it into Linus tree for 4.15 :( Scratch that. My mistake, it is there (I was looking at the wrong part of the diffstat). We should still clear up your query about the aliases. > > Was it because of your question below? > >> >>> ARM: dts: aspeed: Add aliases for UARTs >> >> Can you explain this one? It looks like you now have aliases for >> all uart and i2c entries on all machines, even when they don't >> actually expose the ports. The purpose of the aliases is to >> only list the ones that are actually usable, so they should normally >> go into the board specific .dts files. > > Sorry for not responding to this at the time. I was on vacation. > > The idea was to maintain expectations for userspace where they assume > the character devices match the numbering of the hardware. So > /dev/ttyS4 is always the fifth uart, even when the board only has one > or two wired up. > > If we don't do that, our userspace developers have trouble telling > which UART is actually /dev/ttyS0, for example. > > Cheers, > > Joel