U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: u-boot@lists.denx.de,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Lukasz Majewski <lukma@denx.de>, Peng Fan <peng.fan@nxp.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Heiko Schocher <hs@nabladev.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Anshul Dalal <anshuld@ti.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Andre Przywara <andre.przywara@arm.com>,
	Hrushikesh Salunke <h-salunke@ti.com>,
	Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	Alif Zakuan Yuslaimi <alif.zakuan.yuslaimi@altera.com>,
	Casey Connolly <casey.connolly@linaro.org>,
	Justin Swartz <justin.swartz@risingedge.co.za>,
	Daniel Palmer <daniel@thingy.jp>, Andrew Davis <afd@ti.com>,
	Tien Fong Chee <tien.fong.chee@altera.com>,
	Rasmus Villemoes <ravi@prevas.dk>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Alexey Charkov <alchark@gmail.com>
Subject: Re: [PATCH 6/6] board: variscite: add support for the omap4_var_som
Date: Tue, 19 May 2026 08:03:31 -0600	[thread overview]
Message-ID: <20260519140331.GY1858239@bill-the-cat> (raw)
In-Reply-To: <20260519-omap4-support-v1-6-b4a2a7435775@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

On Tue, May 19, 2026 at 08:45:43AM +0200, Bastien Curutchet wrote:

> OMAP4 support is present but there isn't any board using it.
> 
> Add minimal support for the Variscite OMAP4-SoM (debug console + boot
> from SD card).
> Use the ti/omap/omap4-var-stk-om44 device-tree from the Linux kernel. The
> real representation of the SoM's hardware is located in
> ti/omap/omap4-var-som-om44.dtsi included in it.
> 
> Signed-off-by: Bastien Curutchet <bastien.curutchet@bootlin.com>
[snip]
> diff --git a/board/variscite/omap4_var_som/MAINTAINERS b/board/variscite/omap4_var_som/MAINTAINERS
> new file mode 100644
> index 00000000000..802059ea521
> --- /dev/null
> +++ b/board/variscite/omap4_var_som/MAINTAINERS
> @@ -0,0 +1,6 @@
> +ARM OMAP4 VARISCITE VAR-SOM-OM44 MODULE
> +M:	Bastien Curutchet <bastien.curutchet@bootlin.com>
> +S:	Maintained
> +F:	board/variscite/omap4_var_som
> +F:	include/configs/omap4_var_som.h
> +F:	configs/omap4_var_som_defconfig

So this could all be caught with:
N: omap4_var_som

Which is my way of moving to the next topic, omap4 needs a maintainer
too, if we're bringing it back.

[snip]
> diff --git a/include/configs/omap4_var_som.h b/include/configs/omap4_var_som.h
> new file mode 100644
> index 00000000000..fa916cc71d2
> --- /dev/null
> +++ b/include/configs/omap4_var_som.h
> @@ -0,0 +1,16 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
> +/*
> + * (C) Copyright 2010
> + * Texas Instruments Incorporated.
> + * Steve Sakoman  <steve@sakoman.com>

This part isn't right, is it?

> + * Configuration settings for the TI OMAP4 Variscite SOM board.
> + * See ti_omap4_common.h for OMAP4 common part
> + */
> +
> +#ifndef __CONFIG_VAR_SOM_H
> +#define __CONFIG_VAR_SOM_H
> +
> +#include <configs/ti_omap4_common.h>

Can we just set SYS_CONFIG_NAME or so to ti_omap4_common  and drop this
file? Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-19 14:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  6:45 [PATCH 0/6] arm: omap: Add back omap4 support Bastien Curutchet
2026-05-19  6:45 ` [PATCH 1/6] arm: omap: Move PRM I2C channel frequency to vc.c Bastien Curutchet
2026-05-19  6:45 ` [PATCH 2/6] arm: ti: omap: Extract common clock definitions Bastien Curutchet
2026-05-19  6:45 ` [PATCH 3/6] clk: ti: Remove AM33xx dependency Bastien Curutchet
2026-05-19  6:45 ` [PATCH 4/6] configs: omap4: remove unused boot target devices Bastien Curutchet
2026-05-19  6:45 ` [PATCH 5/6] arm: ti: Introduce back omap4 support Bastien Curutchet
2026-05-19  6:45 ` [PATCH 6/6] board: variscite: add support for the omap4_var_som Bastien Curutchet
2026-05-19 14:03   ` Tom Rini [this message]
2026-05-19 14:55     ` Bastien Curutchet
2026-05-19 15:01       ` Tom Rini
2026-05-20  7:03         ` Bastien Curutchet
2026-05-20 14:29           ` 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=20260519140331.GY1858239@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=afd@ti.com \
    --cc=alchark@gmail.com \
    --cc=alif.zakuan.yuslaimi@altera.com \
    --cc=andre.przywara@arm.com \
    --cc=anshuld@ti.com \
    --cc=bastien.curutchet@bootlin.com \
    --cc=casey.connolly@linaro.org \
    --cc=daniel@thingy.jp \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=h-salunke@ti.com \
    --cc=hs@nabladev.com \
    --cc=jh80.chung@samsung.com \
    --cc=justin.swartz@risingedge.co.za \
    --cc=lukma@denx.de \
    --cc=mkorpershoek@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=patrice.chotard@foss.st.com \
    --cc=peng.fan@nxp.com \
    --cc=quentin.schulz@cherry.de \
    --cc=ravi@prevas.dk \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tien.fong.chee@altera.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