All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: GPIO Centralized Control Daemon
Date: Sun, 17 Sep 2017 18:10:48 -0400	[thread overview]
Message-ID: <1505686248.29751.8.camel@fuzziesquirrel.com> (raw)
In-Reply-To: <CAO=notwfcPJiEjtQ_n1jxFQpwtPwtvPisOZpiV64DbVHrk0qfQ@mail.gmail.com>

On Sun, 2017-09-17 at 14:49 -0700, Patrick Venture wrote:
> 
> Ahh - yeah, sorry, I didn't explain the entire use-case path
> initially.  I assumed gpio-gated sensors were just a normal thing. 

No problemo!

> I'll reach out and see if this should go into the adc driver or the
> iio-hwmon.  Since those are the paths that are involved.  The sensor
> itself it plugged into the aspeed adc, and then controlled by a
> gpio.  My initial thought is the adc should be configured to know if
> such things are required for its sensors, so that iio-hwmon wouldn't
> need to know.

Excellent.  Thx Patrick.

> That's what I'm thinking, if I can put it in the driver as something
> that can be configured - then perhaps that'll be a neater solution. 
> Although, depending on how it gets added, it might be too platform
> specific.  I'm using an Aspeed part, but I know there are other
> manufacturers, and if this type of arrangement exists elsewhere, more
> drivers will need modification in-lieu of a solution at the highest
> level.  I see the value in both approaches.

I can too.  Adding to that I'd like for our standard operating
procedure in general to be that we work with upstream Linux to set the
kernel direction and then we react to that to meet OpenBMCs needs.

-brad

  reply	other threads:[~2017-09-17 22:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 22:02 GPIO Centralized Control Daemon Patrick Venture
2017-09-14 22:29 ` Rick Altherr
2017-09-14 22:55   ` Patrick Venture
2017-09-16 22:12 ` Brad Bishop
2017-09-17  4:22   ` Patrick Venture
2017-09-17 16:26     ` Brad Bishop
2017-09-17 16:39       ` Patrick Venture
2017-09-17 17:33         ` Brad Bishop
2017-09-17 21:04           ` Patrick Venture
2017-09-17 21:38             ` Brad Bishop
2017-09-17 21:49               ` Patrick Venture
2017-09-17 22:10                 ` Brad Bishop [this message]
2017-09-18  7:32                 ` Andrew Jeffery
2017-09-18 14:52                   ` Patrick Venture
2017-09-18  7:07     ` Andrew Jeffery

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=1505686248.29751.8.camel@fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.