Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1741415
| From | Sudeep Holla <sudeep.holla@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init |
| Date | 2017-09-28 12:50 +0200 |
| Message-ID | <uuEye-7SR-15@gated-at.bofh.it> (permalink) |
| References | <uuEyd-7SR-7@gated-at.bofh.it> |
| Organization | ARM |
On 28/09/17 11:44, Sudeep Holla wrote: > Hi Rob, Arnd, > > There's a push to place all firmware related device node under > /firmware/ node. However all the associated drivers are dealing with > device creation in their own ways. For example, qcom_scm, optee and > meson-sm drivers deal with the node in their own way. The SCMI drivers > I am about to add also needs to do the same. This small series is to > make it generic so that all the users of /firmware/ node need not > repeat the same. > > There was concern that /firmware in DT is fit for /sys/firmware in sysfs. > IMO anything exposed to userspace from such firmware interface must > be in "/sys/firmware", but I don't see any issue with kernel handling > them as platform device/driver internally. > Please ignore this, something went wrong and patches were not delivered, have reposted it separately. -- Regards, Sudeep
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init Sudeep Holla <sudeep.holla@arm.com> - 2017-09-28 12:50 +0200 Re: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init Sudeep Holla <sudeep.holla@arm.com> - 2017-09-28 12:50 +0200
csiph-web