LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: arun.ramamurthy@broadcom.com, a.zummo@towertech.it,
rtc-linux@googlegroups.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, sbranden@broadcom.com,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
rjui@broadcom.com, Arun Ramamurthy <arunrama@broadcom.com>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
bcm-kernel-feedback-list@broadcom.com, galak@codeaurora.org,
grant.likely@linaro.org
Subject: Re: [PATCHv1] rtc: bcm-iproc: Add support for Broadcom iproc rtc
Date: Tue, 16 Dec 2014 20:42:56 +0100 [thread overview]
Message-ID: <7947905.aK8KkUx4sY@wuerfel> (raw)
In-Reply-To: <1418757750-3628-1-git-send-email-arun.ramamurthy@broadcom.com>
On Tuesday 16 December 2014 11:22:30 arun.ramamurthy@broadcom.com wrote:
> + rtc: iproc_rtc@0x03026000 {
> + compatible = "brcm,iproc-rtc";
> + reg = spru_bbl: <0x03026000 0xC>,
> + crmu_pwr_good_status: <0x0301C02C 0x14>,
> + crmu_bbl_auth: <0x03024C74 0x8>;
> + interrupts = spru_rtc_periodic: <GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>,
> + spru_alarm: <GIC_SPI 133 IRQ_TYPE_LEVEL_HIGH>;
The reg properties look really random, could it be that the registers
are really part of some other device that contains multiple functions?
Also, what do you use the labels for?
Arnd
next prev parent reply other threads:[~2014-12-16 19:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 19:22 arun.ramamurthy
2014-12-16 19:42 ` Arnd Bergmann [this message]
2014-12-16 20:05 ` Arun Ramamurthy
2014-12-16 20:19 ` Arnd Bergmann
2014-12-16 20:27 ` Ray Jui
2014-12-16 21:54 ` Arun Ramamurthy
2014-12-17 14:31 ` Arnd Bergmann
2015-02-12 22:17 ` Arun Ramamurthy
2015-03-04 22:21 ` Arnd Bergmann
2015-03-04 22:40 ` Arun Ramamurthy
2015-03-04 22:50 ` Arnd Bergmann
2015-03-04 22:53 ` Arun Ramamurthy
2015-03-04 22:58 ` Arnd Bergmann
2015-03-11 20:00 ` Arun Ramamurthy
2015-03-11 20:31 ` Arnd Bergmann
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=7947905.aK8KkUx4sY@wuerfel \
--to=arnd@arndb.de \
--cc=a.zummo@towertech.it \
--cc=arun.ramamurthy@broadcom.com \
--cc=arunrama@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sbranden@broadcom.com \
--subject='Re: [PATCHv1] rtc: bcm-iproc: Add support for Broadcom iproc rtc' \
/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
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).