From: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>
To: Philippe Reynes <tremyfr@gmail.com>, <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>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<fabio.estevam@freescale.com>
Subject: Re: [PATCH 1/2] rtc: mxc: add a second clock
Date: Mon, 18 May 2015 13:27:01 +0200 [thread overview]
Message-ID: <5559CC85.5040703@melag.de> (raw)
In-Reply-To: <1431729330-7625-2-git-send-email-tremyfr@gmail.com>
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 ?
greetings,
--
Enrico Weigelt, metux IT consult
+49-151-27565287
MELAG Medizintechnik oHG Sitz Berlin Registergericht AG Charlottenburg HRA 21333 B
Wichtiger Hinweis: Diese Nachricht kann vertrauliche oder nur für einen begrenzten Personenkreis bestimmte Informationen enthalten. Sie ist ausschließlich für denjenigen bestimmt, an den sie gerichtet worden ist. Wenn Sie nicht der Adressat dieser E-Mail sind, dürfen Sie diese nicht kopieren, weiterleiten, weitergeben oder sie ganz oder teilweise in irgendeiner Weise nutzen. Sollten Sie diese E-Mail irrtümlich erhalten haben, so benachrichtigen Sie bitte den Absender, indem Sie auf diese Nachricht antworten. Bitte löschen Sie in diesem Fall diese Nachricht und alle Anhänge, ohne eine Kopie zu behalten.
Important Notice: This message may contain confidential or privileged information. It is intended only for the person it was addressed to. If you are not the intended recipient of this email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you received this email in error please notify the sender by replying and delete this message and any attachments without retaining a copy.
next prev parent reply other threads:[~2015-05-18 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 22:35 [PATCH 0/2] add dt support for mxc rtc Philippe Reynes
2015-05-15 22:35 ` [PATCH 1/2] rtc: mxc: add a second clock Philippe Reynes
2015-05-18 11:27 ` Enrico Weigelt, metux IT consult [this message]
2015-05-18 21:57 ` Philippe Reynes
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 ` [PATCH 2/2] rtc: mxc: add support of device tree Philippe Reynes
2015-05-28 12:06 ` 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=5559CC85.5040703@melag.de \
--to=weigelt@melag.de \
--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=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;
as well as URLs for NNTP newsgroup(s).