mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zev Weiss <zev@bewilderbeest.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2 2/2] misc: Add power-efuse driver
Date: Wed, 13 Apr 2022 02:03:38 -0700	[thread overview]
Message-ID: <YlaR6kfhQHd3b8Ay@hatter.bewilderbeest.net> (raw)
In-Reply-To: <YlUFuoFPveAYRQDm@kroah.com>

On Mon, Apr 11, 2022 at 09:53:14PM PDT, Greg Kroah-Hartman wrote:
>On Mon, Apr 11, 2022 at 03:09:53PM -0700, Zev Weiss wrote:
>>
>> Ping...Mark (or Liam?), any thoughts on an appropriate path forward on this?
>
>Make it a regular regulator driver please.
>

The existing userspace-consumer regulator driver does provide some of 
the functionality I'm looking for (the on/off switch), and I think would 
be pretty easy to extend to provide the rest of it as well.  When I 
previously proposed using it as such though, Mark stated quite firmly 
that that wasn't going to fly [0]; this approach was my attempt at 
implementing a generic, abstracted mechanism as he had suggested later 
in that thread, though I haven't gotten any further feedback from him on 
what he thought of it.

If he's had a change of heart and would be open to the 
userspace-consumer driver taking on a bit of new functionality I'd be 
happy to go that route though.

[0] https://lore.kernel.org/openbmc/20210330174221.GJ4976@sirena.org.uk/


Thanks,
Zev


      reply	other threads:[~2022-04-13  9:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  1:18 [PATCH v2 0/2] " Zev Weiss
2022-03-08  1:18 ` [PATCH v2 1/2] dt-bindings: Add power-efuse binding Zev Weiss
2022-03-11 15:24   ` Rob Herring
2022-03-11 21:48     ` Zev Weiss
2022-03-12  0:08       ` Rob Herring
2022-03-12  0:39         ` Zev Weiss
2022-03-08  1:18 ` [PATCH v2 2/2] misc: Add power-efuse driver Zev Weiss
2022-03-08  7:06   ` Greg Kroah-Hartman
2022-03-08  7:45     ` Zev Weiss
2022-03-08  7:07   ` Greg Kroah-Hartman
2022-03-08  8:23     ` Zev Weiss
2022-04-11 22:09       ` Zev Weiss
2022-04-12  4:53         ` Greg Kroah-Hartman
2022-04-13  9:03           ` Zev Weiss [this message]

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=YlaR6kfhQHd3b8Ay@hatter.bewilderbeest.net \
    --to=zev@bewilderbeest.net \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    /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

all inboxes | Powered by JetHome®