From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Igor Mitsyanko <i.mitsyanko@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] hw/arm/exynos: Add generic SDHCI devices
Date: Sat, 22 Apr 2017 21:07:54 +0200 [thread overview]
Message-ID: <20170422190754.3tsrihhj5e57r2sy@kozik-lap> (raw)
In-Reply-To: <CAFEAcA-8JJtYjAzq=gXJsRHTnO2xiu_EdFEsMR174jh=G0zW8A@mail.gmail.com>
On Sat, Apr 22, 2017 at 08:05:41PM +0100, Peter Maydell wrote:
> On 22 April 2017 at 19:46, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > On Thu, Apr 20, 2017 at 02:51:00PM +0100, Peter Maydell wrote:
> >> Incidentally someday maybe we should convert this Exynos4210 code
> >> to a proper QOM SoC container object, but that would be a lot of
> >> work.
> >
> > Any existing platforms which I could take as an good example? Maybe I'll
> > have some time to do it.
>
> The Xilinx ones, or stm32f205_soc, maybe. Basically the idea
> is that instead of having a random function which is doing
> a lot of instantiation of SoC devices, you have a QoM device
> which encapsulates all this, and the board level code just
> creates and configures that device.
Right, I've seen this pattern. Thanks for the hint.
Best regards,
Krzysztof
prev parent reply other threads:[~2017-04-22 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 15:16 [Qemu-devel] [RFC] hw/arm/exynos: Add generic SDHCI devices Krzysztof Kozlowski
2017-04-20 13:51 ` Peter Maydell
2017-04-22 18:46 ` Krzysztof Kozlowski
2017-04-22 19:05 ` Peter Maydell
2017-04-22 19:07 ` Krzysztof Kozlowski [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=20170422190754.3tsrihhj5e57r2sy@kozik-lap \
--to=krzk@kernel.org \
--cc=i.mitsyanko@gmail.com \
--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).