From: Nishanth Menon <nm@ti.com>
To: Bryan Brattlof <bb@ti.com>
Cc: Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Hari Nagalla <hnagalla@ti.com>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
UBoot Mailing List <u-boot@lists.denx.de>,
Andrew Davis <afd@ti.com>
Subject: Re: [PATCH 00/11] Introduce basic support for TI's AM62Px SoC family
Date: Mon, 16 Oct 2023 10:52:10 -0500 [thread overview]
Message-ID: <20231016155210.22rlldfh56pjwc23@designed> (raw)
In-Reply-To: <20231012230616.2101992-13-bb@ti.com>
On 18:06-20231012, Bryan Brattlof wrote:
> Hello Everyone!
>
> The AM62Px is an extension of the existing Sitara AM62x low-cost family
> of application processors built for Automotive and Linux Application
> development. Scalable Arm Cortex-A53 performance and embedded features,
> such as: multi high-definition display support, 3D-graphics
> acceleration, 4K video acceleration, and extensive peripherals make the
> AM62Px well-suited for a broad range of automation and industrial
> application, including automotive digital instrumentation, automotive
> displays, industrial HMI, and more.
>
> Some highlights of AM62P SoC are:
>
This is Nice, BUT, I suggest cleaning up AM65 and AM62A prior to
attacking AM62P.
I would like to see:
a) dt sync
b) maintain the bootph - so that the boards finally boot
c) switch to stdboot.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-10-16 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 23:06 [PATCH 00/11] Introduce basic support for TI's AM62Px SoC family Bryan Brattlof
2023-10-12 23:06 ` [PATCH 01/11] soc: add info to identify the am62p " Bryan Brattlof
2023-10-12 23:06 ` [PATCH 02/11] arm: mach-k3: am62px: introduce clock and device files for wkup spl Bryan Brattlof
2023-10-12 23:06 ` [PATCH 03/11] ram: k3-ddrss: enable the am62ax's DDR controller for am62px Bryan Brattlof
2023-10-12 23:06 ` [PATCH 04/11] arm: mach-k3: invert logic for split DM firmware config Bryan Brattlof
2023-10-13 1:24 ` Bryan Brattlof
2023-10-12 23:06 ` [PATCH 05/11] arch: mach-k3: introduce basic files to support the am62px SoC family Bryan Brattlof
2023-10-13 1:28 ` Bryan Brattlof
2023-10-12 23:06 ` [PATCH 06/11] board: ti: introduce basic board files for the am62px family Bryan Brattlof
2023-10-13 12:50 ` Tom Rini
2023-10-13 16:49 ` Bryan Brattlof
2023-10-12 23:06 ` [PATCH 07/11] firmware: ti_sci_static_data: add static DMA channel data Bryan Brattlof
2023-10-12 23:06 ` [PATCH 08/11] arm: dts: add am62p5 dtbs from linux Bryan Brattlof
2023-10-12 23:06 ` [PATCH 09/11] arm: dts: introduce am62p5 uboot dts files Bryan Brattlof
2023-10-12 23:06 ` [PATCH 10/11] configs: introduce configs needed for the am62px Bryan Brattlof
2023-10-12 23:06 ` [PATCH 11/11] doc: board: ti: introduce am62px documentation Bryan Brattlof
2023-10-16 15:52 ` Nishanth Menon [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=20231016155210.22rlldfh56pjwc23@designed \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=hnagalla@ti.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=seanga2@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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