From: David Brownell <david-b@pacbell.net>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] gpio: Add driver for Anton GPIO controllers
Date: Thu, 26 Aug 2010 15:48:31 -0700 (PDT) [thread overview]
Message-ID: <60847.98364.qm@web180305.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20100826212025.GA3366@oksana.dev.rtsoft.ru>
--- On Thu, 8/26/10, Anton Vorontsov <cbouatmailru@gmail.com> wrote:
> From: Anton Vorontsov <cbouatmailru@gmail.com>
> Subject: Re: [PATCH v2] gpio: Add driver for Anton GPIO controllers
> To: "David Brownell" <david-b@pacbell.net>
> Cc: "Andrew Morton" <akpm@linux-foundation.org>, "Samuel Ortiz" <sameo@linux.intel.com>, "Mark Brown" <broonie@opensource.wolfsonmicro.com>, "David Brownell" <dbrownell@users.sourceforge.net>, "Alan Cox" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
> Date: Thursday, August 26, 2010, 2:20 PM
> On Thu, Aug 26, 2010 at 10:57:33AM
> -0700, David Brownell wrote:
> [...]
>
> You seemed to be fine with meaningless amba-9999
> or dw_abc names, but
NOT meaningless ... when there's actual IP behind
the controller! Which, at first, is what I thought
you were talking about.
> Just kiding, of course. basic_mmio.c works for me.
OK, how about resubmitting? With that name?
Be sure to add a bit of documentation about
the controller requirements ... basically that
it has a register from which all values can be
read, and that either that register can be written,
or there's a pair of set-bit/clear-bit registers
affecting that register and the output pins.
Might be worth mentioning how trivial it is to do
that in hardware like CPLDs/FPGAS/etc, which is
why this handles different word sizes/endianness.
and the expectation that in at least some cases
this will be used with roll-your-own ASIC/FPGA
logic in Verilog or VHDL (yes?).
> I also think it makes sense to drop gpio_ prefix,
> as the driver is already in gpio/ directory.
No, keep it; files move around sometimes, and it's
best if that loses no information.
next prev parent reply other threads:[~2010-08-26 22:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 19:42 [PATCH] gpio: Add generic driver for simple memory mapped controllers Anton Vorontsov
[not found] ` <921098.64431.qm@web180306.mail.gq1.yahoo.com>
2010-08-26 5:17 ` Anton Vorontsov
2010-08-26 16:22 ` David Brownell
2010-08-26 16:48 ` Alan Cox
2010-08-26 17:34 ` David Brownell
2010-08-26 18:36 ` Mark Brown
2010-08-26 21:07 ` Alan Cox
2010-08-26 22:58 ` David Brownell
2010-08-27 0:15 ` Alan Cox
2010-08-26 17:26 ` [PATCH v2] gpio: Add driver for Anton GPIO controllers Anton Vorontsov
2010-08-26 17:57 ` David Brownell
2010-08-26 21:20 ` Anton Vorontsov
2010-08-26 22:48 ` David Brownell [this message]
2010-08-27 15:57 ` [PATCH v3] gpio: Add driver for basic memory-mapped " Anton Vorontsov
2010-08-28 19:08 ` David Brownell
2010-08-29 21:28 ` [PATCH v4] " Anton Vorontsov
2010-08-30 20:23 ` David Brownell
2010-08-31 17:58 ` [PATCH v5] " Anton Vorontsov
2010-08-31 18:21 ` Mark Brown
2010-08-31 20:32 ` David Brownell
2010-09-01 19:52 ` [PATCH v6] " Anton Vorontsov
2010-09-07 14:01 ` [PATCH v7] " Anton Vorontsov
2010-09-21 22:23 ` Anton Vorontsov
2010-09-24 21:45 ` Andrew Morton
2010-09-28 12:40 ` [PATCH v7-fix] gpio: Add driver for basic memory-mapped GPIO controllers (fix) Anton Vorontsov
2010-08-26 18:38 ` [PATCH] gpio: Add generic driver for simple memory mapped controllers Mark Brown
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=60847.98364.qm@web180305.mail.gq1.yahoo.com \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbouatmailru@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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®