Hello Christian, hello Andrey, cc: Vladimir Barinov cc: linux-renesas-soc Our team currently has the requirement of adding MOST support to the v4.14-based R-Car3 kernel [1], matching the level of features and interfaces of mld-1.8.0 [2] release. Based on a quick check [3], the mld-1.8.0 release contains 221 non-merge non-mainline commits. It seems like at least some (most?) of them have been reworked during upstreaming and are now part of vanilla, thanks to your efforts. Since you've actively participated in pushing the out-of-tree drivers to mainline, could you please share your gut feeling whether the current mainline state of the MOST subsystem matches the mld-1.8.0 release in terms of features and interfaces? At first glance, such mld-1.8.0 functionalities like "flexible PCM rate support" [4], as well as a number of dim2 sysfs entries [5-8] appear to be missing in v5.1-rc5. Could you please feedback if these have been deliberately dropped or didn't make their way for another reason? What would be your recommendation between going the mld-1.8.0 and going the v5.1-rc5 way for MOST? Best regards, Eugeniu. [1] https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/ [2] https://github.com/microchip-ais/linux/releases/tag/mld-1.8.0 [3] git rev-list --no-merges --count \ $(git merge-base linux/master mld-1.8.0)..mld-1.8.0 221 [4] https://github.com/microchip-ais/linux/commit/8821bad23ff2 ("staging: most: aim-sound: add flexible PCM rate support") [5] https://github.com/microchip-ais/linux/commit/5030f77717a1d7 ("staging: most: dim2: add sysfs property dci/node_position") [6] https://github.com/microchip-ais/linux/commit/3a840d7b504552 ("staging: most: dim2: add sysfs property dci/node_address") [7] https://github.com/microchip-ais/linux/commit/0494ccb4bc5f39 ("staging: most: dim2: add sysfs property dci/ni_state") [8] https://github.com/microchip-ais/linux/commit/3198a5c5f0663 ("staging: most: dim2: add sysfs property dci/mep_eui48")
