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: Tue, 19 Apr 2011 10:09:54 +0100 [thread overview]
Message-ID: <20110419090954.GH2820@pulham.picochip.com> (raw)
In-Reply-To: <4DAC7C9D.7020304@scram.de>
On Mon, Apr 18, 2011 at 08:02:05PM +0200, Jochen Friedrich wrote:
> Hi Jamie,
>
> >>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.
>
> Not really. The "CS3" register on the simpad device is a 16bit register
> which hat 16 write-only pins and 8 independent read-only pins (no
> direction register, at all). It is implemented using 3 TTL logic
> chips.
Ahh, I misread that bit.
> More information about this strange stuff can be found at:
> http://opensimpad.org/index.php/Wiring#CS3_latch
>
> I'm not sure if handling such a corner-case in the generic driver makes
> sense.
I think I agree with you - it's more like two gpio_chip's using a single
register and I would guess that it isn't too common a scenario.
Jamie
next prev parent reply other threads:[~2011-04-19 9:09 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
2011-04-18 18:02 ` Jochen Friedrich
2011-04-19 9:09 ` Jamie Iles [this message]
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=20110419090954.GH2820@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).