All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>, Peng Fan <peng.fan@nxp.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Peter Geis <pgwipeout@gmail.com>,
	XiaoDong Huang <derrick.huang@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround
Date: Tue, 18 Apr 2023 09:58:17 +0100	[thread overview]
Message-ID: <865y9tlg7q.wl-maz@kernel.org> (raw)
In-Reply-To: <20230417214033.25ckpswkjj6twfot@mercury.elektranox.org>

On Mon, 17 Apr 2023 22:40:33 +0100,
Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
> 
> Hi,
> 
> On Mon, Apr 17, 2023 at 05:20:08PM +0100, Marc Zyngier wrote:
> >> [...]
> > Please see below for an untested diff against your patch, addressing
> > most of the issues mentioned here.
> 
> Thanks, looks good. I integrated the changes into v3.
> 
> > Also, I don't see anything here addressing the *other* bug this
> > platform suffers from, which is the 32bit limit to the allocations.
> > Without a fix for it, this patch is pointless as the GIC may end-up
> > with memory it cannot reach.
> >
> > What;s the plan for that?
> 
> It got fixed in RK3588.

So what's the plan for the affected SoCs? It might be a good idea to
address it too, unless there are none of them in the wild?

	M.

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

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>, Peng Fan <peng.fan@nxp.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Peter Geis <pgwipeout@gmail.com>,
	XiaoDong Huang <derrick.huang@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround
Date: Tue, 18 Apr 2023 09:58:17 +0100	[thread overview]
Message-ID: <865y9tlg7q.wl-maz@kernel.org> (raw)
In-Reply-To: <20230417214033.25ckpswkjj6twfot@mercury.elektranox.org>

On Mon, 17 Apr 2023 22:40:33 +0100,
Sebastian Reichel <sebastian.reichel@collabora.com> wrote:
> 
> Hi,
> 
> On Mon, Apr 17, 2023 at 05:20:08PM +0100, Marc Zyngier wrote:
> >> [...]
> > Please see below for an untested diff against your patch, addressing
> > most of the issues mentioned here.
> 
> Thanks, looks good. I integrated the changes into v3.
> 
> > Also, I don't see anything here addressing the *other* bug this
> > platform suffers from, which is the 32bit limit to the allocations.
> > Without a fix for it, this patch is pointless as the GIC may end-up
> > with memory it cannot reach.
> >
> > What;s the plan for that?
> 
> It got fixed in RK3588.

So what's the plan for the affected SoCs? It might be a good idea to
address it too, unless there are none of them in the wild?

	M.

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

  reply	other threads:[~2023-04-18  8:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 15:00 [PATCH v2 0/2] Add Rockchip RK3588 GIC ITS support Sebastian Reichel
2023-04-17 15:00 ` Sebastian Reichel
2023-04-17 15:00 ` [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround Sebastian Reichel
2023-04-17 15:00   ` Sebastian Reichel
2023-04-17 16:20   ` Marc Zyngier
2023-04-17 16:20     ` Marc Zyngier
2023-04-17 21:40     ` Sebastian Reichel
2023-04-17 21:40       ` Sebastian Reichel
2023-04-18  8:58       ` Marc Zyngier [this message]
2023-04-18  8:58         ` Marc Zyngier
2023-04-18 14:34         ` Sebastian Reichel
2023-04-18 14:34           ` Sebastian Reichel
2023-04-17 15:00 ` [PATCH v2 2/2] arm64: dts: rockchip: rk3588: add MSI support Sebastian Reichel
2023-04-17 15:00   ` Sebastian Reichel
2023-04-17 16:39   ` Marc Zyngier
2023-04-17 16:39     ` Marc Zyngier

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=865y9tlg7q.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=derrick.huang@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=peng.fan@nxp.com \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.