linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: at91: use chipid device for soc detection
Date: Tue, 29 Mar 2016 16:30:29 +0200	[thread overview]
Message-ID: <3656574.4DhkCSPNfU@wuerfel> (raw)
In-Reply-To: <1459260638-3899-1-git-send-email-nicolas.ferre@atmel.com>

On Tuesday 29 March 2016 16:10:38 Nicolas Ferre wrote:
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
> 
> So far, the CIDR and EXID registers were in the DBGU interface. This device
> has disappeared with the SAMA5D2 family. These registers are exposed
> through a new device called chipid.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> [nicolas.ferre at atmel.com: remove useless warnings]
> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> [arnd at arndb.de: suggest to use static functions to reduce scope]
> 

(whole series)

Acked-by: Arnd Bergmann <arnd@arndb.de>

      reply	other threads:[~2016-03-29 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  7:21 [PATCH 1/3] ARM: at91: use chipid device for soc detection Ludovic Desroches
2016-03-18  7:21 ` [PATCH 2/3] ARM: at91/soc: reference the whole sama5d2 family Ludovic Desroches
2016-03-18 10:34   ` Alexandre Belloni
2016-03-18  7:21 ` [PATCH 3/3] ARM: at91/dt: sama5d2: add chipid node Ludovic Desroches
2016-03-18 10:34   ` Alexandre Belloni
2016-03-18 10:34 ` [PATCH 1/3] ARM: at91: use chipid device for soc detection Alexandre Belloni
2016-03-23 11:22   ` Nicolas Ferre
2016-03-23 13:47     ` Alexandre Belloni
2016-03-29 13:53       ` Nicolas Ferre
2016-03-20  0:45 ` Rob Herring
2016-03-29 13:55 ` Arnd Bergmann
2016-03-29 14:04   ` Nicolas Ferre
2016-03-29 14:10   ` [PATCH v2 " Nicolas Ferre
2016-03-29 14:30     ` Arnd Bergmann [this message]

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=3656574.4DhkCSPNfU@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;
as well as URLs for NNTP newsgroup(s).