linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2/7] ARM: at91: introduce basic SAMA5D4 support
Date: Fri, 26 Sep 2014 16:54:53 +0200	[thread overview]
Message-ID: <1411743293.7866.62.camel@x220> (raw)
In-Reply-To: <20140926141326.GB4408@piout.net>

Hi Alexandre,

On Fri, 2014-09-26 at 16:13 +0200, Alexandre Belloni wrote:
> On 26/09/2014 at 13:47:03 +0200, Paul Bolle wrote :
> > On Mon, 2014-09-15 at 18:15 +0200, Alexandre Belloni wrote:
> > > From: Nicolas Ferre <nicolas.ferre@atmel.com>
> > > 
> > > Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> > 
> > This landed in next-20140926, as commit 2dc850b62e5b ("ARM: at91:
> > introduce basic SAMA5D4 support").
> > 
> > > diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> > > index b11ad54f8d17..7b44db208f10 100644
> > > --- a/arch/arm/Kconfig.debug
> > > +++ b/arch/arm/Kconfig.debug
> > > @@ -101,6 +101,10 @@ choice
> > >  		bool "Kernel low-level debugging on 9263 and 9g45"
> > >  		depends on HAVE_AT91_DBGU1
> > >  
> > > +	config AT91_DEBUG_LL_DBGU2
> > > +		bool "Kernel low-level debugging on sama5d4"
> > > +		depends on HAVE_AT91_DBGU2
> > > +
> > 
> > Why is this Kconfig symbol needed? Nothing in next-20140926 uses it. Are
> > future users perhaps queued somewhere (say, in commits that didn't
> > survive today's rather lively linux-next merges)? 
> 
> There is no user because it conflicts with the previous one that is
> selected by default by the sama5_defconfig. This is for early print and
> it means that you can get earlyprintk either for sama5d3 or sama5d4.
> 
> My guess is that it will never be included in any defconfig.

I missed that this is inside a "choice" (which complicates matters quite
a bit)!

There are a number of cases where one of the configs inside the choice
only serve to _not_ set anything. In those cases the Kconfig symbol is
used nowhere else. I'll have to think about this particular symbol a bit
more to see if it actually makes sense to not use it anywhere else.

Thinking about the "Kernel low-level debugging port" choice is
complicated by the fact that it holds about a gazillion "config"
entries, many of which only show up only if some dependency is met. So
it might take me some time to say anything sensible about it, if I ever
manage to do that at all...

Thanks,


Paul Bolle

  reply	other threads:[~2014-09-26 14:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:15 [PATCHv3 0/7] Initial support for the Atmel SMART sama5d4 Alexandre Belloni
2014-09-15 16:15 ` [PATCHv3 1/7] clk: at91: add a driver for the h32mx clock Alexandre Belloni
2014-09-19 12:33   ` Nicolas Ferre
2014-09-22  9:04     ` Boris BREZILLON
2014-09-27 23:01       ` Mike Turquette
2014-09-22  8:51   ` Boris BREZILLON
2014-09-15 16:15 ` [PATCHv3 2/7] ARM: at91: introduce basic SAMA5D4 support Alexandre Belloni
2014-09-26 11:47   ` Paul Bolle
2014-09-26 14:13     ` Alexandre Belloni
2014-09-26 14:54       ` Paul Bolle [this message]
2014-09-15 16:15 ` [PATCHv3 3/7] ARM: at91: SAMA5D4 SoC detection code and low level routines Alexandre Belloni
2014-09-15 16:15 ` [PATCHv3 4/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC Alexandre Belloni
2014-09-15 16:15 ` [PATCHv3 5/7] ARM: at91: dt: add device tree file for SAMA5D4ek board Alexandre Belloni
2014-09-19 12:27   ` Nicolas Ferre
2014-09-15 16:15 ` [PATCHv3 6/7] ARM: at91: add sama5d4 support to sama5_defconfig Alexandre Belloni
2014-09-15 16:15 ` [PATCHv3 7/7] ARM: at91: document Atmel SMART compatibles Alexandre Belloni
2014-09-19 12:38   ` Nicolas Ferre

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=1411743293.7866.62.camel@x220 \
    --to=pebolle@tiscali.nl \
    --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;
as well as URLs for NNTP newsgroup(s).