From: <Eugen.Hristev@microchip.com>
To: <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>
Subject: [PULL] u-boot-at91-2022.04-b
Date: Mon, 17 Jan 2022 12:09:06 +0000 [thread overview]
Message-ID: <45f04a4d-5bb5-70d1-59bd-0798b93abc8e@microchip.com> (raw)
Hello Tom,
Please pull tag u-boot-at91-2022.04-b , the second set of at91 features
for the next cycle 2022.04 .
This small feature set includes few changes for sama7g5 and sama7g5ek:
turn blue led on at boot, changes required for the Rev4 of the board,
better sync with the Linux DT with regards to the new DT nodes.
Thanks,
Eugen
The following changes since commit a02af84e03e018d7cd08bb3070cbe5517004712b:
Merge branch '2022-01-12-pci-updates' (2022-01-12 20:49:39 -0500)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-at91.git
tags/u-boot-at91-2022.04-b
for you to fetch changes up to dbf500b55770e58313df9fefa217129da38ea1b6:
configs: at91: sama7g5ek: enable CONFIG_PHANDLE_CHECK_SEQ (2022-01-17
11:18:39 +0200)
----------------------------------------------------------------
Second set of u-boot-at91 features for the 2022.04 cycle
----------------------------------------------------------------
Eugen Hristev (4):
i2c: at91: add compatible with microchip,sam9x60-i2c
ARM: dts: at91: sama7g5: add flx8 and required nodes
ARM: dts: at91: sama7g5ek: move eeproms to flexcom8
configs: at91: sama7g5ek: enable CONFIG_PHANDLE_CHECK_SEQ
Mihai Sain (1):
board: sama7g5ek: set blue led on at boot time
arch/arm/dts/sama7g5.dtsi | 50
+++++++++++++++++++++++++++++++++++++++
arch/arm/dts/sama7g5ek.dts | 39 +++++++++++++++++++++++-------
board/atmel/sama7g5ek/sama7g5ek.c | 9 +++++++
configs/sama7g5ek_mmc1_defconfig | 1 +
configs/sama7g5ek_mmc_defconfig | 1 +
drivers/i2c/at91_i2c.c | 6 +++++
6 files changed, 97 insertions(+), 9 deletions(-)
next reply other threads:[~2022-01-17 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 12:09 Eugen.Hristev [this message]
2022-01-17 16:12 ` [PULL] u-boot-at91-2022.04-b Tom Rini
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=45f04a4d-5bb5-70d1-59bd-0798b93abc8e@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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