Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: "Alim Akhtar" <alim.akhtar@samsung.com>
Cc: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>,
	"'Rob\ Herring'" <robh+dt@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"'Chanwoo Choi'" <cw00.choi@samsung.com>,
	"'Pankaj Dubey'" <pankaj.dubey@samsung.com>,
	"'Sam	Protsenko'" <semen.protsenko@linaro.org>
Subject: Re: [PATCH] arm64: dts: exynos: correct GIC CPU interfaces address range on Exynos7
Date: Thu, 05 Aug 2021 11:01:11 +0100	[thread overview]
Message-ID: <87tuk4b47s.wl-maz@kernel.org> (raw)
In-Reply-To: <03d701d789db$f275d290$d76177b0$@samsung.com>

On Thu, 05 Aug 2021 10:26:14 +0100,
"Alim Akhtar" <alim.akhtar@samsung.com> wrote:
> 
> Hi Krzysztof,
> 
> > -----Original Message-----
> > From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> > Sent: 05 August 2021 13:07
> > To: Rob Herring <robh+dt@kernel.org>; devicetree@vger.kernel.org; linux-
> > arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Cc: Alim Akhtar <alim.akhtar@samsung.com>; Chanwoo Choi
> > <cw00.choi@samsung.com>; Pankaj Dubey <pankaj.dubey@samsung.com>;
> > Sam Protsenko <semen.protsenko@linaro.org>; Marc Zyngier
> > <maz@kernel.org>
> > Subject: Re: [PATCH] arm64: dts: exynos: correct GIC CPU interfaces address
> > range on Exynos7
> > 
> > On 05/08/2021 09:21, Krzysztof Kozlowski wrote:
> > > The GIC-400 CPU interfaces address range is defined as 0x2000-0x3FFF
> > > (by ARM).
> > >
> > 
> Looking at DDI0471B_gic400_r0p1_trm.pdf, CPU interface range is
> 0x0000 ~ 0x10000

I don't where you are getting this range from. The only 64kB range I'm
aware of is the optional integration trick to cope with 64kB pages
that was documented in the initial SBSA spec. The HW itself only
decodes 8kB for the CPU interface.

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-08-05 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  7:21 [PATCH] arm64: dts: exynos: correct GIC CPU interfaces address range on Exynos7 Krzysztof Kozlowski
2021-08-05  7:36 ` Krzysztof Kozlowski
2021-08-05  9:26   ` Alim Akhtar
2021-08-05  9:43     ` Krzysztof Kozlowski
2021-08-05  9:44       ` Krzysztof Kozlowski
2021-08-05  9:54         ` Alim Akhtar
2021-08-05 10:01     ` Marc Zyngier [this message]
2021-08-05 10:51       ` Alim Akhtar
2021-08-05 11:26 ` Sam Protsenko
2021-08-09 10: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=87tuk4b47s.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=pankaj.dubey@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=semen.protsenko@linaro.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