From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 2.6.40 2/3] ARM:simpad: Cleanup CS3 accessors.
Date: Mon, 18 Apr 2011 17:49:11 +0100 [thread overview]
Message-ID: <20110418164911.GF2820@pulham.picochip.com> (raw)
In-Reply-To: <4DAC4C2E.3050604@scram.de>
On Mon, Apr 18, 2011 at 04:35:26PM +0200, Jochen Friedrich wrote:
> Hi Jamie,
>
> >>- register CS3 as GPIO controller with 24 pins
> >> (16 output only and 8 input only).
> >
> >I think the basic-mmio-gpio driver (drivers/gpio/basic_mmio_gpio.c)
> >should cover the GPIO controller portion of this (including the
> >shadowing etc).
>
> I'll have a look at this. Last time I checked, a single virtual address
> for a wite-only/read-only register pair was not supported, but this
> might have changed.
You should just be able to specify a single resource named "dat" and
you'll be good to go. The current driver in mainline detects the number
of GPIO's based on the register width (so it would detect 32 GPIO's in
your case), but I have some patches posted on lkml that allow this to be
overridden. These patches also add support for direction registers
which it looks like you may need.
Jamie
next prev parent reply other threads:[~2011-04-18 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 13:00 [PATCHv2 2.6.40 0/3] ARM: simpad: Add support for GPIO attached hardware Jochen Friedrich
2011-04-18 13:00 ` [PATCHv2 2.6.40 1/3] ARM:simpad: Add ucb1x00 GPIO definitions and register GPIO Jochen Friedrich
2011-04-18 13:00 ` [PATCHv2 2.6.40 2/3] ARM:simpad: Cleanup CS3 accessors Jochen Friedrich
2011-04-18 13:47 ` Jamie Iles
2011-04-18 14:35 ` Jochen Friedrich
2011-04-18 14:46 ` Henning Heinold
2011-04-18 16:49 ` Jamie Iles [this message]
2011-04-18 18:02 ` Jochen Friedrich
2011-04-19 9:09 ` Jamie Iles
2011-04-18 13:00 ` [PATCHv2 2.6.40 3/3] ARM:simpad: add GPIO based device definitions Jochen Friedrich
2011-04-19 13:52 ` Dmitry Artamonow
2011-04-19 14:46 ` Jochen Friedrich
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=20110418164911.GF2820@pulham.picochip.com \
--to=jamie@jamieiles.com \
--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).