Hi Svyatoslav, and Hervé, and all, > > > > > So, if you want upstream supported I2C hot-plugging, you need to wait > > > > > for Luca's and Herve's work being accepted. Or provide a superior > > > > > solution. Or, if you want, join the ride. You already have experience in > > > > > this field (and hardware plus use case), you would be a very welcome > > > > > contributor, I would say. > > > > > > > > Agreed. > > > > > > > > What really slows things down is when there is only 1 user of a new > > > > binding. Too many times have I accepted one only for the 2nd user to > > > > show up right after accepting it and wanting something different. So > > > > now I just require more than 1 user and it is on the submitter(s) to do > > > > that. After all, it is their itch, not mine. For completeness, let me emphasize the above paragraphs again. > > No new advancements. I moved on a prerequisite: Having support for addon > > format in dtb in order to have support for a list of exported symbols > > resolution when an dtb is applied on a live devicetree. Well, I would consider advancements in prerequisites also advancements. > > Anyway, the v3 series [1] need to be updated and a new iteration need to be > > sent. Also, same operations need to be done on the SPI version [2]. Hervé, is that the next planned step or are there prerequisites needed still? > Rob, Wolfram, since the DT Addon framework is not mature yet, may > i2c-hotplug-gpio be accepted in some form? Maybe a staging driver or I vote against it. Accepting intermediate solutions will slow down the proper solution even more. > with notes that ABI may be changed and are unstable or maybe as a > device specific driver only for transformers like > "asus-transformer-dock" etc? Which kernel are you using? Can't you use your driver downstream instead of upstream unless Herve's work is usable? Happy hacking, Wolfram