> > > 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... Hi, Mika How is this handled in the i2c? I think for OF, type can be filled as "bluetooth", "ups" and etc. But for ACPI, the type field of the i2c_board_info is filled as hid in your patches. Is this right? Maybe I just need to add struct acpi_dev_node to the uart_board_info and let OF guys add of_node to it. What's your opinion? Best regards -Lv -- 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
