Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1546803
| From | Geert Uytterhoeven <geert@linux-m68k.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] iio: misc: add a generic regulator driver |
| Date | 2016-12-23 11:10 +0100 |
| Message-ID | <sRuXw-5wu-29@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <sISFI-1NU-41@gated-at.bofh.it> <sJa9z-4PB-3@gated-at.bofh.it> <sKjNw-2Bb-11@gated-at.bofh.it> <sLmpX-1th-13@gated-at.bofh.it> <sNCqB-75R-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Lars,
On Mon, Dec 12, 2016 at 6:15 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> On 12/06/2016 12:12 PM, Bartosz Golaszewski wrote:
>> We're already using libiio to read the measured data from the power
>> monitor, that's why we'd like to use the iio framework for
>> power-cycling the devices as well. My question is: would bridging the
>> regulator framework be the right solution? Should we look for
>> something else? Bridge the GPIO framework instead?
>
> I wouldn't necessaries create bridge, but instead just use the GPIO
> framework directly.
>
> We now have the GPIO chardev interface which meant to be used to support
> application specific logic that control the GPIOs, but where you don't want
> to write a kernel driver.
>
> My idea was to add GPIOs and GPIO chips as high level object inside libiio
> that can be accessed through the same context as the IIO devices. Similar to
> the current IIO API you have a API for gpios that allows to enumerate the
> GPIO devices and their pins as well as modify the pin state.
That would mean libiio has access to all GPIOs, allowing a remote person
to not only control through iiod the GPIOs for industrial control, but also the
GPIOs not intended for export, right?
Having a separate GPIO switch driver avoids that, as DT (or some other means)
can be used to specify and label the GPIOs for IIO use.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] iio: misc: add a generic regulator driver Lars-Peter Clausen <lars@metafoo.de> - 2016-12-12 18:20 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Bartosz Golaszewski <bgolaszewski@baylibre.com> - 2016-12-13 15:30 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Linus Walleij <linus.walleij@linaro.org> - 2016-12-28 14:10 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Geert Uytterhoeven <geert@linux-m68k.org> - 2016-12-23 11:10 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Lars-Peter Clausen <lars@metafoo.de> - 2016-12-23 12:40 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Geert Uytterhoeven <geert@linux-m68k.org> - 2016-12-23 14:00 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Jonathan Cameron <jic23@jic23.retrosnub.co.uk> - 2016-12-24 11:50 +0100
Re: [PATCH] iio: misc: add a generic regulator driver Linus Walleij <linus.walleij@linaro.org> - 2016-12-28 14:10 +0100
csiph-web