mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabien Lahoudere <fabien.lahoudere@collabora.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Add devices to spidev device tree compatibility list
Date: Thu, 6 Oct 2016 10:01:30 +0200	[thread overview]
Message-ID: <49803380-8bc0-2bfa-1947-e4fcafa15778@collabora.co.uk> (raw)
In-Reply-To: <CAMuHMdVY78gNfq0FyXTEBxCZy7LqqOL3UqumW9P=46NgW1SASA@mail.gmail.com>

Hi,

On 30/09/16 19:35, Geert Uytterhoeven wrote:
> On Fri, Sep 30, 2016 at 12:15 PM, Fabien Lahoudere
> <fabien.lahoudere@collabora.co.uk> wrote:
>> Entries are needed in the spidev ID list to configure configure it from a
>> device tree. Add entries for the following devices:
>
>> - "exar,xra1403" : a GPIO expander
>
> Looks like a suitable target for a drivers/gpio/ driver.
> Datasheet available at
> https://www.exar.com/product/interface/bridges/bridging-solutions/spi-gpio-expanders/xra1403
>

Good idea, however we have to measure impact of this change on the project.

Thanks

Fabien

> 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
>

      reply	other threads:[~2016-10-06  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 10:15 Fabien Lahoudere
2016-09-30 16:08 ` Mark Brown
2016-10-06 14:44   ` [PATCH v2 1/1] Add device " Fabien Lahoudere
2016-10-06 14:49     ` Mark Brown
2016-09-30 17:35 ` [PATCH 1/1] Add devices " Geert Uytterhoeven
2016-10-06  8:01   ` Fabien Lahoudere [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=49803380-8bc0-2bfa-1947-e4fcafa15778@collabora.co.uk \
    --to=fabien.lahoudere@collabora.co.uk \
    --cc=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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®