devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	"peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org"
	<qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [kernel PATCH] devicetree: document ARM bindings for QEMU's Firmware Config interface
Date: Fri, 28 Nov 2014 14:49:31 +0100	[thread overview]
Message-ID: <54787D6B.5000302@redhat.com> (raw)
In-Reply-To: <20141128133300.GG25883@leverpostej>

On 11/28/14 14:33, Mark Rutland wrote:
> On Fri, Nov 28, 2014 at 01:22:29PM +0000, Laszlo Ersek wrote:
>> On 11/28/14 13:59, Arnd Bergmann wrote:

>>> We don't normally list contiguous registers separately. Maybe just round
>>> up to one page and make the register property
>>>
>>> 	reg = <0x0 0x9020000 0x0 0x1000>;
>>
>> The registers are not necessarily placed shoulder to shoulder (it's not
>> a requirement in the QEMU source).
> 
> It might not be at the moment, but if no-one separates them it could be
> a requirement for using this binding. Is there any benefit to having
> them separated?

I couldn't name any.

Thanks
Laszlo

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-11-28 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28 12:26 [kernel PATCH] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
     [not found] ` <1417177604-21194-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-28 12:59   ` Arnd Bergmann
2014-11-28 13:22     ` Laszlo Ersek
     [not found]       ` <54787715.6030407-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-28 13:33         ` Mark Rutland
2014-11-28 13:49           ` Laszlo Ersek [this message]
2014-11-28 13:17   ` Mark Rutland
2014-11-28 13:47     ` Laszlo Ersek

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=54787D6B.5000302@redhat.com \
    --to=lersek-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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).