archive mirror
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <>
To: Joel Stanley <>
Cc: "Jonathan Neuschäfer" <>,,,,
	"Russell King" <>
Subject: Re: [PATCH v3] ARM: Add wpcm450_defconfig for Nuvoton WPCM450
Date: Thu, 3 Nov 2022 16:27:42 +0100	[thread overview]
Message-ID: <Y2Pd7vIkOu0ptVMb@probook> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

On Wed, Nov 02, 2022 at 10:29:58PM +0000, Joel Stanley wrote:
> On Tue, 1 Nov 2022 at 11:22, Jonathan Neuschäfer <> wrote:
> >
> > This defconfig aims to offer a reasonable set of defaults for all
> > systems running on a Nuvoton WPCM450 chip.
> I was going to ask if we could instead have a common nuvoton
> defconfig, but this is an ARMv5 part so we can't also select the ARMv7
> npcm750.


> Reviewed-by: Joel Stanley <>

> Do you use this? OpenBMC systems tend to just use FIT, so we don't
> need this option.

I use this, because there is no modern U-Boot port for WPCM450 yet
(as far as I'm aware).


I also use kexec, it's useful during development, but I see that it's
not so useful for the BMC usecase.

> Does the wpcm do frequency scaling? If not you could disable this.

No, as it currently stands the clock driver is read-only except for the
clock gates, and there is no cpufreq. I'll disable this option.

CPU_IDLE could plausibly be implemented on WPCM450, but currently isn't.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-11-03 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 11:21 [PATCH v3] ARM: Add wpcm450_defconfig for Nuvoton WPCM450 Jonathan Neuschäfer
2022-11-02 22:29 ` Joel Stanley
2022-11-03 15:27   ` Jonathan Neuschäfer [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y2Pd7vIkOu0ptVMb@probook \ \ \ \ \ \ \

* 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).