linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: elaine.zhang@rock-chips.com, mturquette@baylibre.com,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] ARM: dts: add basic support for Rockchip RK1108 SOC
Date: Tue, 08 Nov 2016 14:20:17 +0100	[thread overview]
Message-ID: <2018991.LuBz7Cl7BQ@diego> (raw)
In-Reply-To: <0516ad0b-bfbe-ec80-fdb6-e118dab3e758@rock-chips.com>

Am Dienstag, 8. November 2016, 20:31:55 schrieb Andy Yan:
> Hi Heiko:
>=20
> On 2016=E5=B9=B411=E6=9C=8804=E6=97=A5 16:00, Heiko Stuebner wrote:
> > Am Donnerstag, 3. November 2016, 20:40:48 CET schrieb Andy Yan:

> >> +=09gic: interrupt-controller@32010000 {
> >> +=09=09compatible =3D "arm,cortex-a15-gic";
> >=20
> > compatible =3D "arm,gic-400"; ?
> >=20
> >> +=09=09interrupt-controller;
> >> +=09=09#interrupt-cells =3D <3>;
> >> +=09=09#address-cells =3D <0>;
> >> +
> >> +=09=09reg =3D <0x32011000 0x1000>,
> >> +=09=09      <0x32012000 0x1000>;
> >=20
> > please provide all 4 register areas and also the interrupt (
>=20
>      I only found 2 register areas in our rockchip linux 3.10 source
> code. And haven't found the interrupt. From the arm,gic bindings, the=

> interrupt property is optional. So am not sure if we
> really need it here.

Devicetree is a hardware description, so it's not a factor if we "need"=
 it but=20
only if it is present in the hardware. And we really want this informat=
ion to=20
be complete, as these additional areas are necessary if someone wants t=
o use=20
the virtualization extensions the cortext-A7 does contain.

The gic is a very standard component and the gic400 used here should de=
finitly=20
have those two additional areas as well as the interrupt.

I think the memory areas are pretty standard and should be for the rk11=
08:
reg =3D <0x32011000 0x1000>,
      <0x32012000 0x1000>,
      <0x32014000 0x2000>,
      <0x32016000 0x2000>;

The TRM talks about 128 SPI and 3 PPI interrupts but the irq-list does =
not=20
contain them, so this seems to be an error in the TRM, as the gic inter=
rupt=20
should be one of those PPI interrupts.


Heiko

  reply	other threads:[~2016-11-08 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 12:26 [PATCH 0/6] Add basic support for support for Rockchip RK1108 SOC Andy Yan
2016-11-03 12:38 ` [PATCH 3/6] clk: rockchip: add clock controller for rk1108 Andy Yan
2016-11-04  2:09   ` Shawn Lin
2016-11-04  7:32   ` Heiko Stuebner
2016-11-03 12:40 ` [PATCH 4/6] ARM: dts: add basic support for Rockchip RK1108 SOC Andy Yan
2016-11-04  8:00   ` Heiko Stuebner
2016-11-08 12:31     ` Andy Yan
2016-11-08 13:20       ` Heiko Stübner [this message]
2016-11-04  8:07   ` Heiko Stuebner
2016-11-12 16:02 ` [PATCH 0/6] Add basic support for " 陈豪

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=2018991.LuBz7Cl7BQ@diego \
    --to=heiko@sntech.de \
    --cc=andy.yan@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=elaine.zhang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.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).