* MXS persistent bits driver
@ 2013-07-11 7:30 Hector Palacios
2013-07-11 7:44 ` Hector Palacios
2013-07-11 8:24 ` maxime.ripard
0 siblings, 2 replies; 6+ messages in thread
From: Hector Palacios @ 2013-07-11 7:30 UTC (permalink / raw)
To: linux-kernel@vger.kernel.org
Cc: fabio.estevam@freescale.com, Marek Vasut,
maxime.ripard@free-electrons.com
Greetings,
Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
(drivers/misc/mxs-persistent.c).
I haven't seen this is supported upstream. Is anybody working on that?
Where would such a driver fit?
Best regards,
--
Hector Palacios
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MXS persistent bits driver
2013-07-11 7:30 MXS persistent bits driver Hector Palacios
@ 2013-07-11 7:44 ` Hector Palacios
2013-07-11 9:12 ` Steffen Trumtrar
2013-07-11 8:24 ` maxime.ripard
1 sibling, 1 reply; 6+ messages in thread
From: Hector Palacios @ 2013-07-11 7:44 UTC (permalink / raw)
To: linux-kernel@vger.kernel.org
Cc: fabio.estevam@freescale.com, Marek Vasut,
maxime.ripard@free-electrons.com, s.trumtrar
On 07/11/2013 09:30 AM, Hector Palacios wrote:
> Greetings,
>
> Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
> (drivers/misc/mxs-persistent.c).
> I haven't seen this is supported upstream. Is anybody working on that?
> Where would such a driver fit?
Adding Steffen Trumtrar, as I came across his patch:
http://permalink.gmane.org/gmane.linux.drivers.devicetree/31370
@Steffen, was there no answer to your questions about these being binary attributes?
Best regards,
--
Hector Palacios
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MXS persistent bits driver
2013-07-11 7:30 MXS persistent bits driver Hector Palacios
2013-07-11 7:44 ` Hector Palacios
@ 2013-07-11 8:24 ` maxime.ripard
2013-07-11 8:56 ` Hector Palacios
1 sibling, 1 reply; 6+ messages in thread
From: maxime.ripard @ 2013-07-11 8:24 UTC (permalink / raw)
To: Hector Palacios
Cc: linux-kernel@vger.kernel.org, fabio.estevam@freescale.com,
Marek Vasut, cb
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
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?
> 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
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MXS persistent bits driver
2013-07-11 8:24 ` maxime.ripard
@ 2013-07-11 8:56 ` Hector Palacios
2013-07-11 16:37 ` maxime.ripard
0 siblings, 1 reply; 6+ messages in thread
From: Hector Palacios @ 2013-07-11 8:56 UTC (permalink / raw)
To: maxime.ripard@free-electrons.com
Cc: linux-kernel@vger.kernel.org, fabio.estevam@freescale.com,
Marek Vasut, cb@sgoc.de
Dear Maxime,
On 07/11/2013 10:24 AM, maxime.ripard@free-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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MXS persistent bits driver
2013-07-11 7:44 ` Hector Palacios
@ 2013-07-11 9:12 ` Steffen Trumtrar
0 siblings, 0 replies; 6+ messages in thread
From: Steffen Trumtrar @ 2013-07-11 9:12 UTC (permalink / raw)
To: Hector Palacios
Cc: linux-kernel@vger.kernel.org, fabio.estevam@freescale.com,
Marek Vasut, maxime.ripard@free-electrons.com
On Thu, Jul 11, 2013 at 09:44:12AM +0200, Hector Palacios wrote:
> On 07/11/2013 09:30 AM, Hector Palacios wrote:
> >Greetings,
> >
> >Linux 2.6.35 had a driver for sysfs access to the MXS persistent bits
> >(drivers/misc/mxs-persistent.c).
> >I haven't seen this is supported upstream. Is anybody working on that?
> >Where would such a driver fit?
>
> Adding Steffen Trumtrar, as I came across his patch:
> http://permalink.gmane.org/gmane.linux.drivers.devicetree/31370
>
> @Steffen, was there no answer to your questions about these being binary attributes?
Hi!
I didn't work on the driver after the v2 and lost track about its whereabouts.
As far as I can see, I didn't get any answers regarding the binary attributes.
Regards,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MXS persistent bits driver
2013-07-11 8:56 ` Hector Palacios
@ 2013-07-11 16:37 ` maxime.ripard
0 siblings, 0 replies; 6+ messages in thread
From: maxime.ripard @ 2013-07-11 16:37 UTC (permalink / raw)
To: Hector Palacios
Cc: linux-kernel@vger.kernel.org, fabio.estevam@freescale.com,
Marek Vasut, cb@sgoc.de
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hi Hector,
On Thu, Jul 11, 2013 at 10:56:42AM +0200, Hector Palacios wrote:
> On 07/11/2013 10:24 AM, maxime.ripard@free-electrons.com wrote:
> >>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!
Oops, sorry, I read your mail too quickly.
But it's true that it would fit quite well in the EEPROM stuff we're
discussing.
Feel free to participate, and I'll let you know if something come out of
it.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-07-11 16:37 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-11 7:30 MXS persistent bits driver Hector Palacios
2013-07-11 7:44 ` Hector Palacios
2013-07-11 9:12 ` Steffen Trumtrar
2013-07-11 8:24 ` maxime.ripard
2013-07-11 8:56 ` Hector Palacios
2013-07-11 16:37 ` maxime.ripard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox