From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] arm: lpc32xx: create platform specific Kconfig file
Date: Mon, 17 Sep 2018 21:43:02 +0300 [thread overview]
Message-ID: <20180917184304.15441-1-vz@mleia.com> (raw)
There is a need to introduce ARCH_LPC32XX build config symbol
to improve selection of build options for drivers, which are
specific to NXP LPC32xx platform only. At the same time the
new Kconfig file and sections can be used to describe common SoC
properties and collect entries of all LPC32xx boards.
The presented two patches are the initial ones in the series of
LPC32xx device driver changes, which move LPC32xx board specific
options from include/configs/* to build system and board configs.
Vladimir Zapolskiy (2):
arm: lpc32xx: add CONFIG_ARCH_LPC32XX build option
Makefile: add LPC32xx precondition for building platform images
Makefile | 2 ++
arch/arm/Kconfig | 24 ++++++++++++------------
arch/arm/cpu/arm926ejs/lpc32xx/Kconfig | 20 ++++++++++++++++++++
board/timll/devkit3250/Kconfig | 3 ---
board/work-microwave/work_92105/Kconfig | 3 ---
configs/devkit3250_defconfig | 6 +-----
configs/work_92105_defconfig | 11 ++++-------
7 files changed, 39 insertions(+), 30 deletions(-)
create mode 100644 arch/arm/cpu/arm926ejs/lpc32xx/Kconfig
--
2.17.1
next reply other threads:[~2018-09-17 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 18:43 Vladimir Zapolskiy [this message]
2018-09-17 18:43 ` [U-Boot] [PATCH 1/2] arm: lpc32xx: add CONFIG_ARCH_LPC32XX build option Vladimir Zapolskiy
2018-10-20 19:10 ` [U-Boot] [U-Boot, " Tom Rini
2018-09-17 18:43 ` [U-Boot] [PATCH 2/2] Makefile: add LPC32xx precondition for building platform images Vladimir Zapolskiy
2018-10-20 19:11 ` [U-Boot] [U-Boot, " Tom Rini
2018-10-19 0:27 ` [U-Boot] [PATCH 0/2] arm: lpc32xx: create platform specific Kconfig file Vladimir Zapolskiy
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=20180917184304.15441-1-vz@mleia.com \
--to=vz@mleia.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