On Fri, 2017-03-31 at 15:31 +0200, Greg Kroah-Hartman wrote: > DEVICE_ATTR_RW()? > > And why random sysfs files for a uart? Where have you documented > these? We should stick a file somewhere in Documentation I suppose or at least put that in a comment blob at the head of the file. FYI: The VUART is basically two UART 'front ends' connected by their FIFO (no actual serial line in between). One is on the BMC side (management controller) and one is on the host CPU side. It allows the BMC to provide to the host a "UART" that pipes into the BMC itself and can then be turned by the BMC into a network console of some sort for example. This driver is for the BMC side. The sysfs files allow the BMC userspace which owns the system configuration policy, to specify at what IO port and interrupt number the host side will appear to the host on the Host <-> BMC LPC bus. It could be different on a different system (though most of them use 3f8/4). Cheers, Ben. -- 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