On Tue, Apr 20, 2021 at 12:15:40PM CDT, Mark Brown wrote:
On Tue, Apr 20, 2021 at 11:40:24AM -0500, Zev Weiss wrote:
On Tue, Apr 20, 2021 at 11:13:18AM CDT, Mark Brown wrote:
> I already suggested writing a driver or drivers that represent the
> hardware you have, that advice remains. It's
On Tue, Apr 20, 2021 at 11:40:24AM -0500, Zev Weiss wrote:
> On Tue, Apr 20, 2021 at 11:13:18AM CDT, Mark Brown wrote:
> > I already suggested writing a driver or drivers that represent the
> > hardware you have, that advice remains. It's hard to follow what you
> > were trying to say with your
On Tue, Apr 20, 2021 at 11:13:18AM CDT, Mark Brown wrote:
On Tue, Apr 20, 2021 at 10:19:04AM -0500, Zev Weiss wrote:
Mark, do you have any further input on what a viable approach might look
like?
I already suggested writing a driver or drivers that represent the
hardware you have, that
On Tue, Apr 20, 2021 at 10:19:04AM -0500, Zev Weiss wrote:
> Mark, do you have any further input on what a viable approach might look
> like?
I already suggested writing a driver or drivers that represent the
hardware you have, that advice remains. It's hard to follow what you
were trying to
On Tue, Apr 20, 2021 at 05:52:16AM CDT, Guenter Roeck wrote:
On 4/20/21 12:06 AM, Zev Weiss wrote:
On Tue, Apr 20, 2021 at 01:00:25AM CDT, Guenter Roeck wrote:
On 4/19/21 10:50 PM, Zev Weiss wrote:
[ ... ]
I had a glance at the enclosure driver; it looks pretty geared toward SES-like things
On 4/20/21 12:06 AM, Zev Weiss wrote:
> On Tue, Apr 20, 2021 at 01:00:25AM CDT, Guenter Roeck wrote:
>> On 4/19/21 10:50 PM, Zev Weiss wrote:
>> [ ... ]
>>
>>> I had a glance at the enclosure driver; it looks pretty geared toward
>>> SES-like things (drivers/scsi/ses.c being its only usage I can
On Tue, Apr 20, 2021 at 01:00:25AM CDT, Guenter Roeck wrote:
On 4/19/21 10:50 PM, Zev Weiss wrote:
[ ... ]
I had a glance at the enclosure driver; it looks pretty geared toward SES-like things
(drivers/scsi/ses.c being its only usage I can see in the kernel at the moment) and while
it could
On 4/19/21 10:50 PM, Zev Weiss wrote:
[ ... ]
> I had a glance at the enclosure driver; it looks pretty geared toward
> SES-like things (drivers/scsi/ses.c being its only usage I can see in the
> kernel at the moment) and while it could perhaps be pressed into working for
> this it seems like
On Mon, Apr 19, 2021 at 10:36:48PM CDT, Guenter Roeck wrote:
On Mon, Apr 19, 2021 at 08:29:53PM -0500, Zev Weiss wrote:
On Tue, Mar 30, 2021 at 02:38:10PM CDT, Guenter Roeck wrote:
> On Tue, Mar 30, 2021 at 07:02:00PM +0100, Mark Brown wrote:
> > On Tue, Mar 30, 2021 at 12:56:56PM -0500, Zev
On Mon, Apr 19, 2021 at 08:29:53PM -0500, Zev Weiss wrote:
> On Tue, Mar 30, 2021 at 02:38:10PM CDT, Guenter Roeck wrote:
> > On Tue, Mar 30, 2021 at 07:02:00PM +0100, Mark Brown wrote:
> > > On Tue, Mar 30, 2021 at 12:56:56PM -0500, Zev Weiss wrote:
> > >
> > > > Okay, to expand a bit on the
On Tue, Mar 30, 2021 at 02:38:10PM CDT, Guenter Roeck wrote:
On Tue, Mar 30, 2021 at 07:02:00PM +0100, Mark Brown wrote:
On Tue, Mar 30, 2021 at 12:56:56PM -0500, Zev Weiss wrote:
> Okay, to expand a bit on the description in my initial message -- we've
> got a single chassis with multiple
On Tue, Mar 30, 2021 at 07:02:00PM +0100, Mark Brown wrote:
> On Tue, Mar 30, 2021 at 12:56:56PM -0500, Zev Weiss wrote:
>
> > Okay, to expand a bit on the description in my initial message -- we've
> > got a single chassis with multiple server boards and a single manager board
> > that handles,
On Tue, Mar 30, 2021 at 12:56:56PM -0500, Zev Weiss wrote:
> Okay, to expand a bit on the description in my initial message -- we've
> got a single chassis with multiple server boards and a single manager board
> that handles, among other things, power control for the servers.
> The manager board
On Tue, Mar 30, 2021 at 12:42:21PM CDT, Mark Brown wrote:
On Tue, Mar 30, 2021 at 12:19:29PM -0500, Zev Weiss wrote:
On Tue, Mar 30, 2021 at 06:22:54AM CDT, Mark Brown wrote:
> On Tue, Mar 30, 2021 at 03:34:16AM -0700, Guenter Roeck wrote:
> > (and I don't know if the userspace consumer code
On Tue, Mar 30, 2021 at 12:19:29PM -0500, Zev Weiss wrote:
> On Tue, Mar 30, 2021 at 06:22:54AM CDT, Mark Brown wrote:
> > On Tue, Mar 30, 2021 at 03:34:16AM -0700, Guenter Roeck wrote:
> > > (and I don't know if the userspace consumer code is appropriate - you
> > > might want to check with the
On Tue, Mar 30, 2021 at 06:22:54AM CDT, Mark Brown wrote:
On Tue, Mar 30, 2021 at 03:34:16AM -0700, Guenter Roeck wrote:
(and I don't know if the userspace consumer code is appropriate - you
might want to check with the regulator maintainer on that).
It's not, you should never see this in a
On Tue, Mar 30, 2021 at 03:34:16AM -0700, Guenter Roeck wrote:
> (and I don't know if the userspace consumer code is appropriate - you
> might want to check with the regulator maintainer on that).
It's not, you should never see this in a production system.
> > first attempt at this ran into
On 3/30/21 1:17 AM, Zev Weiss wrote:
>
> Hello,
>
> I'm working on a board that has a handful of LM25066 PMICs controlling
> the power supply to various devices, and I'd like to have both the
> existing hwmon sensor functionality as well as userspace power on/off
> control, which does not
Hello,
I'm working on a board that has a handful of LM25066 PMICs controlling
the power supply to various devices, and I'd like to have both the
existing hwmon sensor functionality as well as userspace power on/off
control, which does not currently seem to be available (other than via
'i2cset
19 matches
Mail list logo
