From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-mips@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] MIPS: BMIPS: Improved early panic support
Date: Sun, 17 Jul 2022 15:49:32 +0200 [thread overview]
Message-ID: <20220717134932.GA17494@alpha.franken.de> (raw)
In-Reply-To: <20220715213747.111321-1-f.fainelli@gmail.com>
On Fri, Jul 15, 2022 at 02:37:45PM -0700, Florian Fainelli wrote:
> Hi Thomas,
>
> This patch series adds support for cfe_die() which can be used during
> early platform initialization when we do not yet have a valid DTB to
> infer an earlycon console from. This is useful while bringing up new
> platforms/DTBs as well.
>
> Thanks!
>
> Changes in v2:
>
> - ensure that we do not break multi-CPU builds by reading the CPU's PrID
> to perform the appropriate XKS01 disabling before handing over to CFE
>
> Florian Fainelli (2):
> MIPS: CFE: Add cfe_die()
> MIPS: BMIPS: Utilize cfe_die() for invalid DTB
>
> arch/mips/Kconfig | 1 +
> arch/mips/bmips/setup.c | 14 +++++-
> arch/mips/fw/cfe/cfe_api.c | 68 +++++++++++++++++++++++++-
> arch/mips/include/asm/fw/cfe/cfe_api.h | 2 +
> 4 files changed, 83 insertions(+), 2 deletions(-)
series 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 ]
prev parent reply other threads:[~2022-07-17 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 21:37 [PATCH v2 0/2] MIPS: BMIPS: Improved early panic support Florian Fainelli
2022-07-15 21:37 ` [PATCH v2 1/2] MIPS: CFE: Add cfe_die() Florian Fainelli
2022-07-15 21:37 ` [PATCH v2 2/2] MIPS: BMIPS: Utilize cfe_die() for invalid DTB Florian Fainelli
2022-07-17 13:49 ` Thomas Bogendoerfer [this message]
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=20220717134932.GA17494@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.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