From: Tom Rini <trini@konsulko.com>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>,
u-boot@lists.denx.de, u-boot-qcom@groups.io
Subject: Re: [PULL] Please pull qcom/qcom-next
Date: Mon, 9 Sep 2024 13:45:25 -0600 [thread overview]
Message-ID: <20240909194525.GD4252@bill-the-cat> (raw)
In-Reply-To: <20240909101245.1302713-1-caleb.connolly@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On Mon, Sep 09, 2024 at 12:04:46PM +0200, Caleb Connolly wrote:
> Hi Tom,
>
> Various improvements to Snapdragon support:
>
> * Bumped up the pagetable size to handle newer SoCs with much more RAM
> * Made memory map parsing more robust, fixing chainloading on SM8550/SM8650
> * Populate fdt_addr_r with U-Boot's FDT by default, and set $loadaddr to prevent
> crashes with some commands which expect it
> * Added initial support for SC7280/QCM6490 and the new RB3 Gen 2 board
> * Add debug config fragments to enable debug UART on some SoCs.
> * Enable RPMh regulators on SM8550/SM8650
> * Map the cmd-db memory explicitly since it may not be in the memory map
>
> CI: https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/pipelines/22255
>
> Thanks,
>
> The following changes since commit cbaf53fdf12534be50075fdd84105c682955424f:
>
> mmc: consider cd-gpios in Synopsys DesignWare driver (2024-09-05 19:08:14 -0600)
>
> are available in the Git repository at:
>
> git@source.denx.de:/u-boot/custodians/u-boot-snapdragon.git HEAD
>
> for you to fetch changes up to 41864bb2b66d0c68e6b2f6ae0c70d3c239ad258d:
>
> board/qualcomm: add debug config fragments for some SoCs (2024-09-06 11:59:51 +0200)
>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-09-09 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 10:04 [PULL] Please pull qcom/qcom-next Caleb Connolly
2024-09-09 10:14 ` Caleb Connolly
2024-09-09 19:45 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 16:17 Caleb Connolly
2025-01-22 21:57 ` Tom Rini
2024-10-04 14:22 Caleb Connolly
2024-10-04 17:15 ` Tom Rini
2024-10-04 14:17 Caleb Connolly
2024-10-04 14:21 ` Caleb Connolly
2024-03-01 15:45 Caleb Connolly
2024-03-01 21:35 ` 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=20240909194525.GD4252@bill-the-cat \
--to=trini@konsulko.com \
--cc=caleb.connolly@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=sumit.garg@linaro.org \
--cc=u-boot-qcom@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