> > > > The property should not be in any ACPI specific form or space - > > > > just attach it directly to the tty from ACPI, DT, driver internal > > > > knowledge, PCI id, whatever > > > > > > The only property that comes into mind is _HID/_CID (referring to > > > the ACPI > > > ID) that can be used by userspace to find out type of the device > > > behind the UART port. I don't know what name would be generic enough > > > for the property, though. > > > > We just need a set of type names for the sysfs node I think > > "bluetooth", "ups", "loconet", "serial", "modem", "cir" etc... > > Is it a good idea to introduce uart_device driver in the kernel to fill a new 'ldisc' > member in the uart_device or to load ldisc by default for the corresponding > tty_port? In the ACPI spec, there is no such attribute for the UART devices, OF might easily introduce this. It's hard to add type name or ldisc name directly to the uart_board_info. We can either add driver support for the uart_device to fill this as I mentioned in the first reply or to add a HID -> type name (or ldisc name) matching table in the acpi_uart.c to extract this information for the ACPI enumerated uart_board_info. Best regards/Lv Zheng -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
