U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Sapp <rs@ti.com>
To: <rs@ti.com>, <robertcnelson@gmail.com>, <ayush@beagleboard.org>,
	<Erik.Welsh@octavosystems.com>, <anshuld@ti.com>, <bb@ti.com>,
	<trini@konsulko.com>, <afd@ti.com>, <xypron.glpk@gmx.de>,
	<ilias.apalodimas@linaro.org>, <sjg@chromium.org>
Cc: <u-boot@lists.denx.de>
Subject: Re: [PATCHv3 3/4] k3-am62-pocketbeagle2: add support for 1GB variant
Date: Wed, 24 Jun 2026 18:29:47 -0500	[thread overview]
Message-ID: <DJHO54H0KY54.3SIYX4G0BFWCL@ti.com> (raw)
In-Reply-To: <20260624211949.327905-4-rs@ti.com>

On Wed Jun 24, 2026 at 4:19 PM CDT, rs wrote:
> From: Randolph Sapp <rs@ti.com>
>
> Take Phytec's current DDR fixup functions and utilize them to
> dynamically adjust for variants in the pocketbeagle2. There are
> currently 3 skews, two of which are both 512MB with the same memory
> configuration, and one which is 1GB using the same CWL and CL settings
> but a modified density [1].
>
> Based off of Bryan Brattlof's patch [2].
>
> [1] https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/5411/8G%20Bits%20DDR4%20SDRAM.pdf
> [2] https://github.com/bryanbrattlof/beagleboot/commit/fb2f022e27427e990d7a33fd001ffb571e13cfc3
>
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
>  board/beagle/pocketbeagle2/Kconfig            |  26 +++++
>  board/beagle/pocketbeagle2/Makefile           |   2 +
>  board/beagle/pocketbeagle2/pocketbeagle2.c    | 103 +++++++++++++++++-
>  .../beagle/pocketbeagle2/pocketbeagle2_ddr.h  |  50 +++++++++
>  configs/am62_pocketbeagle2_r5_defconfig       |   5 +-
>  5 files changed, 184 insertions(+), 2 deletions(-)
>  create mode 100644 board/beagle/pocketbeagle2/pocketbeagle2_ddr.h
>
> [snip]

Just thinking out loud here, but maybe we shouldn't take this patch. The
industrial version, on top of having more memory, also has eMMC. That already
mandates a new device tree and configuration if people are going to use it as a
boot method.

Then again, maybe it's convenient for the users who don't care about eMMC? I
dunno. Seems odd either way.

  reply	other threads:[~2026-06-24 23:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24 21:19 [PATCHv3 0/4] k3-am62-pocketbeagle2: add board and variant support rs
2026-06-24 21:19 ` [PATCHv3 1/4] arm: mach-k3: am62: add &main_uart6 to clock and pwr tree rs
2026-06-24 21:19 ` [PATCHv3 2/4] k3-am62-pocketbeagle2: add initial board support rs
2026-06-24 21:19 ` [PATCHv3 3/4] k3-am62-pocketbeagle2: add support for 1GB variant rs
2026-06-24 23:29   ` Randolph Sapp [this message]
2026-06-25  8:21     ` Anshul Dalal
2026-06-29 20:32       ` Randolph Sapp
2026-06-30 15:17         ` Bryan Brattlof
2026-06-24 21:19 ` [PATCHv3 4/4] k3-am62-pocketbeagle2: add support for efi capsules rs
2026-06-26 17:59 ` [PATCHv3 0/4] k3-am62-pocketbeagle2: add board and variant support Marko Mäkelä

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=DJHO54H0KY54.3SIYX4G0BFWCL@ti.com \
    --to=rs@ti.com \
    --cc=Erik.Welsh@octavosystems.com \
    --cc=afd@ti.com \
    --cc=anshuld@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=bb@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=robertcnelson@gmail.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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