From: Wolfram Sang <w.sang@pengutronix.de>
To: Austin Boyle <Austin.Boyle@aviatnet.com>
Cc: rtc-linux@googlegroups.com,
David Anderson <danders.dev@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Joakim Tjernlund <Joakim.Tjernlund@transmode.se>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: ds1307: generalise ram size and offset
Date: Thu, 3 Nov 2011 00:06:52 +0100 [thread overview]
Message-ID: <20111102230652.GA10696@pengutronix.de> (raw)
In-Reply-To: <1320267555.3000.13.camel@pc786-ubu.gnet.global.vpn>
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
On Thu, Nov 03, 2011 at 09:59:15AM +1300, Austin Boyle wrote:
> From: Austin Boyle <Austin.Boyle@aviatnet.com>
>
> This patch generalises NVRAM to support RAM with other size and offset, such
> as the 64 bytes of SRAM on the MCP7941x.
>
> Cc: Wolfram Sang <w.sang@pengutronix.de>
> Cc: David Anderson <danders.dev@gmail.com>
> Cc: Alessandro Zummo <a.zummo@towertech.it>
> Cc: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
> Signed-off-by: Austin Boyle <Austin.Boyle@aviatnet.com>
Looks good to me in general, with one exception.
> ---
> this patch is based on Wolfram Sang's tree:
> git://git.pengutronix.de/git/wsa/linux-2.6.git ds1307
>
> patch depends on:
> rtc: ds1307: comment and format cleanup 21af5f7bd6
> rtc: ds1307: simplify irq setup code 8c63e03627
> rtc: ds1307: refactor chip_desc table e246db081d
> rtc: add initial support for mcp7941x parts e69bba2d3a
>
> --- a/drivers/rtc/rtc-ds1307.c 2011-10-10 11:22:22.674690998 +1300
> +++ b/drivers/rtc/rtc-ds1307.c 2011-11-03 09:13:06.662159569 +1300
> @@ -104,10 +104,12 @@ enum ds_type {
>
> struct ds1307 {
> u8 offset; /* register's offset */
> + u16 ram_offset;
> + u16 ram_size;
> u8 regs[11];
> enum ds_type type;
> unsigned long flags;
> -#define HAS_NVRAM 0 /* bit 0 == sysfs file active */
> +#define HAS_RAM 0 /* bit 0 == sysfs file active */
Why the rename from NVRAM to RAM everywhere? While it doesn't matter much for
most occurences...
> -static struct bin_attribute nvram = {
> +static struct bin_attribute ram = {
> .attr = {
> - .name = "nvram",
> + .name = "ram",
> .mode = S_IRUGO | S_IWUSR,
> },
... here it will break userspace.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-11-02 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 20:59 Austin Boyle
2011-11-02 23:06 ` Wolfram Sang [this message]
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=20111102230652.GA10696@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Austin.Boyle@aviatnet.com \
--cc=Joakim.Tjernlund@transmode.se \
--cc=a.zummo@towertech.it \
--cc=danders.dev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®