[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZyIV8bQbLs6rFhzs@alpha.franken.de>
Date: Wed, 30 Oct 2024 12:18:09 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>,
Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-mips@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] mips: bmips: bcm6358/6368: define required
brcm,bmips-cbr-reg
On Tue, Oct 01, 2024 at 05:23:59PM +0200, Christian Marangi wrote:
> For the bcm6358/6368 SoC the brcm,bmips-cbr-reg due to bootloader
> misconfiguration or HW bug from running the system from TP1.
>
> A workaround is now present to handle broken system that suffer from
> this bug hence add the now required property.
>
> Reported-by: kernel test robot <lkp@...el.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202409251520.pE12GzHd-lkp@intel.com/
> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>
> ---
> arch/mips/boot/dts/brcm/bcm6358.dtsi | 1 +
> arch/mips/boot/dts/brcm/bcm6368.dtsi | 1 +
> 2 files changed, 2 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists