public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Casanova <detlev.casanova@collabora.com>
To: u-boot@lists.denx.de
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Hai Pham <hai.pham.ud@renesas.com>,
	Tam Nguyen <tam.nguyen.xa@renesas.com>,
	Detlev Casanova <detlev.casanova@collabora.com>
Subject: [PATCH v1 0/4] Introduce the sysinfo command
Date: Fri, 16 Jun 2023 11:21:18 -0400	[thread overview]
Message-ID: <20230616152122.588168-1-detlev.casanova@collabora.com> (raw)

The command can be used to show various information that can be used to
identify the running system.

Currently supported subcommands are:
* model: A string representing the model
* id: The id of the board
* revision: The revision of this board id.

I'm not sure about the last commit, if it needs to be here upstream or
if it chould be something done by packagers.

I'm also not sure if a test should be added and where to start to test
this kind of command.

Detlev Casanova (4):
  sysinfo: Add IDs for board id and revision
  cmd: Add a sysinfo command
  sysinfo: rcar3: Implement BOARD_ID and BOARD_REVISION
  configs: rcar3: Add shell function to select the linux devicetree

 cmd/Kconfig                        |   6 ++
 cmd/Makefile                       |   1 +
 cmd/sysinfo.c                      | 124 +++++++++++++++++++++++++++++
 configs/rcar3_ulcb_defconfig       |   1 +
 drivers/sysinfo/rcar3.c            |  46 ++++++++---
 include/configs/rcar-gen3-common.h |   9 ++-
 include/sysinfo.h                  |   4 +
 7 files changed, 180 insertions(+), 11 deletions(-)
 create mode 100644 cmd/sysinfo.c

-- 
2.39.3


             reply	other threads:[~2023-06-16 15:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 15:21 Detlev Casanova [this message]
2023-06-16 15:21 ` [PATCH v1 1/4] sysinfo: Add IDs for board id and revision Detlev Casanova
2023-06-16 15:21 ` [PATCH v1 2/4] cmd: Add a sysinfo command Detlev Casanova
2023-06-17  0:41   ` Marek Vasut
2023-06-16 15:21 ` [PATCH v1 3/4] sysinfo: rcar3: Implement BOARD_ID and BOARD_REVISION Detlev Casanova
2023-06-17  0:43   ` Marek Vasut
2023-06-19 14:42     ` Detlev Casanova
2023-06-19 16:11       ` Marek Vasut
2023-06-19 18:27         ` Detlev Casanova
2023-06-19 21:54           ` Marek Vasut
2023-06-20 17:49             ` Detlev Casanova
2023-06-20 20:03               ` Marek Vasut
2023-06-20 20:40                 ` Detlev Casanova
2023-06-21  3:49                   ` Marek Vasut
2023-06-16 15:21 ` [PATCH v1 4/4] configs: rcar3: Add shell function to select the linux devicetree Detlev Casanova
2023-06-17  0:45   ` Marek Vasut
2023-06-19 14:45     ` Detlev Casanova

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=20230616152122.588168-1-detlev.casanova@collabora.com \
    --to=detlev.casanova@collabora.com \
    --cc=hai.pham.ud@renesas.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=tam.nguyen.xa@renesas.com \
    --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