Hi Andreas, On 04/07/2015 12:51 PM, Andreas Färber wrote: > Am 07.04.2015 um 18:30 schrieb Maxime Coquelin: >> This drivers adds support to the STM32 USART controller, which is a >> standard serial driver. >> >> Tested-by: Chanwoo Choi <cw00.choi@xxxxxxxxxxx> >> Reviewed-by: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> >> Signed-off-by: Maxime Coquelin <mcoquelin.stm32@xxxxxxxxx> >> --- >> drivers/tty/serial/Kconfig | 17 + >> drivers/tty/serial/Makefile | 1 + >> drivers/tty/serial/stm32-usart.c | 735 +++++++++++++++++++++++++++++++++++++++ >> include/uapi/linux/serial_core.h | 3 + >> 4 files changed, 756 insertions(+) >> create mode 100644 drivers/tty/serial/stm32-usart.c > [...] >> diff --git a/drivers/tty/serial/stm32-usart.c b/drivers/tty/serial/stm32-usart.c >> new file mode 100644 >> index 0000000..4adc430 >> --- /dev/null >> +++ b/drivers/tty/serial/stm32-usart.c > [...] >> +#define DRIVER_NAME "stm32-usart" >> +#define STM32_SERIAL_NAME "ttyS" > > I'm surprised no one has complained about ttyS yet. Doesn't that need to > be unique, such as ttySTM (efm32 uses ttyefm), to avoid clashes between > serial drivers? ttyS was exclusive to the 8250 driver, I thought. As long as this platform doesn't support 8250 h/w, I don't care; and by the time this platform is ready for multiconfig, I'll have ttyS coexistence fixed. Regards, Peter Hurley -- 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
