linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC V3 2/3] mxs: add driver for ocotp in i.MX23 and i.MX28
Date: Fri, 9 Jan 2015 11:02:07 +0100	[thread overview]
Message-ID: <20150109100206.GE27845@ulmo> (raw)
In-Reply-To: <54AE8D45.7050805@imgtec.com>

On Thu, Jan 08, 2015 at 10:59:33AM -0300, Ezequiel Garcia wrote:
> Hi Stefan, Arnd,
> 
> (I'm trimming the Cc list and adding Thierry and Maxime to the loop):
> 
> On 11/06/2014 04:47 PM, Arnd Bergmann wrote:
> [..]
> >>
> >> i don't have a answer to this question, but how about changing fsl_ocotp driver
> >> to driver/soc/mxs/fuse with a similiar binary interface like the tegra ones.
> >>
> >> Does it make sense to you?
> > 
> > I haven't looked at the drivers, so I don't know if the tegra interface
> > is any better or worse than the others. Changing everyone to have the same
> > interface is definitely a good idea, but of course only if the unified
> > interface is a good one ;-)
> > 
> 
> I'm in the process of finding a suitable upstream path for a new eFuse driver
> for fuses used on Imagination Technologies SoCs.
> 
> This was our last proposal, which follows Tegra's work:
> 
> http://www.spinics.net/lists/devicetree/msg59246.html
> 
> However, Arnd was reluctant to take yet another efuse driver under drivers/soc
> and proposed instead to try to find a unified API. We've had numerous fuse
> drivers (tegra, sunxi, imx and img) appearing, so his concern certainly makes
> sense.
> 
> I've talked to Arnd on IRC and we agreed to create a new directory
> drivers/efuse. As a first step we would just move the tegra driver,
> and add the new drivers (img on my side, and possibly mxs on Stefan's).
> Perhaps we would also pull the sunxi_sid driver as well.
> 
> Having the drivers together would allow us to come up with a unified API
> as follow up work.
> 
> How does this sound? If you have no objections to this, I can go ahead and
> try to prepare some RFCs.

No objections from me. Adding Peter and linux-tegra for visibility.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150109/e448848c/attachment.sig>

  parent reply	other threads:[~2015-01-09 10:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 10:32 [PATCH RFC V3 0/3] mxs: add ocotp support for i.MX23 and i.MX28 Stefan Wahren
2014-10-18 10:32 ` [PATCH RFC V3 1/3] mxs: add binding for fsl ocotp Stefan Wahren
2014-10-18 10:32 ` [PATCH RFC V3 2/3] mxs: add driver for ocotp in i.MX23 and i.MX28 Stefan Wahren
2014-10-20 14:44   ` Arnd Bergmann
2014-10-20 15:32     ` Stefan Wahren
2014-10-20 17:32       ` Arnd Bergmann
2014-10-28 17:17     ` Ezequiel Garcia
2014-10-28 19:13       ` Arnd Bergmann
2014-11-06 19:25         ` Stefan Wahren
2014-11-06 19:47           ` Arnd Bergmann
2015-01-08 13:59             ` Ezequiel Garcia
2015-01-08 14:53               ` Stefan Wahren
2015-01-08 20:47               ` Stefan Wahren
2015-01-09 10:02               ` Thierry Reding [this message]
2015-01-12  9:21               ` Maxime Ripard
2014-11-07 19:14           ` Ezequiel Garcia
2014-11-07 19:44             ` Stefan Wahren
2014-10-29  7:14       ` Stefan Wahren
2014-10-18 10:32 ` [PATCH RFC V3 3/3] mxs: enable ocotp for " Stefan Wahren
2015-02-25 20:18 ` [PATCH RFC V3 0/3] mxs: add ocotp support " Jörg Krause
2015-02-25 20:27 ` Jörg Krause
2015-02-26  7:11   ` Stefan Wahren
2015-02-26  8:02     ` Jörg Krause

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=20150109100206.GE27845@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).