lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 Oct 2018 00:01:45 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Russell King <linux@...linux.org.uk>
Cc:     DTML <devicetree@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Mark Rutland <mark.rutland@....com>,
        Rob Herring <robh+dt@...nel.org>,
        Frank Rowand <frowand.list@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Question] directory for SoC-related DT binding

On Wed, Oct 10, 2018 at 9:09 PM Russell King - ARM Linux
<linux@...linux.org.uk> wrote:
>
> On Wed, Oct 10, 2018 at 08:07:52PM +0900, Masahiro Yamada 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
> > ./Documentation/devicetree/bindings/arm/apm
> > ./Documentation/devicetree/bindings/arm/bcm
> > ./Documentation/devicetree/bindings/arm/calxeda
> > ./Documentation/devicetree/bindings/arm/freescale
> > ./Documentation/devicetree/bindings/arm/hisilicon
> > ./Documentation/devicetree/bindings/arm/keystone
> > ./Documentation/devicetree/bindings/arm/marvell
> > ./Documentation/devicetree/bindings/arm/mediatek
> > ./Documentation/devicetree/bindings/arm/mrvl
> > ./Documentation/devicetree/bindings/arm/msm
> > ./Documentation/devicetree/bindings/arm/npcm
> > ./Documentation/devicetree/bindings/arm/nxp
> > ./Documentation/devicetree/bindings/arm/omap
> > ./Documentation/devicetree/bindings/arm/rockchip
> > ./Documentation/devicetree/bindings/arm/samsung
> > ./Documentation/devicetree/bindings/arm/stm32
> > ./Documentation/devicetree/bindings/arm/sunxi
> > ./Documentation/devicetree/bindings/arm/tegra
> > ./Documentation/devicetree/bindings/arm/ti
> > ./Documentation/devicetree/bindings/arm/uniphier
> > ./Documentation/devicetree/bindings/arm/ux500
> > ./Documentation/devicetree/bindings/arm/vt8500
>
> These are for arch/arm/mach-* and are the DT root descriptions for the
> various boards and SoCs.
>
> > 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
>
> These are for individual drivers in drivers/soc/

I see.

Thanks for helpful info!


-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ