From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Pinmux subsystem
Date: Tue, 03 May 2011 15:29:58 -0400 [thread overview]
Message-ID: <26287.1304450998@localhost> (raw)
In-Reply-To: Your message of "Tue, 03 May 2011 19:27:12 +0200." <20110503172712.GE6538@lunn.ch>
On Tue, 03 May 2011 19:27:12 +0200, Andrew Lunn said:
> I can think of two different solutions:
>
> 1) Three functions: uart-3wire, uart-hw-flow, uart-hw-flow-modem. The
> first just has 2 pins, the second 4 and the last 8. The board code
> selects one of these for the serial driver to use.
>
> 2) Three functions: uart-core, uart-hw-flow, uart-mode. The first has
> 2 pins, the second has 2 pins and the last 4 pins. The board code tells
> the driver to use uart-core, plus say uart-hw-flow.
For this second solution, what happens if some bozo selects *only* uart-modem
but not uart-core? If there's a strict ordering (hw-flow requires core, modem
requires both hw-flow and core), it's essentially the same thing as the first
solution. If there's not a strict ordering (i.e you can select uart-modem
without uart-core), you need to come up with sane semantics.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110503/ccb5316f/attachment.sig>
next prev parent reply other threads:[~2011-05-03 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:16 [PATCH 0/4] Pinmux subsystem Linus Walleij
2011-05-02 22:57 ` Russell King - ARM Linux
2011-05-10 21:25 ` Linus Walleij
2011-05-10 21:45 ` Russell King - ARM Linux
2011-05-10 23:15 ` Linus Walleij
2011-05-03 17:27 ` Andrew Lunn
2011-05-03 19:29 ` Valdis.Kletnieks at vt.edu [this message]
2011-05-10 21:42 ` Linus Walleij
2011-05-11 9:50 ` Andrew Lunn
2011-05-12 0:41 ` Linus Walleij
2011-05-12 7:00 ` Andrew Lunn
2011-05-15 13:33 ` Andrew Lunn
2011-05-15 17:50 ` Linus Walleij
2011-05-17 1:57 ` Kyungmin Park
2011-05-18 20:02 ` Linus Walleij
2011-05-18 21:21 ` Mark Brown
2011-05-12 7:44 ` Sascha Hauer
2011-05-12 9:40 ` Tony Lindgren
2011-05-12 14:02 ` Linus Walleij
2011-05-12 21:17 ` Matthieu Castet
2011-05-13 7:05 ` Linus Walleij
2011-05-13 16:03 ` Matthieu CASTET
2011-05-14 7:57 ` Linus Walleij
2011-05-13 9:59 ` Sascha Hauer
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=26287.1304450998@localhost \
--to=valdis.kletnieks@vt.edu \
--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).