devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	lee@kernel.org, pawel.moll@arm.com, linux@arm.linux.org.uk,
	robh+dt@kernel.org, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, mark.rutland@arm.com
Subject: Re: [PATCH 2/4 V2] dt-bindings: Add root properties for Raspberry Pi
Date: Mon, 09 Feb 2015 11:06:28 -0700	[thread overview]
Message-ID: <54D8F724.4080609@wwwdotorg.org> (raw)
In-Reply-To: <1722146904.386302.1421694080817.JavaMail.open-xchange@oxbaltgw08.schlund.de>

On 01/19/2015 12:01 PM, Stefan Wahren wrote:
> Hi Stephen,
>
>> Stephen Warren <swarren@wwwdotorg.org> hat am 19. Januar 2015 um 18:13
>> geschrieben:
>>
>>
>> On 01/19/2015 04:00 AM, Stefan Wahren wrote:
>>> This patch adds root compatible properties for the following boards:
>>> - Raspberry Pi Model A
>>> - Raspberry Pi Model A+
>>> - Raspberry Pi Model B
>>> - Raspberry Pi Model B (no P5)
>>> - Raspberry Pi Model B rev2
>>> - Raspberry Pi Model B+
>>> - Raspberry Pi Compute Module
>>
>> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
>>
>> This seems sane to me. One thing I should have asked: What compatible
>> values does the RPi Foundation's downstream for all these cases?
>
> good point. Unfortunately my patches to linux-rpi-kernel are held back because
> of too many recipients, so it's possible that someone complain later.
>
> I have looked at chapter 3.1 in [1], but didn't find the any other variants than
> B and B+:
>
>    Here, the presence or absence of the "-plus" is the significant thing, not the
> "b" -- Model A's and A+'s will
>    use the "b" and "b-plus" variants, respectively.
>
> Also in the newest branch [2]:
>
> bcm2835-rpi-b.dts      -> model = Raspberry Pi Model B
> bcm2708-rpi-b.dts      -> model = Raspberry Pi Model B
> bcm2708-rpi-b-plus.dts -> model = Raspberry Pi Model B+
>
> Sorry, i don't have any experience with the downstream kernel. So please correct
> me if looked at the wrong places.
>
> [1] -
> https://github.com/raspberrypi/documentation/blob/master/configuration/device-tree.md
> [2] - https://github.com/raspberrypi/linux/tree/rpi-3.18.y/

This all matches what I found. I think differentiating between A/B and 
A+/B+ makes sense, so the compatible values in your patch should be 
fine; I'll reply to v2 in just a minute.

      reply	other threads:[~2015-02-09 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 11:00 [PATCH 2/4 V2] dt-bindings: Add root properties for Raspberry Pi Stefan Wahren
     [not found] ` <1421665231-28221-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2015-01-19 17:13   ` Stephen Warren
2015-01-19 19:01     ` Stefan Wahren
2015-02-09 18:06       ` Stephen Warren [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=54D8F724.4080609@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.com \
    /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).