public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: nm@ti.com, vigneshr@ti.com, trini@konsulko.com
Cc: srk@ti.com, robertcnelson@gmail.com, u-boot@lists.denx.de,
	Roger Quadros <rogerq@kernel.org>
Subject: [RFC PATCH 0/2] board: ti: Use Extension framework
Date: Mon, 10 Jul 2023 17:50:24 +0300	[thread overview]
Message-ID: <20230710145026.128481-1-rogerq@kernel.org> (raw)

Hi,

RFC as only build tested. Need to get early feedback before I spend
more time on this.

Newer TI boards (AM6/J7) are using a custom logic to
detect expansion cards and set a 'name_overlays' environment
variable. Then DT overlays are applied by again custom
environment scripts during boot.

Instead of that migrate to using the Extension framework.
This allows the user to call 'extension scan' and 'extension apply'
commands to detect extension cards and apply the
DT overlays respectively.

For Booting, I expect distro boot scripts to already support
the extension framework via following environment
'extension_overlay_cmd' and 'extension_overlay_addr'.
i.e. include/config_distro_bootcmd.h

cheers,
-roger

Roger Quadros (2):
  board: ti: common: Add CONFIG_TI_CAPE_DETECT for cape detection
  board: ti: am65x: Move to using Extension framework

 board/ti/am335x/board.c            |   8 +
 board/ti/am65x/evm.c               | 264 ++++++++---------------------
 board/ti/common/Kconfig            |  16 ++
 board/ti/common/Makefile           |   3 +-
 board/ti/common/cape_detect.c      |   2 +-
 board/ti/common/cape_detect.h      |   2 +-
 board/ti/common/ti_card_detect.c   | 155 +++++++++++++++++
 board/ti/common/ti_card_detect.h   |  43 +++++
 configs/am65x_evm_a53_defconfig    |   2 +
 configs/am65x_hs_evm_a53_defconfig |   2 +
 10 files changed, 299 insertions(+), 198 deletions(-)
 create mode 100644 board/ti/common/ti_card_detect.c
 create mode 100644 board/ti/common/ti_card_detect.h

-- 
2.34.1


             reply	other threads:[~2023-07-10 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 14:50 Roger Quadros [this message]
2023-07-10 14:50 ` [RFC PATCH 1/2] board: ti: common: Add CONFIG_TI_CAPE_DETECT for cape detection Roger Quadros
2023-07-10 14:50 ` [RFC PATCH 2/2] board: ti: am65x: Move to using Extension framework Roger Quadros
2023-07-10 19:45   ` Simon Glass
2023-07-11 12:29     ` Roger Quadros
2023-07-13 18:44       ` Nishanth Menon
2023-10-04 12:39         ` Roger Quadros
2023-10-06 13:26           ` Köry Maincent
2023-10-06 15:48             ` Roger Quadros
2023-10-06 16:47             ` Simon Glass
2024-01-11 14:14               ` Roger Quadros

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=20230710145026.128481-1-rogerq@kernel.org \
    --to=rogerq@kernel.org \
    --cc=nm@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=srk@ti.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