Hi Ricardo, On Mon, Jun 11, 2018 at 01:52:16PM +0200, Ricardo Ribalda Delgado wrote: > There are some situations where it is interesting to load/remove serdev > devices dynamically, like during board bring-up or when we are > developing a new driver or for devices that are neither described via > ACPI or device tree. First of all, this would be more appropriately labeled an RFC as this is far from being in a mergeable state. Besides some implementation issues, we need to determine if this approach is at all viable. Second, I wonder how you tested this given that this series breaks RX (and write-wakeup signalling) for serial ports (patch 19/24)? Third, and as Marcel already suggested, you need to limit your scope here. Aim at ten patches or so, and use a representative serdev driver as an example of the kind of driver updates that would be needed. It also looks like some patches should be squashed (e.g. the ones introducing new fields and the first one actually using them). > This implementation allows the creation of serdev devices via sysfs, > in a similar way as the i2c bus allows sysfs instantiation [1]. Note that this is a legacy interface and not necessarily something that new interfaces should be modelled after. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
