From: David Brownell <david-b@pacbell.net>
To: Mike Rapoport <mike@compulab.co.il>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
raph@8d.com
Subject: Re: [PATCH] rtc-v3020: add ability to access v3020 chip with GPIOs
Date: Tue, 3 Mar 2009 13:08:29 -0800 [thread overview]
Message-ID: <200903031308.29933.david-b@pacbell.net> (raw)
In-Reply-To: <49ABCEB3.6090100@compulab.co.il>
On Monday 02 March 2009, Mike Rapoport wrote:
> +
> +#define V3020_CS 0
> +#define V3020_WR 1
> +#define V3020_RD 2
> +#define V3020_IO 3
> +
> +struct v3020_gpio {
> + const char *name;
> + unsigned int gpio;
> +};
> +
> +static struct v3020_gpio v3020_gpio[] = {
> + { "RTC CS", 0 },
> + { "RTC WR", 0 },
> + { "RTC RD", 0 },
> + { "RTC IO", 0 },
> +};
After Andrew's fault path cleanup it looks OK, but I see
no point to that GPIO struct with the name. You know the
name based on the position, if you ever need one. Take
that away, and you can add my ack.
Also, best not to have a single static struct; there's
no need to add a driver restriction that there be only
one of these chips in a system.
- Dave
next prev parent reply other threads:[~2009-03-03 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 11:40 [PATCH] rtc-v3020: add ability to access v3020 chip with GPIOs Mike Rapoport
2009-03-02 11:40 ` [PATCH] rtc-v3020: coding style cleanup Mike Rapoport
2009-03-02 11:43 ` Alessandro Zummo
2009-03-02 11:40 ` [PATCH] rtc-v3020: add ability to access v3020 chip with GPIOs Mike Rapoport
2009-03-02 11:47 ` Alessandro Zummo
2009-03-02 12:18 ` Mike Rapoport
2009-03-03 21:08 ` David Brownell [this message]
2009-03-08 10:03 ` Mike Rapoport
2009-03-19 21:25 ` David Brownell
2009-03-02 22:36 ` Andrew Morton
2009-03-03 6:16 ` Mike Rapoport
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=200903031308.29933.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alessandro.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=raph@8d.com \
--cc=rtc-linux@googlegroups.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