devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Rob Herring <robh+dt@kernel.org>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH v3 0/2] Support for Axentia TSE-850
Date: Thu, 1 Dec 2016 08:02:57 +0100	[thread overview]
Message-ID: <b8bf3670-b925-c35f-7f03-5324a1dd1f9c@axentia.se> (raw)
In-Reply-To: <5198068.r9o6jcztHW@wuerfel>

On 2016-11-30 23:25, Arnd Bergmann wrote:
> On Wednesday, November 30, 2016 1:48:20 PM CET Peter Rosin wrote:
>> Hi!
>>
>> changes v2 -> v3
>> - document the new compatible strings prefixed with "axentia,".
>>
>> changes v1 -> v2
>> - squash the fixup into the correct patch, sorry for the noise.
>>
>> After finally having all essintial drivers upstreamed (the
>> last ones are currently in -next) I would like to have the
>> dts and the defconfig also upstreamed.
>>
>> Cheers,
>> Peter
>>
>> Peter Rosin (2):
>>   ARM: dts: add devicetree for the Axentia TSE-850
>>   ARM: tse850_defconfig: add Axentia TSE-850
>>
>>  Documentation/devicetree/bindings/arm/axentia.txt |  19 ++
>>  MAINTAINERS                                       |   8 +
>>  arch/arm/boot/dts/Makefile                        |   1 +
>>  arch/arm/boot/dts/axentia-linea.dtsi              |  53 +++++
>>  arch/arm/boot/dts/axentia-tse850-3.dts            | 276 ++++++++++++++++++++++
>>  arch/arm/configs/tse850_defconfig                 | 223 +++++++++++++++++
>>  6 files changed, 580 insertions(+)
> 
> Hi Peter,
> 
> I'm a bit confused. Are these just boards using the sama5d31 SoC,
> or something else?

No no, it's just what it seems, a cpu module with a sama5d31 and a
board using it (a couple more boards using the cpu module coming
later). I just didn't know about the naming conventions.

> Normally, dts files are picked up by the SoC platform maintainers
> and named with a prefix for that soc.

I was starting to wonder about the deafening silence, now I know
the reason...

> Also, we don't normally add a defconfig file for a specific
> machine, just add the options you want to sama5_defconfig
> and multi_v7_defconfig, and send all patches to the
> at91 maitainers.

I'll make some changes, thank you very much for the pointers!

Cheers,
Peter

      reply	other threads:[~2016-12-01  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 12:48 [PATCH v3 0/2] Support for Axentia TSE-850 Peter Rosin
2016-11-30 12:48 ` [PATCH v3 1/2] ARM: dts: add devicetree for the " Peter Rosin
2016-11-30 12:48 ` [PATCH v3 2/2] ARM: tse850_defconfig: add " Peter Rosin
2016-11-30 22:25 ` [PATCH v3 0/2] Support for " Arnd Bergmann
2016-12-01  7:02   ` Peter Rosin [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=b8bf3670-b925-c35f-7f03-5324a1dd1f9c@axentia.se \
    --to=peda@axentia.se \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).