From: Stefan Wahren <stefan.wahren@i2se.com>
To: Fabio Estevam <festevam@gmail.com>, Oleksij Rempel <ore@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sascha Hauer <kernel@pengutronix.de>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/3] nvmem: dt: document SNVS LPGPR binding
Date: Mon, 19 Jun 2017 16:02:29 +0200 [thread overview]
Message-ID: <f83cae78-4422-ce07-7a39-92ba70be8de6@i2se.com> (raw)
In-Reply-To: <CAOMZO5Dd243VXCYBigTcFJ2aF4prZhWYtOuw7Z86M4X6nEXB=A@mail.gmail.com>
Am 19.06.2017 um 14:52 schrieb Fabio Estevam:
> Hi Stefan,
>
> On Mon, Jun 19, 2017 at 7:58 AM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>
>> do you know how the clock "lp_ipg_clk_s" should be handled?
> As per the Reference Manual there is no CCM gating bits for this clock.
I was only surprised that there is no clock handling in the driver.
Sorry, about that noise.
next prev parent reply other threads:[~2017-06-19 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 12:57 [PATCH v5 0/3] nvmem: upstream snvs_lpgpr driver Oleksij Rempel
2017-06-09 12:57 ` [PATCH v5 1/3] nvmem: dt: document SNVS LPGPR binding Oleksij Rempel
2017-06-09 14:59 ` Stefan Wahren
2017-06-19 6:06 ` Oleksij Rempel
2017-06-19 10:58 ` Stefan Wahren
2017-06-19 12:52 ` Fabio Estevam
2017-06-19 14:02 ` Stefan Wahren [this message]
2017-06-14 7:35 ` Guy Shapiro
2017-06-09 12:57 ` [PATCH v5 2/3] nvmem: add snvs_lpgpr driver Oleksij Rempel
2017-06-09 15:01 ` Stefan Wahren
2017-06-19 14:33 ` Oleksij Rempel
2017-06-09 12:57 ` [PATCH v5 3/3] ARM: dts: imx6qdl.dtsi: add "fsl,imx6q-snvs-lpgpr" node Oleksij Rempel
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=f83cae78-4422-ce07-7a39-92ba70be8de6@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=o.rempel@pengutronix.de \
--cc=ore@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®