[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51DE734A.80206@digi.com>
Date: Thu, 11 Jul 2013 10:56:42 +0200
From: Hector Palacios <hector.palacios@...i.com>
To: "maxime.ripard@...e-electrons.com" <maxime.ripard@...e-electrons.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"fabio.estevam@...escale.com" <fabio.estevam@...escale.com>,
Marek Vasut <marex@...x.de>, "cb@...c.de" <cb@...c.de>
Subject: Re: MXS persistent bits driver
Dear Maxime,
On 07/11/2013 10:24 AM, maxime.ripard@...e-electrons.com wrote:
> Hi Hector,
>
> On Thu, Jul 11, 2013 at 09:30:34AM +0200, Hector Palacios wrote:
>> Greetings,
>>
>> Linux 2.6.35 had a driver for sysfs access to the MXS persistent
>> bits (drivers/misc/mxs-persistent.c).
>
> Freescale's 2.6.35 I suspect, right?
Yes.
>> I haven't seen this is supported upstream. Is anybody working on that?
>> Where would such a driver fit?
>
> Christoph Baumann recently started porting the Freescale's driver to
> newer release.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/181569.html
>
> This needs quite a lot of work, but it's ongoing.
>
> Also, about where to put such a driver, I started a discussion about
> this last week. Mostly, that would be part of MTD, from what is out of
> the discussion so far.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/182002.html
I was talking about RTC persistent bits, not OTP bits, but I they also fit in your
EEPROM like model. I like it!
Best regards,
--
Hector Palacios
--
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