linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] Convert some ARM platforms to basic-mmio-gpio
Date: Mon, 11 Apr 2011 17:17:53 +0200	[thread overview]
Message-ID: <BANLkTi=bur3zPkQ45+StkPxLm_YMyw9uaw@mail.gmail.com> (raw)
In-Reply-To: <1302522502-24381-1-git-send-email-jamie@jamieiles.com>

2011/4/11 Jamie Iles <jamie@jamieiles.com>:

> The basic-mmio-gpio driver has been extended in
> <http://marc.info/?l=linux-kernel&m=130252092900804&w=2> to support a
> larger wider of controllers and this series converts the ARM platforms
> that do not implement I/O muxing in the GPIO driver or use the .to_irq
> method of gpio_chip to use the driver.
>
> Jamie Iles (5):
> ?gemini: convert to basic-mmio-gpio
> ?sa1100: convert to basic-mmio-gpio
> ?w90x900: convert to basic-mmio-gpio
> ?iop: convert to basic-mmio-gpio
> ?mxc: convert to basic-mmio-gpio

For all of these, maybe you can
  select GPIO_BASIC_GPIO

In their mach-xxx/Kconfig so that the driver gets compiled-in by default?

Further the basic_mmio_gpio.c driver looks a bit dangerous: it only uses
__raw_* accessors for the GPIO registers, I'd very much like to replace that
with the non-__raw* versions if this is to have any generic impact.

The raw accessors can get stuck in things like write buffers and the like
IIRC, they usually won't so you don't notice first, then you start getting
all kind of real strange bugs.

Yours,
Linus Walleij

  parent reply	other threads:[~2011-04-11 15:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 11:48 [RFC PATCH 0/5] Convert some ARM platforms to basic-mmio-gpio Jamie Iles
2011-04-11 11:48 ` [RFC PATCH 1/5] gemini: convert " Jamie Iles
2011-04-12 14:37   ` Anton Vorontsov
2011-04-12 15:01     ` Jamie Iles
2011-04-13 11:46     ` Sergei Shtylyov
2011-04-11 11:48 ` [RFC PATCH 2/5] sa1100: " Jamie Iles
2011-04-11 16:00   ` Jamie Iles
2011-04-11 11:48 ` [RFC PATCH 3/5] w90x900: " Jamie Iles
2011-04-11 14:27   ` Wan ZongShun
2011-06-10 12:50     ` Jamie Iles
2011-04-11 11:48 ` [RFC PATCH 4/5] iop: " Jamie Iles
2011-04-11 11:48 ` [RFC PATCH 5/5] mxc: " Jamie Iles
2011-04-11 13:43 ` [RFC PATCH 0/5] Convert some ARM platforms " Uwe Kleine-König
2011-04-11 13:52   ` Jamie Iles
2011-04-11 14:23     ` Uwe Kleine-König
2011-04-11 14:33       ` Jamie Iles
2011-04-11 14:49         ` Uwe Kleine-König
2011-04-11 15:13           ` Jamie Iles
2011-04-12 15:06           ` Anton Vorontsov
2011-04-11 15:17 ` Linus Walleij [this message]
2011-04-11 15:21   ` Jamie Iles

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='BANLkTi=bur3zPkQ45+StkPxLm_YMyw9uaw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).