From: Philippe Reynes <tremyfr@gmail.com>
To: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>
Cc: shawn.guo@linaro.org, kernel@pengutronix.de,
linux@arm.linux.org.uk, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rtc-linux@googlegroups.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
fabio.estevam@freescale.com
Subject: [rtc-linux] Re: [PATCH 1/2] rtc: mxc: add a second clock
Date: Mon, 18 May 2015 23:57:19 +0200 [thread overview]
Message-ID: <555A603F.7000005@gmail.com> (raw)
In-Reply-To: <5559CC85.5040703@melag.de>
Hi Enrico,
On 18/05/15 13:27, Enrico Weigelt, metux IT consult wrote:
> Am 16.05.2015 um 00:35 schrieb Philippe Reynes:
>> The mxc RTC needs two clocks, one for the input
>> reference, and one for the IP. But this driver
>> was only using one clock (for the reference).
>> This patch add the second clock (for the IP).
>
>
> Does this also apply to MX53, or just MX21 ?
I don't found this rtc on mx53 manual. The mx53 seems to use rtc-imxdi.c.
So, I think it's just for mx21.
Regards,
Philippe
=20
> greetings,
> --
> Enrico Weigelt, metux IT consult
> +49-151-27565287
> MELAG Medizintechnik oHG Sitz Berlin Registergericht AG Charlottenburg HR=
A 21333 B
>
> Wichtiger Hinweis: Diese Nachricht kann vertrauliche oder nur f=C3=BCr ei=
nen begrenzten Personenkreis bestimmte Informationen enthalten. Sie ist aus=
schlie=C3=9Flich f=C3=BCr denjenigen bestimmt, an den sie gerichtet worden =
ist. Wenn Sie nicht der Adressat dieser E-Mail sind, d=C3=BCrfen Sie diese =
nicht kopieren, weiterleiten, weitergeben oder sie ganz oder teilweise in i=
rgendeiner Weise nutzen. Sollten Sie diese E-Mail irrt=C3=BCmlich erhalten =
haben, so benachrichtigen Sie bitte den Absender, indem Sie auf diese Nachr=
icht antworten. Bitte l=C3=B6schen Sie in diesem Fall diese Nachricht und a=
lle Anh=C3=A4nge, ohne eine Kopie zu behalten.
> Important Notice: This message may contain confidential or privileged inf=
ormation. It is intended only for the person it was addressed to. If you ar=
e not the intended recipient of this email you may not copy, forward, discl=
ose or otherwise use it or any part of it in any form whatsoever. If you re=
ceived this email in error please notify the sender by replying and delete =
this message and any attachments without retaining a copy.
s
--=20
--=20
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.
---=20
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 e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-05-18 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 22:35 [rtc-linux] [PATCH 0/2] add dt support for mxc rtc Philippe Reynes
2015-05-15 22:35 ` [rtc-linux] [PATCH 1/2] rtc: mxc: add a second clock Philippe Reynes
2015-05-18 11:27 ` [rtc-linux] " Enrico Weigelt, metux IT consult
2015-05-18 21:57 ` Philippe Reynes [this message]
2015-05-19 5:27 ` Shawn Guo
2015-05-28 11:57 ` Alexandre Belloni
2015-06-04 21:08 ` Philippe Reynes
2015-06-04 22:17 ` Alexandre Belloni
2015-05-15 22:35 ` [rtc-linux] [PATCH 2/2] rtc: mxc: add support of device tree Philippe Reynes
2015-05-28 12:06 ` [rtc-linux] " Alexandre Belloni
2015-06-04 21:26 ` Philippe Reynes
2015-06-04 22:22 ` 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=555A603F.7000005@gmail.com \
--to=tremyfr@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--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=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.org \
--cc=weigelt@melag.de \
/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