From: Neil Armstrong <neil.armstrong@linaro.org>
To: trini@konsulko.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de
Subject: [GIT PULL] Please pull u-boot-amlogic-20231106
Date: Mon, 6 Nov 2023 15:34:31 +0100 [thread overview]
Message-ID: <93fdf4b5-db69-47ec-86bc-94741d362b24@linaro.org> (raw)
Hi Tom,
A little set of fix for:
- also enable DFU RAM boot for libretech-ac, since it uses a different config header
- SM probe fix
- A1 USB missing clocks
The CI job is at https://source.denx.de/u-boot/custodians/u-boot-amlogic/pipelines/18452
Thanks,
Neil
The following changes since commit a4c83bda17196bf5d1ce640844595aaeced6465e:
Merge branch '2023-11-03-assorted-tegra-improvements' (2023-11-04 09:55:39 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-amlogic.git tags/u-boot-amlogic-20231106
for you to fetch changes up to c550e81171940932664a85bda315a6a073aae23c:
ARM: configs: libretech-ac: enable USB_DFU like in meson64.h (2023-11-06 09:46:05 +0100)
----------------------------------------------------------------
- fixup to also enabled DFU RAM boot for libretech-ac
- sm fix to bind child sm devices in the device tree
- add missing A1 clocks for USB stack
----------------------------------------------------------------
Alexey Romanov (1):
clk: a1: add new clocks for USB stack
Dmitry Rokosov (1):
drivers: sm: bind child sm devices in the device tree
Neil Armstrong (1):
ARM: configs: libretech-ac: enable USB_DFU like in meson64.h
drivers/clk/meson/a1.c | 6 ++++++
drivers/sm/meson-sm.c | 1 +
include/configs/libretech-ac.h | 1 +
3 files changed, 8 insertions(+)
next reply other threads:[~2023-11-06 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 14:34 Neil Armstrong [this message]
2023-11-06 16:33 ` [GIT PULL] Please pull u-boot-amlogic-20231106 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=93fdf4b5-db69-47ec-86bc-94741d362b24@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).