From: "maxime.ripard@free-electrons.com" <maxime.ripard@free-electrons.com>
To: Hector Palacios <hector.palacios@digi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
Marek Vasut <marex@denx.de>,
cb@sgoc.de
Subject: Re: MXS persistent bits driver
Date: Thu, 11 Jul 2013 10:24:13 +0200 [thread overview]
Message-ID: <20130711082413.GU11243@lukather> (raw)
In-Reply-To: <51DE5F1A.8010209@digi.com>
[-- 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 --]
next prev parent reply other threads:[~2013-07-11 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-07-11 8:56 ` Hector Palacios
2013-07-11 16:37 ` maxime.ripard
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=20130711082413.GU11243@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=cb@sgoc.de \
--cc=fabio.estevam@freescale.com \
--cc=hector.palacios@digi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
/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