qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Sai Pavan Boddu <saipava@xilinx.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	Edgar Iglesias <edgari@xilinx.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Implementing IOMMU support for SDHCI
Date: Tue, 3 Mar 2020 09:07:06 +0000	[thread overview]
Message-ID: <CAFEAcA9esoLLxeG_oe9d=cSKtJGhyVytLdPNTxXJOT7XJ0dsxw@mail.gmail.com> (raw)
In-Reply-To: <MN2PR02MB5935222A7AAD7518BD4F5DF8CAE40@MN2PR02MB5935.namprd02.prod.outlook.com>

On Tue, 3 Mar 2020 at 06:05, Sai Pavan Boddu <saipava@xilinx.com> wrote:
> > From: Peter Maydell <peter.maydell@linaro.org>
> > I don't think any of those scenarios are ones where you'd want the board
> > model to be passing in a MemTxAttr at device creation time.
> [Sai Pavan Boddu] Yeah ok, this makes sense. Only things which me might need to configure are master id's and trust zone settings if possible.
> May be we can set them at soc emulation level i.e "hw/arm/xlnx-zynqmp.c"

For that kind of thing, a good guide is to look at what the
hardware does. If the device inside the SoC just has
a hardcoded master ID, hardcode it in the QEMU device
model. If it has some signal lines that the SoC has to tie
off to 1 or 0 to configure it, implement that as a QEMU
device property (usually with the same name and basic
semantics as the config signal lines).

thanks
-- PMM


      reply	other threads:[~2020-03-03  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 12:38 Implementing IOMMU support for SDHCI Sai Pavan Boddu
2020-02-26 16:29 ` Peter Maydell
2020-02-28 10:08   ` Sai Pavan Boddu
2020-02-28 10:26     ` Peter Maydell
2020-03-03  6:05       ` Sai Pavan Boddu
2020-03-03  9:07         ` Peter Maydell [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='CAFEAcA9esoLLxeG_oe9d=cSKtJGhyVytLdPNTxXJOT7XJ0dsxw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=edgari@xilinx.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=saipava@xilinx.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 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).