mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org,
	 Jonas Richardsen <jonasrichardsen@emlix.com>
Cc: denis.osterland@diehl.com
Subject: Re: [PATCH 0/3] raspi: cleanup of vc fixups
Date: Tue, 23 Apr 2024 10:34:06 +0200	[thread overview]
Message-ID: <171386124636.3461761.10857280667691362622.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240422102232.551842-1-jonasrichardsen@emlix.com>


On Mon, 22 Apr 2024 10:16:46 +0000, Jonas Richardsen wrote:
> This patch series contains a few changes to the video core fixups where
> the desired behaviour is obvious from raspberry device trees. These were
> tested on a Raspberry Pi 4B. There's a few more differences between the
> video core device tree and the one provided by barebox for which a
> discussion is welcome:
> 
> - After a [recent change][link1] the `/chosen` node of the device tree
>   is now fully copied from the video core device tree. This could
>   possibly be restricted to only copy relevant properties.
> - The properties `memreserve` and `serial-number` of the root node are
>   added by the video core and could also be copied.
> - The property `model` of the root node is updated with the specific
>   hardware revision of the pi.
> - The video core adds the two aliases `i2c_arm` and `i2c_vc` (as
>   properties to the `/aliases` node). As the [raspberrypi
>   documentation][link2] suggests to use the former for writing overlays,
>   it should maybe also be copied as a fixup.
> 
> [...]

Applied, thanks!

[1/3] raspi: add fixup method for specific properties
      https://git.pengutronix.de/cgit/barebox/commit/?id=dcb947764491 (link may not be stable)
[2/3] raspi: override properties in /reserved-memory node of device tree
      https://git.pengutronix.de/cgit/barebox/commit/?id=3cf4417d0045 (link may not be stable)
[3/3] raspi: add a fixup for the `dma-ranges` property of the `/emmc2bus` dt node
      https://git.pengutronix.de/cgit/barebox/commit/?id=3f9788433919 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-04-23  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 10:16 Jonas Richardsen
2024-04-22 10:16 ` [PATCH 1/3] raspi: add fixup method for specific properties Jonas Richardsen
2024-04-22 10:16 ` [PATCH 2/3] raspi: override properties in /reserved-memory node of device tree Jonas Richardsen
2024-04-22 10:16 ` [PATCH 3/3] raspi: add a fixup for the `dma-ranges` property of the `/emmc2bus` dt node Jonas Richardsen
2024-04-23  8:34 ` Sascha Hauer [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=171386124636.3461761.10857280667691362622.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=denis.osterland@diehl.com \
    --cc=jonasrichardsen@emlix.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