From: Conor Dooley <conor@kernel.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
palmer@dabbelt.com, liwei1518@gmail.com,
daniel.barboza@oss.qualcomm.com, zhiwei_liu@linux.alibaba.com,
chao.liu.zevorn@gmail.com, qemu-riscv@nongnu.org,
qemu-devel@nongnu.org, sebastian.huber@embedded-brains.de,
"Alistair Francis" <alistair.francis@wdc.com>,
"Guenter Roeck" <linux@roeck-us.net>
Subject: Re: [PATCH] MAINTAINERS: Mark Microchip PolarFire SoC as Odd Fixes
Date: Thu, 14 May 2026 10:59:33 +0100 [thread overview]
Message-ID: <20260514-flatly-gallantly-00579d38db65@spud> (raw)
In-Reply-To: <CAKmqyKN5Tjwuy+S+NzEN0Xpsv_U7rQSM=PtvAkNNuhgA_oaRXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
On Thu, May 14, 2026 at 09:54:43AM +1000, Alistair Francis wrote:
> On Thu, May 14, 2026 at 7:26 AM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Wed, May 13, 2026 at 08:10:06AM +0200, Philippe Mathieu-Daudé wrote:
> > > On 13/5/26 04:38, alistair23@gmail.com wrote:
> > > > From: Alistair Francis <alistair.francis@wdc.com>
> > > >
> > > > Mark the "Microchip PolarFire SoC Icicle Kit" as Odd Fixes and enlist
> > > > Conor and Sebastian as people to help deal with the fixes.
> > > >
> > > > Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> > > > ---
> > > > Conor let me know if it should be a different address
> > > >
> > > > MAINTAINERS | 4 +++-
> > > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > index 952ed683bb..9626eb1ea9 100644
> > > > --- a/MAINTAINERS
> > > > +++ b/MAINTAINERS
> > > > @@ -1751,8 +1751,10 @@ F: target/riscv/xlrbr.decode
> > > > F: tests/tcg/riscv64/test-crc32.S
> > > > Microchip PolarFire SoC Icicle Kit
> > > > +M: Conor Dooley <conor@kernel.org>
> > > > +M: Sebastian Huber <sebastian.huber@embedded-brains.de>
> > >
> > > Maybe worth having a look at Guenter's following patch for this
> > > machine:
> > > https://github.com/groeck/qemu/commit/1a66d5b4e5fe9
> >
> > Ye, I can do that. It looks mostly pretty sane, but needs a bit of
> > cleanup I think before it is really applicable.
> >
> > Does it matter if the rates the PLLs report are accurate btw? Since
>
> You know the hardware better than us. Generally if it allows the guest
> boot and the values are sane then that's probably fine
In that case, there's very little that needs doing with it IMO.
Dropping this one line here is probably sufficient:
https://github.com/groeck/qemu/commit/1a66d5b4e5fe9#diff-9d9266aa5117a927eda2de5ec50e77c41664adfbf48599ffaa58c9e7def28d0dR98-R116
I'll test that out and see.
>
> Alistair
>
> > everything here is emulated, it shouldn't matter if the PLLs run say all
> > at 100 MHz instead of one at 100 and one at 40, right? They're just used
> > to clock things like i2c or pwm controllers.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-14 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 2:38 [PATCH] MAINTAINERS: Mark Microchip PolarFire SoC as Odd Fixes alistair23
2026-05-13 3:08 ` Sebastian Huber
2026-05-13 5:56 ` Markus Armbruster
2026-05-13 6:07 ` Sebastian Huber
2026-05-13 6:10 ` Philippe Mathieu-Daudé
2026-05-13 21:26 ` Conor Dooley
2026-05-13 21:31 ` Guenter Roeck
2026-05-13 23:54 ` Alistair Francis
2026-05-14 9:59 ` Conor Dooley [this message]
2026-05-13 19:18 ` Conor Dooley
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=20260514-flatly-gallantly-00579d38db65@spud \
--to=conor@kernel.org \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=linux@roeck-us.net \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sebastian.huber@embedded-brains.de \
--cc=zhiwei_liu@linux.alibaba.com \
/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.