On Tue, Mar 28, 2017 at 06:18:03PM +0200, Stefan Wahren wrote: > Am 27.03.2017 um 22:30 schrieb Rob Herring: > > On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren <stefan.wahren@xxxxxxxx> wrote: > >> This is the serdev binding for the QCA7000 UART driver (Ethernet over UART). > >> > >> Signed-off-by: Stefan Wahren <stefan.wahren@xxxxxxxx> > >> --- > >> > >> According to this binding are still some questions: > >> > >> Where should be the optional hardware flow control defined (at master or slave side)? > > Probably should be in the slave side. We already have uart-has-rtscts > > and rts/cts-gpios for the UART. Those mean we have RTS/CTS, but not > > necessarily that we want to enable them. > > > > In many cases, the driver may know what it needs. > > Like all the other UART settings the hardware flow control can be > configured in the QCA7000 firmware and the driver can't detect it. > > Property suggestion for the slave side: > > use-rtscts Okay. > >> Is it okay to have two bindings (qca-qca7000-spi and qca-qca7000-uart) or should they be merged? > > Are they mutually-exclusive or both are used at the same time? > > They are mutually-exclusive because they use the same pins. > > > What > > are the dependencies between the interfaces? > > Except they uses the same pins of the QCA7000, i can't see any dependency. I think they should be a single doc. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
