linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rojhalat Ibrahim <imr@rtschenk.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Grant Likely <grant.likely@linaro.org>,
	Mark Brown <broonie@kernel.org>, Gerhard Sittig <gsi@denx.de>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs
Date: Mon, 07 Jul 2014 18:12:32 +0200	[thread overview]
Message-ID: <3862339.n8jYhAjBf6@pcimr> (raw)
In-Reply-To: <CACRpkdYBCHnCRe3sJ5Uf62ZUjZ23wM54nKs6_QwWyswHUsWaEw@mail.gmail.com>

On Monday 07 July 2014 17:23:34 Linus Walleij wrote:
> On Mon, Jun 16, 2014 at 3:51 PM, Rojhalat Ibrahim <imr@rtschenk.de> wrote:
> 
> > Introduce new functions gpiod_set_array & gpiod_set_raw_array to the consumer
> > interface which allow setting multiple outputs with just one function call.
> > Also add an optional set_multiple function to the driver interface. Without an
> > implementation of that function in the chip driver outputs are set
> > sequentially.
> 
> Yes this looks good.
> 
> Except for one thing I mentioned quite early  I think:
> 
> no users!
> 

I'm pretty sure you did _not_ mention this before.

> How am I supposed to test this?
> 
> I wanted to see a patch also switching the one in-kernel thing that
> really needs this switched over to using this functionality.
> 
> That means, a patch to drivers/i2c/busses/i2c-gpio.c
> to set scl+sda in one go, for example.
> 
> Or a similar patch to drivers/spi/spi-gpio.c I guess?
> 
> Something that makes sense. As a bonus you get to rewrite
> one of these drivers to use GPIO descriptors ;)
> 
> This is not a hard wall, but I highly suspect that there must be
> some driver using this if you want to implement it, right? And the
> two mentioned drivers will be easy to use to test the feature on
> a lot of platforms.
> 

I'll take a look at those drivers and hopefully come back with an extended
patch set.

   Rojhalat


  reply	other threads:[~2014-07-07 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 13:51 [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs Rojhalat Ibrahim
2014-06-21  7:08 ` Alexandre Courbot
2014-06-21 20:24 ` Mark Brown
2014-07-07 15:23 ` Linus Walleij
2014-07-07 16:12   ` Rojhalat Ibrahim [this message]
2014-07-09 10:17     ` Linus Walleij
2014-07-30  9:12       ` Rojhalat Ibrahim
2014-07-30 10:41         ` Mark Brown
2014-07-30 11:04           ` Rojhalat Ibrahim
2014-07-31  2:35         ` Alexandre Courbot
2014-07-31  7:12           ` Gerhard Sittig
2014-07-31  8:42             ` Rojhalat Ibrahim
2014-08-06 12:45               ` Gerhard Sittig
2014-08-06 19:39                 ` Mark Brown
2014-08-07  9:52                 ` Rojhalat Ibrahim
2014-08-29  5:21               ` Linus Walleij
2014-08-29  8:15                 ` Wolfram Sang

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=3862339.n8jYhAjBf6@pcimr \
    --to=imr@rtschenk.de \
    --cc=broonie@kernel.org \
    --cc=gnurou@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=gsi@denx.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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;
as well as URLs for NNTP newsgroup(s).