[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDEA3BF.6020507@gmail.com>
Date: Tue, 06 Dec 2011 17:22:39 -0600
From: Rob Herring <robherring2@...il.com>
To: Wolfram Sang <w.sang@...gutronix.de>
CC: Wolfgang Denk <wd@...x.de>, devicetree-discuss@...ts.ozlabs.org,
Heiko Schocher <hs@...x.de>, linux-kernel@...r.kernel.org,
Vitaly Bordug <vbordug@...mvista.com>,
linux-watchdog@...r.kernel.org
Subject: Re: [PATCH] drivers, char: add U-Boot bootcount driver
On 12/06/2011 04:06 PM, Wolfram Sang wrote:
>
>>> bootcount itself is not a device. It is a feature of certain devices. And that
>>> needs to be implemented; possibly generic enough that it can work for register
>>> based, i2c based, and so forth, accesses.
>>
>> If "boot counter" is not a good name for such a device, then what name
>> would you suggest?
>
> None.
>
>> Or do you think a counter (which can be implemented in a number of
>> different ways, depending on hardware specifics) is not a device?
>
> Yes.
>
>> What would be such a device, then?
>
> "maxim,ds1338"
>
> Please have a look at the devicetree.org-wiki-page I just mentioned:
>
> http://devicetree.org/Device_Tree_Usage
>
Perhaps fs/pstore would be a good choice for the user space interface
(defining a new file bootcount). This can support any arbitrary backing
device although pretty much only ACPI is implemented.
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists