From: Peter Korsgaard <peter@korsgaard.com>
To: Srinivas Neeli <srinivas.neeli@xilinx.com>
Cc: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<michal.simek@xilinx.com>, <sgoud@xilinx.com>,
<shubhraj@xilinx.com>, <srinivas.neeli@amd.com>,
<neelisrinivas18@gmail.com>, <devicetree@vger.kernel.org>,
<linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <git@xilinx.com>
Subject: Re: [PATCH V8 2/3] rtc: zynqmp: Updated calibration value
Date: Tue, 14 Jun 2022 13:39:35 +0200 [thread overview]
Message-ID: <878rpzwk20.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220613125836.523449-2-srinivas.neeli@xilinx.com> (Srinivas Neeli's message of "Mon, 13 Jun 2022 18:28:35 +0530")
>>>>> "Srinivas" == Srinivas Neeli <srinivas.neeli@xilinx.com> writes:
> As per RTC spec default calibration value is 0x7FFF.
> Signed-off-by: Srinivas Neeli <srinivas.neeli@xilinx.com>
> ---
> Changes in V8
> -None, just swapped 2/3 and 3/3 patches from V7.
> Changes in V7:
> -New patch
> -TRM not updated yet, Internal design document contains 0x7FFF as
> default value. TRM Will update in next release.
Maybe add this to the commit message so it is clear where this comes
from. If possible specific the TRM version number that will contain the
fix.
Other than that:
Acked-by: Peter Korsgaard <peter@korsgaard.com>
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2022-06-14 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:58 [PATCH V8 1/3] dt-bindings: rtc: zynqmp: Add clock information Srinivas Neeli
2022-06-13 12:58 ` [PATCH V8 2/3] rtc: zynqmp: Updated calibration value Srinivas Neeli
2022-06-14 11:39 ` Peter Korsgaard [this message]
2022-06-13 12:58 ` [PATCH V8 3/3] rtc: zynqmp: Add calibration set and get support Srinivas Neeli
2022-06-14 20:51 ` [PATCH V8 1/3] dt-bindings: rtc: zynqmp: Add clock information Rob Herring
2022-06-18 0:38 ` Krzysztof Kozlowski
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=878rpzwk20.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=neelisrinivas18@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sgoud@xilinx.com \
--cc=shubhraj@xilinx.com \
--cc=srinivas.neeli@amd.com \
--cc=srinivas.neeli@xilinx.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
all inboxes | Powered by JetHome®