On Fri, Apr 17, 2020 at 11:06 AM Nicolas Saenz Julienne <nsaenzjulienne@xxxxxxx> wrote: > > Hi Saravana, > > On Fri, 2020-04-17 at 18:54 +0200, Nicolas Saenz Julienne wrote: > > As I'm interested in using this feature to fine-tune Raspberry Pi 4's > > device probe dependencies, I tried to get the board to boot with > > fw_devlink=on. As of today's linux-next the board won't boot with that > > option. I tried to address the underlying issues. > > > > On a semi-related topic, have you looked at vendor specific properties? most of > them create a consumer/supplier relationship, it'd be nice to be able to take > those ones into account as well. I'm on the wall about that. If we take every vendor specific property, this file will explode. Not sure I want to do that. Also, we haven't even finished all the generic bindings. I'm just adding bindings as I get familiar with each of them and I test them on hardware I have lying around before sending it out. So, there's where my focus is right now wrt fw_devlink and DT. I wonder how many of the vendor specific properties do very similar things and got in over time. Maybe they can be made generic? What one did you have in mind? -Saravana
