From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Guenter Roeck <linux@roeck-us.net>,
Eddie James <eajames@linux.vnet.ibm.com>
Cc: linux-hwmon@vger.kernel.org, Joel Stanley <joel@jms.id.au>
Subject: Re: hwmon driver with misc interface
Date: Wed, 11 Jul 2018 12:54:32 +1000 [thread overview]
Message-ID: <42a49baad45d67b280c8605c0e22d9fd1ab008aa.camel@kernel.crashing.org> (raw)
In-Reply-To: <5437584ecc9db993bbba1cc81f70e241a5507023.camel@kernel.crashing.org>
On Wed, 2018-07-11 at 09:26 +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2018-07-10 at 13:44 -0700, Guenter Roeck wrote:
> > > > Yes, I think that would be more appropriate.
> > >
> > > This still won't work, since then we wouldn't have those attributes
> > > available in the P8 version of the driver (which has no fsi-occ driver). In
> > > addition, how would the poll response data get from the hwmon driver to the
> > > fsi-occ driver? Yet another interface? Seems awkward.
> > >
> > > How about debugfs? We don't really mind where the attributes are, just that
> > > the data is exposed somewhere...
> > >
> >
> > You are essentially confirming that using sysfs attributes would not be
> > appropriate. I have no problems with using debugfs; you have a free ride
> > there.
>
> I disagree.
>
> If the attributes are used for the normal operation of the system then
> they should be in sysfs.
>
> A system should be able to function normally without debugfs mounted.
>
> Those attributes are about monitoring proper operations of the OCC
> right ? Or are there other things here ? I don't see any reason why
> those couldn't hang off the device sysfs node...
Eddie: If Guenter really strongly objects to that handful of attributes
being in the hwmon device itself, then we have two alternatives we can
consider:
- Not upstream P8 :-)
- Use a similar 2-level driver for P8/i2c, which additionally
provides the ability to create a p8 variant of /dev/occ if needed.
I don't like the way the P8 backend works today anyway. It basically
uses i2c to do SCOMs which will race/clash with anything else in the
system trying to do the same.
We should ideally have a pure "SCOM" driver providing a P8 /dev/scom
and lay on top of that a platform device for OCC like we do with
sbefifo.
That said, I'm also not too fussed about leaving P8 behind as legacy
and not upstreaming it.
Cheers,
Ben.
>
> Cheers,
> Ben.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-11 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 23:31 hwmon driver with misc interface Benjamin Herrenschmidt
2018-05-22 1:36 ` Benjamin Herrenschmidt
2018-07-08 23:30 ` Guenter Roeck
2018-07-09 1:05 ` Benjamin Herrenschmidt
2018-07-09 1:26 ` Guenter Roeck
2018-07-09 6:04 ` Benjamin Herrenschmidt
2018-07-09 6:37 ` Guenter Roeck
2018-07-09 6:45 ` Benjamin Herrenschmidt
2018-07-10 20:04 ` Eddie James
2018-07-10 20:44 ` Guenter Roeck
2018-07-10 23:26 ` Benjamin Herrenschmidt
2018-07-11 2:54 ` Benjamin Herrenschmidt [this message]
2018-07-11 4:17 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42a49baad45d67b280c8605c0e22d9fd1ab008aa.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=eajames@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox