devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc Marí" <markmb@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Drew <drjones@redhat.com>, Kevin O'Connor <kevin@koconnor.net>,
	Laszlo <lersek@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
	Rob Herring <rob.herring@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Graf <agraf@suse.de>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2] QEMU fw_cfg DMA interface documentation
Date: Mon, 07 Sep 2015 13:08:29 +0200	[thread overview]
Message-ID: <1441624109.27149.18.camel@redhat.com> (raw)
In-Reply-To: <20150902103311.5335d469@markmb_rh>

  Hi,

> It's just simplicity. If you want to read a few times from the same
> field (like in ACPI tables, read the data size and then the data), you
> need a way to enable and disable the selector and manage the current
> offset for that entry. This is already provided with the "old"
> interface.

Could be handled with a 'select' control bit.  Only when set select
entry and reset offset to zero.

Also: would it make sense to allow an *array* of FWCfgDmaAccess structs?
With a 'more' bit in control we could indicate that there are more
entries.  I'm not sure firmware would actually use that though ...

cheers,
  Gerd

  reply	other threads:[~2015-09-07 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  9:08 QEMU fw_cfg DMA interface Marc Marí
     [not found] ` <1441012133-8154-1-git-send-email-markmb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-08-31  9:11   ` [PATCH v2] QEMU fw_cfg DMA interface documentation Marc Marí
2015-09-02  8:20     ` Stefan Hajnoczi
     [not found]       ` <CAJSP0QXgiMo0ahzRQ=2iMXVmiO+R27Re17c966LX1T_Q=Rdgow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-02  8:33         ` Marc Marí
2015-09-07 11:08           ` Gerd Hoffmann [this message]
     [not found]             ` <1441624109.27149.18.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-07 11:25               ` Laszlo Ersek
2015-09-08 16:46             ` Kevin O'Connor
2015-09-10 14:21               ` Marc Marí

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=1441624109.27149.18.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=drjones@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=lersek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=markmb@redhat.com \
    --cc=rob.herring@linaro.org \
    --cc=stefanha@gmail.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).