From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] rtc: armada38x: Add the device tree binding documentation
Date: Thu, 15 Jan 2015 08:50:07 +0100 [thread overview]
Message-ID: <54B7712F.2090509@free-electrons.com> (raw)
In-Reply-To: <20150114202252.457d328e@free-electrons.com>
Hi Thomas,
On 14/01/2015 20:22, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> On Wed, 14 Jan 2015 18:39:11 +0100, Gregory CLEMENT wrote:
>
>> +Required properties:
>> +- compatible : Should be "marvell,armada-380-rtc"
>> +- reg: physical base address of the controller and length of memory
>> + mapped region, associated to the reg-name "rtc". The other entry is
>> + related to the interrupt control from the SoC, associated to the
>> + reg-name "soc-interrupt".
>
> soc-interrupt or...
I changed all the name from soc-interrupt to soc-int except here.
I will fix it.
>
>> +- reg-names: names of the mapped memory regions listed in regs
>> + property in the same order: "rtc" and "soc-int".
>
> soc-int ?
>
>> +rtc at a3800 {
>> + compatible = "marvell,armada-380-rtc";
>> + reg = <0xa3800 0x20>, <0x184a0 0x0c>;
>
> Any reason to use <0x184A0 0xC> instead of <0x184A8 0x4> ? According to
> the datasheet, there is only this 184A8 register for RTC stuff.
Yes but according to the code I saw there were other registers related to the RTC
from 0x184A0. Even if we don't use them now I prefer having an accurate mapping from
the beginning for avoiding using negative offset as we needed to do in the past.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-01-15 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 17:39 [PATCH v2 0/5] Add a new RTC driver for recent mvebu SoCs Gregory CLEMENT
2015-01-14 17:39 ` [PATCH v2 1/5] rtc: armada38x: Add the device tree binding documentation Gregory CLEMENT
2015-01-14 19:22 ` Thomas Petazzoni
2015-01-15 7:50 ` Gregory CLEMENT [this message]
2015-01-15 8:24 ` Thomas Petazzoni
2015-01-15 8:25 ` Gregory CLEMENT
2015-01-14 17:39 ` [PATCH v2 2/5] drivers/rtc/rtc-armada38x: Add a new RTC driver for recent mvebu SoCs Gregory CLEMENT
2015-01-14 20:55 ` Arnaud Ebalard
2015-01-15 9:51 ` Gregory CLEMENT
2015-01-14 17:39 ` [PATCH v2 3/5] MAINTAINERS: Add the RTC driver for the Armada38x Gregory CLEMENT
2015-01-14 17:39 ` [PATCH v2 4/5] ARM: mvebu: add Device Tree description of RTC on Armada 38x Gregory CLEMENT
2015-01-14 17:39 ` [PATCH v2 5/5] ARM: mvebu: enable Armada 38x RTC driver in mvebu_v7_defconfig Gregory CLEMENT
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=54B7712F.2090509@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).