On 16/08/2022 10:21, Alexander Stein wrote: >>> >>> So what is the conclusion of this? >>> If using the "family" name there is no way for userspace to see the actual >>> device name rather than the driver name. This might be confusing, >>> especially of both ov9281 and ov9282 are attached to the same platform. >>> The only difference would be the i2c-bus-address. >>> You can also go for ov928x but this is not a real improvement. >> >> I still don't understand. Why user-space cannot see this? I really >> cannot find any trouble... Your 3/7 patch does nothing special here for >> user-space... > > 3/7 itself does nothing for userspace, but 6/7 does, which relies on separate > compatibles in the driver. Ah, that's so confusing... First adding new incomplete device support in patch 3 and then in patch 6 fixing it. 6 and 3 should be squashed. They really do not make any sense being separate and this just brings this unnecessary confusion. I would argue that the binding still should have devices compatible (in one family), but now it is a bit less important. Best regards, Krzysztof
