From: Roberto Fichera <kernel@tekno-soft.it>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: /sys/fsl_otp patch for linux-fslc v4.4 kernel, where?
Date: Wed, 17 Feb 2016 14:52:50 +0100 [thread overview]
Message-ID: <56C47B32.3040309@tekno-soft.it> (raw)
In-Reply-To: <CAOMZO5ATEWEpuDQcYsTU2DqOJpcCOk3nZVU3gZW5neGKfw3g2g@mail.gmail.com>
On 02/17/2016 01:05 PM, Fabio Estevam wrote:
Ciao Fabio,
> On Mon, Feb 8, 2016 at 2:22 PM, Roberto Fichera <kernel@tekno-soft.it> wrote:
>> Hi All,
>>
>> where I can get the /sys/fsl_opt filesystem patch for fslc kernel v4.4? I need writable support.
> Not a meta-freescale related issue, but anyway, 4.4 has support for this since:
I've already this enabled, but doesn't have write support
>
> commit 3edba6b47e4265948db3a77a0137157c033d69e2
> Author: Philipp Zabel <p.zabel@pengutronix.de>
> Date: Wed Sep 30 13:55:47 2015 +0100
>
> nvmem: imx-ocotp: Add i.MX6 OCOTP driver
>
> This driver handles the i.MX On-Chip OTP Controller found in
> i.MX6Q/D, i.MX6S/DL, i.MX6SL, and i.MX6SX SoCs. Currently it
> just returns the values stored in the shadow registers.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
next prev parent reply other threads:[~2016-02-17 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:22 /sys/fsl_otp patch for linux-fslc v4.4 kernel, where? Roberto Fichera
2016-02-17 12:05 ` Fabio Estevam
2016-02-17 13:52 ` Roberto Fichera [this message]
2016-02-17 14:14 ` Fabio Estevam
2016-02-17 14:22 ` Roberto Fichera
2016-02-17 15:43 ` Roberto Fichera
2016-02-17 15:46 ` Fabio Estevam
2016-02-17 15:50 ` Fabio Estevam
2016-02-17 15:53 ` Roberto Fichera
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 11:25 Colin Wernham
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=56C47B32.3040309@tekno-soft.it \
--to=kernel@tekno-soft.it \
--cc=festevam@gmail.com \
--cc=meta-freescale@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.