[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.11.1403231742430.1291@knanqh.ubzr>
Date: Sun, 23 Mar 2014 17:48:48 -0400 (EDT)
From: Nicolas Pitre <nicolas.pitre@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
cc: linux-arm-kernel@...ts.infradead.org,
Rob Herring <robherring2@...il.com>,
Rob Herring <robh@...nel.org>,
Russell King <linux@....linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>, x86@...nel.org,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH 7/8] tty/serial: add arm64 semihosting earlycon
On Sun, 23 Mar 2014, Arnd Bergmann wrote:
> On Sunday 23 March 2014 16:04:41 Nicolas Pitre wrote:
> > On Fri, 21 Mar 2014, Rob Herring wrote:
> >
> > > From: Rob Herring <robh@...nel.org>
> > >
> > > Add earlycon support for the arm64 semihosting debug serial interface.
> > > This allows enabling a debug console when early_params are processed.
> > > This is based on the arm64 earlyprintk smh support and is intended to
> > > replace it.
> > >
> > > This is named arm rather than arm64 in hopes it will be used for both,
> > > but only arm64 is supported ATM.
> >
> > It can't be used for both as the semihosting calls themselves need
> > assembly code and this is not compatible with the equivalent ARM32
> > calls. So I'd suggest naming this "arm64" to avoid potential confusion.
>
> How about using an compile-time conditional to put both inline assemblies
> in there? While the driver is rather trivial to start with, I don't see
> a point in duplicating it either.
Sure. But it can be trivially renamed at that point.
Or, even better would be to add the ARM calls right away. And of course
ARM in Thumb mode has yet another call convention.
The printascii and printch code in arch/arm/kernel/debug.S for
CONFIG_DEBUG_SEMIHOSTING can be copied almost as is.
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists