From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] ARM: lpc18xx: add basic support for NXP LPC18xx/43xx SoCs
Date: Tue, 19 May 2015 11:11:31 +0200 [thread overview]
Message-ID: <2401619.oTy4WsRsYp@wuerfel> (raw)
In-Reply-To: <CAMuHMdXvvJDE1V=fQM7h8RDQOCy71zEG2S0LO17QSJdtd3tfrQ@mail.gmail.com>
On Tuesday 19 May 2015 10:45:14 Geert Uytterhoeven wrote:
> Hi Joachim,
>
> On Tue, May 19, 2015 at 10:39 AM, Joachim Eastwood <manabian@gmail.com> wrote:
> > On 19 May 2015 at 09:26, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >> On Tue, May 12, 2015 at 12:00 AM, Joachim Eastwood <manabian@gmail.com> wrote:
> >>> --- a/arch/arm/Kconfig.debug
> >>> +++ b/arch/arm/Kconfig.debug
> >>> @@ -1359,6 +1359,7 @@ config DEBUG_UART_PHYS
> >>> default 0x20201000 if DEBUG_BCM2835
> >>> default 0x3e000000 if DEBUG_BCM_KONA_UART
> >>> default 0x4000e400 if DEBUG_LL_UART_EFM32
> >>> + default 0x40081000 if ARCH_LPC18XX
> >>
> >> This will be used in any multi-platform kernel with DEBUG_LL=y, possible
> >> overriding a correct value, even if low-level LPC18XX debug support itself
> >> (what's the config option for that, I couldn't find it?) is disabled.
> >
> > Right now LPC18xx can't be a part of any multi-platform kernel.
>
> Oops. Sorry for the noise, I completely overlooked that...
> So it doesn't bite us (yet).
I actually have a patch to convert all remaining 'if ARCH_*' dependencies
in this file the way you suggest here, and noticed the LPC18XX addition
when rebasing that one yesterday.
> >> Please make this dependent on an appropriate DEBUG_LPC18XX
> >> option. Thanks!
> >
> > But anyways defining a DEBUG_LPC18XX symbol seems to be what most
> > other platforms do. I'll send a follow up patch defining DEBUG_LPC18XX
> > and then use that in DEBUG_UART_PHYS.
>
> Nevertheless, IMHO it's still good to have, thanks!
Agreed.
Arnd
next prev parent reply other threads:[~2015-05-19 9:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:00 [PATCH v4 0/7] Add support for NXP LPC18xx family Joachim Eastwood
2015-05-11 22:00 ` [PATCH v4 1/7] ARM: lpc18xx: add basic support for NXP LPC18xx/43xx SoCs Joachim Eastwood
2015-05-15 19:58 ` Arnd Bergmann
2015-05-19 7:26 ` Geert Uytterhoeven
2015-05-19 8:39 ` Joachim Eastwood
2015-05-19 8:45 ` Geert Uytterhoeven
2015-05-19 9:11 ` Arnd Bergmann [this message]
2015-05-19 9:25 ` Geert Uytterhoeven
2015-05-11 22:00 ` [PATCH v4 2/7] clocksource: add lpc32xx timer driver Joachim Eastwood
2015-05-12 1:32 ` Ezequiel Garcia
2015-05-12 7:32 ` Daniel Lezcano
2015-05-15 20:01 ` Arnd Bergmann
2015-05-18 12:09 ` Daniel Lezcano
2015-05-11 22:00 ` [PATCH v4 3/7] doc: dt: add documentation for lpc3220-timer Joachim Eastwood
2015-05-18 12:09 ` Daniel Lezcano
2015-05-11 22:00 ` [PATCH v4 4/7] ARM: dts: Add base DT for NXP LPC18xx Joachim Eastwood
2015-05-15 20:30 ` Arnd Bergmann
2015-05-11 22:00 ` [PATCH v4 5/7] ARM: dts: Add DT for Embedded Artists LPC4357 Developers Kit Joachim Eastwood
2015-05-11 22:00 ` [PATCH v4 6/7] ARM: dts: Add DT for Hitex LPC4350 Evaluation Board Joachim Eastwood
2015-05-11 22:00 ` [PATCH v4 7/7] ARM: lpc18xx: add kernel config Joachim Eastwood
2015-05-15 20:03 ` Arnd Bergmann
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=2401619.oTy4WsRsYp@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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