From: Guenter Roeck <linux@roeck-us.net>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Pekka Enberg <penberg@iki.fi>,
Clement Deschamps <clement.deschamps@antfield.fr>,
Luc Michel <luc.michel@git.antfield.fr>
Subject: Re: [Qemu-devel] [Qemu-arm] [RFC PATCH] hw: arm: Add basic support for cprman (clock subsystem)
Date: Wed, 10 Oct 2018 08:02:41 -0700 [thread overview]
Message-ID: <20181010150241.GA4418@roeck-us.net> (raw)
In-Reply-To: <CAAdtpL6c-_=zHqF1vBHVgM9=DA3PMYu1HX60oCy1DrzZ-LRVmA@mail.gmail.com>
On Wed, Oct 10, 2018 at 03:25:22PM +0200, Philippe Mathieu-Daudé wrote:
> Hi Guenter,
>
> On Tue, Jul 17, 2018 at 6:08 AM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > On 07/16/2018 06:53 PM, Philippe Mathieu-Daudé wrote:
> > > Hi Guenter,
> > >
> > > On 07/15/2018 07:06 PM, Guenter Roeck wrote:
> > >> Add basic support for BCM283x CPRMAN. Provide support for reading and
> > >> writing CPRMAN registers and initialize registers with sensible default
> > >> values. During runtime retain any written values.
> > >>
> > >> Basic CPRMAN support is necessary and sufficient to boot Linux on raspi2
> > >> and raspi3 systems.
> > >>
> > >> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> > >> ---
> > >> I don't seriously expect this patch to get accepted, but I thought
> > >> it might be valuable enough for others to use it when playing with
> > >> raspi2 and raspi3 emulations.
> > >
> > > I've been working on a very similar patch... But due to soft-freeze I
> > > postponed it.
> > >
> >
> > > I don't feel very confident with my local work, as you, it is based on
> > > looking at the Broadcom firmware [1] and how the Linux kernel initialize
> > > the devices. I'll however compare with your work.
> > >
> >
> > I'll be more than happy to drop my patch and go with yours instead.
> > Let's just do that - it looks like it is much more comprehensive.
>
> Did you make any progress with your work?
>
My patch works for me, and continue using it. My suggestion above was
for you to finalize your patch and submit it. I did not spend any further
time on it. Sorry for any confusion I may have caused.
> Your patch might be useful to solve the following issue:
> https://bugs.launchpad.net/bugs/1779017
Yes, that was one of the reasons for writing the patch in the first place.
Thanks,
Guenter
prev parent reply other threads:[~2018-10-10 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 22:06 [Qemu-devel] [RFC PATCH] hw: arm: Add basic support for cprman (clock subsystem) Guenter Roeck
2018-07-16 9:08 ` Peter Maydell
2018-07-16 13:51 ` Guenter Roeck
2018-07-16 14:07 ` Peter Maydell
2018-07-16 22:22 ` Guenter Roeck
2018-07-16 14:33 ` Peter Maydell
2018-07-16 16:14 ` Guenter Roeck
2018-07-17 1:53 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-07-17 4:07 ` Guenter Roeck
2018-10-10 13:25 ` Philippe Mathieu-Daudé
2018-10-10 15:02 ` Guenter Roeck [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=20181010150241.GA4418@roeck-us.net \
--to=linux@roeck-us.net \
--cc=clement.deschamps@antfield.fr \
--cc=f4bug@amsat.org \
--cc=luc.michel@git.antfield.fr \
--cc=penberg@iki.fi \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).