From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Philippe Reynes <tremyfr@gmail.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Shawn Guo <shawn.guo@linaro.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [rtc-linux] Re: [PATCH v3 5/6] dt-binding: document the binding for mxc rtc
Date: Mon, 22 Jun 2015 21:27:02 +0200 [thread overview]
Message-ID: <20150622192702.GC19203@piout.net> (raw)
In-Reply-To: <CAL_JsqKQzC=aSuORGhsuPQ0Ciha2JVpYOGU91M2iHaG8RousnQ@mail.gmail.com>
On 22/06/2015 at 08:59:06 -0500, Rob Herring wrote :
> What about newer versions with the secure functionality. IIRC, that
> was in MX31 and later.
>
Aren't those covered by the snvs driver?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-06-22 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 17:12 [rtc-linux] [PATCH v3 0/6] add device tree support for mxc rtc Philippe Reynes
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 1/6] imx31: add a second rtc clock Philippe Reynes
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 2/6] imx35: define two clocks for rtc Philippe Reynes
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 3/6] rtc: mxc: use a second rtc clock Philippe Reynes
2015-06-29 9:23 ` [rtc-linux] " Alexandre Belloni
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 4/6] rtc: mxc: add support of device tree Philippe Reynes
2015-06-29 9:24 ` [rtc-linux] " Alexandre Belloni
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 5/6] dt-binding: document the binding for mxc rtc Philippe Reynes
2015-06-22 13:59 ` [rtc-linux] " Rob Herring
2015-06-22 19:27 ` Alexandre Belloni [this message]
2015-06-20 17:12 ` [rtc-linux] [PATCH v3 6/6] apf27: dt: add support of internal rtc Philippe Reynes
2015-06-29 9:26 ` [rtc-linux] " Alexandre Belloni
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=20150622192702.GC19203@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.org \
--cc=tremyfr@gmail.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