From: Chen-Yu Tsai <wens@kernel.org>
To: u-boot@lists.denx.de
Cc: Chen-Yu Tsai <wens@csie.org>, Tom Rini <trini@konsulko.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Andy Yan <andy.yan@rock-chips.com>, Nick Xie <nick@khadas.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Deepak Das <deepakdas.linux@gmail.com>,
Alexandre Vicenzi <linux@alxd.me>,
Tianling Shen <cnsztl@gmail.com>,
David Bauer <mail@david-bauer.net>,
Xiaobo Tian <peterwillcn@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Klaus Goger <klaus.goger@theobroma-systems.com>,
Loic Devulder <ldevulder@suse.com>,
Jonas Karlman <jonas@kwiboo.se>, Levin Du <djw@t-chip.com.cn>,
Suniel Mahesh <sunil@amarulasolutions.com>,
FUKAUMI Naoki <naoki@radxa.com>,
Christopher Obbard <chris.obbard@collabora.com>,
Banglang Huang <banglang.huang@foxmail.com>,
"Matwey V. Kornilov" <matwey.kornilov@gmail.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: [PATCH v2 0/5] rockchip: Read cpuid and generate MAC address from efuse for RK3328 and RK3399
Date: Mon, 12 Feb 2024 21:51:03 +0800 [thread overview]
Message-ID: <20240212135111.1767734-1-wens@kernel.org> (raw)
From: Chen-Yu Tsai <wens@csie.org>
Hi folks,
This is v2 of my "read cpuid and generate MAC address from efuse on
RK3328 and RK3399 by default" series.
Changes since v1:
- Also imply "CONFIG_MISC"
- Add back unintentionally removed CONFIG_OF_LIBFDT_OVERLAY=y
- Remove ROCKCHIP_OTP from nanopi-r4s-rk3399_defconfig as requested by
Jonas
This series enables ROCKCHIP_EFUSE and MISC_INIT_R by default for RK3328
and RK3399 so that the cpuid is read from the efuse and used to generate
a serial number and MAC addresses for all boards.
This stacks on top of the recent defconfig update series [1] from Jonas.
[1] https://lore.kernel.org/u-boot/20240207000301.3270722-1-jonas@kwiboo.se/
Chen-Yu Tsai (5):
rockchip: rk3328: Read cpuid and generate MAC address from efuse
rockchip: rk3399: Read cpuid and generate MAC address from efuse
rockchip: rk3328: regenerate defconfigs
rockchip: rk3399: regenerate defconfigs
rockchip: nanopi-r4s: Drop ROCKCHIP_OTP
arch/arm/mach-rockchip/Kconfig | 6 ++++++
configs/chromebook_bob_defconfig | 3 ---
configs/chromebook_kevin_defconfig | 3 ---
configs/eaidk-610-rk3399_defconfig | 1 -
configs/evb-rk3328_defconfig | 3 ---
configs/evb-rk3399_defconfig | 1 -
configs/firefly-rk3399_defconfig | 3 ---
configs/khadas-edge-captain-rk3399_defconfig | 1 -
configs/khadas-edge-rk3399_defconfig | 1 -
configs/khadas-edge-v-rk3399_defconfig | 1 -
configs/leez-rk3399_defconfig | 1 -
configs/nanopc-t4-rk3399_defconfig | 1 -
configs/nanopi-m4-2gb-rk3399_defconfig | 1 -
configs/nanopi-m4-rk3399_defconfig | 1 -
configs/nanopi-m4b-rk3399_defconfig | 1 -
configs/nanopi-neo4-rk3399_defconfig | 1 -
configs/nanopi-r2c-plus-rk3328_defconfig | 3 ---
configs/nanopi-r2c-rk3328_defconfig | 3 ---
configs/nanopi-r2s-rk3328_defconfig | 3 ---
configs/nanopi-r4s-rk3399_defconfig | 4 ----
configs/orangepi-r1-plus-lts-rk3328_defconfig | 3 ---
configs/orangepi-r1-plus-rk3328_defconfig | 3 ---
configs/orangepi-rk3399_defconfig | 1 -
configs/pinebook-pro-rk3399_defconfig | 3 ---
configs/pinephone-pro-rk3399_defconfig | 3 ---
configs/puma-rk3399_defconfig | 3 ---
configs/roc-cc-rk3328_defconfig | 3 ---
configs/roc-pc-mezzanine-rk3399_defconfig | 3 ---
configs/roc-pc-rk3399_defconfig | 3 ---
configs/rock-4c-plus-rk3399_defconfig | 3 ---
configs/rock-4se-rk3399_defconfig | 3 ---
configs/rock-pi-4-rk3399_defconfig | 3 ---
configs/rock-pi-4c-rk3399_defconfig | 3 ---
configs/rock-pi-e-rk3328_defconfig | 3 ---
configs/rock-pi-n10-rk3399pro_defconfig | 2 --
configs/rock64-rk3328_defconfig | 3 ---
configs/rock960-rk3399_defconfig | 2 --
configs/rockpro64-rk3399_defconfig | 3 ---
38 files changed, 6 insertions(+), 86 deletions(-)
--
2.39.2
next reply other threads:[~2024-02-12 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:51 Chen-Yu Tsai [this message]
2024-02-12 13:51 ` [PATCH v2 1/5] rockchip: rk3328: Read cpuid and generate MAC address from efuse Chen-Yu Tsai
2024-02-12 13:51 ` [PATCH v2 2/5] rockchip: rk3399: " Chen-Yu Tsai
2024-02-12 13:51 ` [PATCH v2 3/5] rockchip: rk3328: regenerate defconfigs Chen-Yu Tsai
2024-03-13 10:27 ` Kever Yang
2024-03-13 14:43 ` Chen-Yu Tsai
2024-03-13 15:32 ` Jonas Karlman
2024-03-14 6:46 ` Kever Yang
2024-02-12 13:51 ` [PATCH v2 4/5] rockchip: rk3399: " Chen-Yu Tsai
2024-02-12 13:51 ` [PATCH v2 5/5] rockchip: nanopi-r4s: Drop ROCKCHIP_OTP Chen-Yu Tsai
2024-02-12 13:59 ` Dragan Simic
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=20240212135111.1767734-1-wens@kernel.org \
--to=wens@kernel.org \
--cc=alpernebiyasak@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=banglang.huang@foxmail.com \
--cc=chris.obbard@collabora.com \
--cc=cnsztl@gmail.com \
--cc=deepakdas.linux@gmail.com \
--cc=djw@t-chip.com.cn \
--cc=jagan@amarulasolutions.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=ldevulder@suse.com \
--cc=linux@alxd.me \
--cc=mail@david-bauer.net \
--cc=manivannan.sadhasivam@linaro.org \
--cc=matwey.kornilov@gmail.com \
--cc=naoki@radxa.com \
--cc=nick@khadas.com \
--cc=pbrobinson@gmail.com \
--cc=peterwillcn@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=sunil@amarulasolutions.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wens@csie.org \
/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