public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: srinivas.kandagatla@linaro•org (Srinivas Kandagatla)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/3] nvmem: imx-ocotp: Add i.MX6 OCOTP driver
Date: Fri, 07 Aug 2015 10:11:23 +0100	[thread overview]
Message-ID: <55C4763B.4090508@linaro.org> (raw)
In-Reply-To: <1438933597.3638.5.camel@pengutronix.de>


On 07/08/15 08:46, Philipp Zabel wrote:
>>> Nobody. I had initially copied the code that actually senses the fuses,
>>> > >but since this happens during power-on reset anyway (all values are
>>> > >stored in shadow registers), I didn't see the point and dropped it for
>>> > >now.
>>> > >The shadow registers are clocked directly by the ungated ipg_root clock.
>> >
>> >So, are you planning to drop the clocks property from the bindings too?
> The gated clock input exists and is needed for the full functionality of
> the device (writing and re-sensing fuses).
Thanks for clarification.

--srini
  It should be in the device
> tree even if the linux driver doesn't implement writing.
>
> regards
> Philipp
>

  reply	other threads:[~2015-08-07  9:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 13:02 [PATCH 1/3] nvmem: Add i.MX6 OCOTP device tree binding documentation Philipp Zabel
2015-08-04 13:02 ` [PATCH 2/3] nvmem: imx-ocotp: Add i.MX6 OCOTP driver Philipp Zabel
2015-08-06 16:20   ` Srinivas Kandagatla
2015-08-06 16:28     ` Philipp Zabel
2015-08-06 19:36       ` Srinivas Kandagatla
2015-08-07  7:46         ` Philipp Zabel
2015-08-07  9:11           ` Srinivas Kandagatla [this message]
2015-08-04 13:02 ` [PATCH 3/3] ARM: imx6: Add clock to OCOTP node Philipp Zabel
2015-08-06 16:12 ` [PATCH 1/3] nvmem: Add i.MX6 OCOTP device tree binding documentation Srinivas Kandagatla
2015-08-06 16:33   ` Philipp Zabel
2015-08-06 19:34     ` Srinivas Kandagatla

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=55C4763B.4090508@linaro.org \
    --to=srinivas.kandagatla@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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