devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Rob Herring <robh@kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>Florian
	Fainelli <f.fainelli@gmail.com>
Subject: Re: [Question] directory for SoC-related DT binding
Date: Wed, 10 Oct 2018 14:16:53 +0200	[thread overview]
Message-ID: <af9eec6f-cb31-f23e-61b4-da1364ea7ba5@i2se.com> (raw)
In-Reply-To: <20181010120955.GQ30658@n2100.armlinux.org.uk>

Am 10.10.2018 um 14:09 schrieb Russell King - ARM Linux:
> On Wed, Oct 10, 2018 at 02:04:14PM +0200, Stefan Wahren wrote:
>> Hi,
>>
>> Am 10.10.2018 um 13:19 schrieb Rob Herring:
>>> On Wed, Oct 10, 2018 at 6:08 AM Masahiro Yamada
>>> <yamada.masahiro@socionext.com> wrote:
>>>> Hi,
>>>>
>>>>
>>>> I see a bunch of vendor (or SoC) names in
>>>> Documentation/device/bindings/arm/
>>>>
>>>> ./Documentation/devicetree/bindings/arm/altera
>>>> ./Documentation/devicetree/bindings/arm/amlogic
>>> Yeah, it's kind of a mixture of board/soc bindings mostly with some
>>> ARM architecture, ARM, Ltd. IP, and SoC system reg bindings.
>>>
>>> Eventually, I'd like to not split board bindings by arch and maybe we
>>> should move all the system/misc reg bindings out.
>>>
>>> [,,,]
>>>
>>>> I also see some vendor names in
>>>> Documentation/device/bindings/soc/
>>>>
>>>> ./Documentation/devicetree/bindings/soc/bcm
>>>> ./Documentation/devicetree/bindings/soc/dove
>>>> ./Documentation/devicetree/bindings/soc/fsl
>>>> ./Documentation/devicetree/bindings/soc/mediatek
>>>> ./Documentation/devicetree/bindings/soc/qcom
>>>> ./Documentation/devicetree/bindings/soc/rockchip
>>>> ./Documentation/devicetree/bindings/soc/ti
>>>> ./Documentation/devicetree/bindings/soc/xilinx
>>>> ./Documentation/devicetree/bindings/soc/zte
>>> This I believe is mostly SoC system reg bindings though there's
>>> probably a few other things.
>>>
>>>> Confusingly, I see bcm, mediatek, rockchip
>>>> in both locations.
>>>>
>>>> Is there any rule to choose one than the other?
>>> Top-level SoC/board bindings in arm/ and anything else elsewhere ideally.
>> in case of Documentation/devicetree/bindings/soc/bcm the directory
>> contains SoC / board bindings, cpu-enable and a firmware binding.
> I think you're confused there...
>
> $ ls -1 Documentation/devicetree/bindings/soc/bcm/
> brcm,bcm2835-vchiq.txt
> raspberrypi,bcm2835-power.txt
>
> Doesn't look like SoC/board bindings to me...
>
> whereas:
>
> $ ls -1 Documentation/devicetree/bindings/arm/bcm/
> brcm,bcm11351-cpu-method.txt
> brcm,bcm11351.txt
> brcm,bcm21664.txt
> brcm,bcm23550-cpu-method.txt
> brcm,bcm23550.txt
> brcm,bcm2835.txt
> brcm,bcm4708.txt
> brcm,bcm63138.txt
> brcm,brcmstb.txt
> brcm,cygnus.txt
> brcm,hr2.txt
> brcm,ns2.txt
> brcm,nsp-cpu-method.txt
> brcm,nsp.txt
> brcm,stingray.txt
> brcm,vulcan-soc.txt
> raspberrypi,bcm2835-firmware.txt
>
> does fit with your description, except for the directory path...

sorry, my fault i copied the wrong path. I actually thought of
Documentation/devicetree/bindings/arm/bcm/

Thanks for pointing out

  reply	other threads:[~2018-10-10 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 11:07 [Question] directory for SoC-related DT binding Masahiro Yamada
2018-10-10 11:19 ` Rob Herring
2018-10-10 12:04   ` Stefan Wahren
2018-10-10 12:09     ` Russell King - ARM Linux
2018-10-10 12:16       ` Stefan Wahren [this message]
2018-10-10 18:59     ` Rob Herring
2018-10-10 12:07 ` Russell King - ARM Linux
2018-10-10 15:01   ` Masahiro Yamada

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=af9eec6f-cb31-f23e-61b4-da1364ea7ba5@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --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@kernel.org \
    --cc=yamada.masahiro@socionext.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).