[PATCH linux 2/6] hwmon: occ: Add sysfs interface
Andrew Jeffery
andrew at aj.id.au
Wed Jan 4 11:25:05 AEDT 2017
On Tue, 2017-01-03 at 19:13 -0500, Brad Bishop wrote:
> > > > On Jan 3, 2017, at 7:06 PM, Joel Stanley <joel at jms.id.au> wrote:
> >
> > On Wed, Jan 4, 2017 at 10:49 AM, Brad Bishop
> > > > <bradleyb at fuzziesquirrel.com> wrote:
> > > What if the driver is built into the kernel? Is there such a thing as module only drivers?
> >
> > Our kernel is build with module loading disabled at present.
> >
> > modprobing the driver when userspace is ready is a neat hack that we
> > could use for now. However, the driver will need a mechanism that
>
> Do you happen to know if ‘a mechanism’ is something that needs to be invented or
> if Linux already has something?
I spoke with Rusty about this and by his response there's no existing
"event-bus" mechanism. His suggestions for the problem were:
1. As userspace is coordinating the host power-on, do the modprobe in
userspace
2. Push the power-on logic into the kernel so it can trigger hotplug
events to probe the drivers, and expose a power-{on,off}/{soft,hard}-
reboot interface to userspace.
Andrew
>
> > tells it to bind to the hardware when it becomes available. The same
> > mechanism would be useful for the fsi driver to initiate a scan and
> > bind it's client drivers.
> >
> > Cheers,
> >
> > Joel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170104/0187fa99/attachment.sig>
More information about the openbmc
mailing list