public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Maxime Jourdan <mjourdan@baylibre.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Hans de Goede <hdegoede@redhat.com>, Chen-Yu Tsai <wens@csie.org>,
	Frank Rowand <frowand.list@gmail.com>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: Add schemas for simple-framebuffer
Date: Mon, 1 Apr 2019 12:52:53 +0200	[thread overview]
Message-ID: <20190401105253.oakh3uboz3vcgaj7@flea> (raw)
In-Reply-To: <CAL_JsqK=sazBCP7BBvzaBtvCxrtHVB0jbSqY4XmWgEz6B-5y7Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2167 bytes --]

Hi Rob,

On Wed, Mar 27, 2019 at 08:20:18AM -0500, Rob Herring wrote:
> On Tue, Mar 26, 2019 at 4:35 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > On Mon, Mar 25, 2019 at 11:27:36AM -0500, Rob Herring wrote:
> > > On Mon, Mar 25, 2019 at 8:54 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > > >
> > > > The simple framebuffer is a binding that allows the bootloader to setup a
> > > > framebuffer, describe it in the Device Tree for the OS to pick it up and
> > > > use it as is.
> > > >
> > > > Replace the current binding by a schema to allow the validation tools to
> > > > check those nodes.
> > > >
> > > > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > > > Cc: Chen-Yu Tsai <wens@csie.org>
> > > > Cc: Hans de Goede <hdegoede@redhat.com>
> > > > Cc: Maxime Jourdan <mjourdan@baylibre.com>
> > > > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > > >
> > > > ---
> > > >
> > > > Rob,
> > > >
> > > > Even though the node itself is properly described, I still end up with some
> > > > validation warnings when the chosen node is validated (basically
> > > > complaining that ranges, and the framebuffer nodes shouldn't be here, since
> > > > we haven't described them in the chosen schemas).
> > >
> > > Having 'ranges' is a bit strange because 'chosen' doesn't have an
> > > address. We can add #address-cells, #size-cells and framebuffer child
> > > node to the base chosen schema.

I've just sent a github PR to do that.

> > Maybe that's just cargo cult, but both the amlogic and the sunxi DT
> > have ranges in chosen. Shouldn't we need it so that the address is
> > decoded properly?
>
> I don't think so. If you have #{size,address}-cells then that should
> be enough. Lack of ranges should just mean that any translation stops
> at that level. But it is possible that the kernel code requires
> translation to go all the way to the root for memory addresses. I
> haven't checked.

I tested it, and it looks like of_translate_address returns EINVAL if
ranges is missing. If that's not desired, then I can look into it.

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-04-01 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 13:54 [PATCH] dt-bindings: Add schemas for simple-framebuffer Maxime Ripard
2019-03-25 16:27 ` Rob Herring
2019-03-26 21:35   ` Maxime Ripard
2019-03-27 13:20     ` Rob Herring
2019-04-01 10:52       ` Maxime Ripard [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=20190401105253.oakh3uboz3vcgaj7@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mjourdan@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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