From: "Pali Rohár" <pali@kernel.org>
To: Stefan Roese <sr@denx.de>,
Chris Packham <judge.packham@gmail.com>,
Baruch Siach <baruch@tkos.co.il>,
Dirk Eibach <dirk.eibach@gdsys.cc>,
u-boot@lists.denx.de
Cc: "Marek Behún" <marek.behun@nic.cz>,
"Dennis Gilmore" <dgilmore@redhat.com>,
"Mario Six" <mario.six@gdsys.cc>,
"Jon Nettleton" <jon@solid-run.com>
Subject: [PATCH 0/5] arm: mvebu: Automatically detect CONFIG_SYS_TCLK
Date: Sat, 31 Jul 2021 14:22:51 +0200 [thread overview]
Message-ID: <20210731122256.6546-1-pali@kernel.org> (raw)
This patch series automatically detects CONFIG_SYS_TCLK value, set it in
global mach/soc.h file and remove manual CONFIG_SYS_TCLK value from all
mvebu/kirkwood board config files.
So it just a cleanup to avoid defining custom macros in board config
files which can be automatically detected.
Could you test these patches on a38x and a37x platforms that nothing is
broken? I tested them on a38x Turris Omnia.
Pali Rohár (5):
arm: mvebu: a38x: Detect CONFIG_SYS_TCLK from SAR register
arm: mvebu: a37x: Detect CONFIG_SYS_TCLK from SAR register
arm: mvebu: msys: Set CONFIG_SYS_TCLK globally
arm: mvebu: axp: Set CONFIG_SYS_TCLK globally
arm: kirkwood: Do not overwrite CONFIG_SYS_TCLK
arch/arm/mach-kirkwood/include/mach/kw88f6281.h | 2 --
arch/arm/mach-mvebu/include/mach/soc.h | 15 ++++++++++-----
include/configs/clearfog.h | 1 -
include/configs/controlcenterdc.h | 2 --
include/configs/crs3xx-98dx3236.h | 1 -
include/configs/db-88f6720.h | 1 -
include/configs/db-88f6820-amc.h | 2 --
include/configs/db-88f6820-gp.h | 2 --
include/configs/db-mv784mp-gp.h | 1 -
include/configs/db-xc3-24g4xg.h | 1 -
include/configs/ds414.h | 1 -
include/configs/helios4.h | 1 -
include/configs/lacie_kw.h | 5 -----
include/configs/lsxl.h | 2 --
include/configs/maxbcm.h | 1 -
include/configs/theadorable.h | 1 -
include/configs/turris_omnia.h | 1 -
include/configs/x530.h | 2 --
18 files changed, 10 insertions(+), 32 deletions(-)
--
2.20.1
next reply other threads:[~2021-07-31 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 12:22 Pali Rohár [this message]
2021-07-31 12:22 ` [PATCH 1/5] arm: mvebu: a38x: Detect CONFIG_SYS_TCLK from SAR register Pali Rohár
2021-08-02 6:33 ` Stefan Roese
2021-07-31 12:22 ` [PATCH 2/5] arm: mvebu: a37x: " Pali Rohár
2021-08-02 6:33 ` Stefan Roese
2021-07-31 12:22 ` [PATCH 3/5] arm: mvebu: msys: Set CONFIG_SYS_TCLK globally Pali Rohár
2021-08-02 6:34 ` Stefan Roese
2021-07-31 12:22 ` [PATCH 4/5] arm: mvebu: axp: " Pali Rohár
2021-08-02 6:35 ` Stefan Roese
2021-07-31 12:22 ` [PATCH 5/5] arm: kirkwood: Do not overwrite CONFIG_SYS_TCLK Pali Rohár
2021-08-01 8:07 ` Chris Packham
2021-08-01 10:25 ` Pali Rohár
2022-08-16 9:37 ` Michael Walle
2022-08-16 18:17 ` Pali Rohár
2022-08-16 19:38 ` Pali Rohár
2022-08-16 20:02 ` Pali Rohár
2022-08-16 20:06 ` Michael Walle
2022-08-16 20:05 ` Michael Walle
2021-08-02 6:35 ` Stefan Roese
2021-08-11 8:27 ` [PATCH 0/5] arm: mvebu: Automatically detect CONFIG_SYS_TCLK Stefan Roese
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=20210731122256.6546-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=baruch@tkos.co.il \
--cc=dgilmore@redhat.com \
--cc=dirk.eibach@gdsys.cc \
--cc=jon@solid-run.com \
--cc=judge.packham@gmail.com \
--cc=marek.behun@nic.cz \
--cc=mario.six@gdsys.cc \
--cc=sr@denx.de \
--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