On Sat, Jun 2, 2018 at 10:19 PM, Ramon Fried <ramon.fr...@gmail.com> wrote: > On Sat, Jun 2, 2018 at 9:03 PM, Heinrich Schuchardt <xypron.g...@gmx.de> > wrote: >> On 06/02/2018 06:25 PM, Ramon Fried wrote: >>> Hi Simon, all. >>> >>> I want to port a specific driver from Linux Kernel (Qualcomm smem) >>> which is declared in Linux as platform device. >>> The implementation is very specific and It doesn't fall into any >>> defined uclass id. >>> I still want to use the dm framework, what's the approach taken on >>> these kind of things ? >>> Is it possible to create a generic uclass id ? >> >> Hello Ramon, >> >> a major benefit of the driver model is that drivers are selected via the >> device tree. >> >> In Linux the driver is in drivers/soc. Wouldn't it make sense to create >> a minimal uclass for platform devices in drivers/soc on U-Boot? >> >> drivers/ram/ram-uclass.c shows what a minimal uclass looks like. >> The identifier has to be added in include/dm/uclass-id.h. >> >> Best regards >> >> Heinrich > Thanks for the comment Heinrich. > My initial intention was to place the driver under drivers/soc and I > do thing that > creating a UCLASS_PLATFORM make sense, acutally, it's exaclt what I'm > suggesting > in a different name. > The thing is that there's no apperent ops that I think will suit all > the platform drivers as they're different in nature. > So, I don't see any requirement to create a platform_uclass.c file. > > Thanks, > Ramon.
Added some initial contributors to uclass for comments. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
