public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
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>,
	"maxime.ripard@free-electrons.com"
	<maxime.ripard@free-electrons.com>
Subject: Re: MXS persistent bits driver
Date: Thu, 11 Jul 2013 11:12:44 +0200	[thread overview]
Message-ID: <20130711091244.GC31410@pengutronix.de> (raw)
In-Reply-To: <51DE624C.1080208@digi.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 |

  reply	other threads:[~2013-07-11  9:12 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 [this message]
2013-07-11  8:24 ` maxime.ripard
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=20130711091244.GC31410@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --cc=fabio.estevam@freescale.com \
    --cc=hector.palacios@digi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=maxime.ripard@free-electrons.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