[RFC PATCH 12/12] [DO NOT MERGE] ARM: dts: sun8i: v831: add a device tree file for Y20GA

Yi Y20GA is an IP camera with QG2101A chip (a rebranded Allwinner V831). Add a device tree for it. Signed-off-by: Icenowy Zheng --- arch/arm/boot/dts/Makefile| 3 +- arch/arm/boot/dts/sun8i-v831-yi-y20ga.dts | 53 +++ 2 files changed, 55 insertions(+), 1

[PATCH] In the device tree file openbmc-flash-layout.dtsi, rofs partition offset is defined as 0x4c0000, while its node name is "rofs@c0000" which is a typo. It should be "rofs@4c0000".

ARM: dts: openbmc-flash-layout: Fix a typo of rofs offset Signed-off-by: Kun Zhao --- arch/arm/boot/dts/openbmc-flash-layout.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/openbmc-flash-layout.dtsi b/arch/arm/boot/dts/openbmc-flash-layout.dtsi index

[PATCH V2 6/8] mmc: sdhci-msm: Read and use DLL Config property from device tree file

Certain platforms require different settings in the SDCC_HC_REG_DLL_CONFIG register. This setting can change from platform to platform. So the driver should check whether a particular platform require a different setting by reading the DT file and use it. Also use msm_cm_dll_set_freq only when

[PATCH V2 5/8] mmc: sdhci-msm: Update DDR_CONFIG as per device tree file

Certain platforms require different settings in the SDCC_HC_REG_DDR_CONFIG register. This setting can change from platform to platform. So the driver should check whether a particular platform require a different setting by reading the device tree file and use it. Signed-off-by: Bao D. Nguyen

[PATCH V1 5/7] mmc: sdhci-msm: Read and use DLL Config property from device tree file

Certain platforms require different settings in the SDCC_HC_REG_DLL_CONFIG register. This setting can change from platform to platform. So the driver should check whether a particular platform require a different setting by reading the DT file and use it. Also use msm_cm_dll_set_freq only when

[PATCH V1 4/7] mmc: sdhci-msm: Update DDR_CONFIG as per device tree file

Certain platforms require different settings in the SDCC_HC_REG_DDR_CONFIG register. This setting can change from platform to platform. So the driver should check whether a particular platform require a different setting by reading the device tree file and use it. Signed-off-by: Bao D. Nguyen

[BUG/PATCH 2/4] REVERT: DTS: GTA04: SPI / gpiolib: no no no, we do not want to "fix" our device tree file

just because some legacy boards seem to require changes in the gpio-lib which make our so far correct DTS/DTB being wrongly interpreted. A better solution seems to make the legacy handler optional so that DTS/DTB developed without legacy modes are not harmed. Signed-off-by: H. Nikolaus Schaller

Re: [PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

On Fri, May 25, 2018 at 11:27:46AM +0200, Geert Uytterhoeven wrote: > Hi Michel, > > On Thu, May 24, 2018 at 11:28 AM, Michel Pollet > wrote: > > This adds the Renesas R9A06G032 bare bone support. > > > > This currently only handles generic parts (gic, architected

Re: [PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

On Fri, May 25, 2018 at 11:27:46AM +0200, Geert Uytterhoeven wrote: > Hi Michel, > > On Thu, May 24, 2018 at 11:28 AM, Michel Pollet > wrote: > > This adds the Renesas R9A06G032 bare bone support. > > > > This currently only handles generic parts (gic, architected timer) > > and a UART. > > > >

Re: [PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

Hi Michel, On Thu, May 24, 2018 at 11:28 AM, Michel Pollet wrote: > This adds the Renesas R9A06G032 bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > > Signed-off-by: Michel Pollet

Re: [PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

Hi Michel, On Thu, May 24, 2018 at 11:28 AM, Michel Pollet wrote: > This adds the Renesas R9A06G032 bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > > Signed-off-by: Michel Pollet Thanks for your patch! > --- /dev/null > +++

[PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

This adds the Renesas R9A06G032 bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. Signed-off-by: Michel Pollet --- arch/arm/boot/dts/r9a06g032.dtsi | 86 1 file changed, 86

[PATCH v7 3/5] ARM: dts: Renesas R9A06G032 base device tree file

This adds the Renesas R9A06G032 bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. Signed-off-by: Michel Pollet --- arch/arm/boot/dts/r9a06g032.dtsi | 86 1 file changed, 86 insertions(+) create mode

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Geert, On Wed, 23 May 2018 at 12:18, Geert Uytterhoeven wrote: > Hi Michel, > On Wed, May 23, 2018 at 11:20 AM, M P wrote: > > On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven > > wrote: > >> On Tue, May 22, 2018 at 12:01 PM,

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Geert, On Wed, 23 May 2018 at 12:18, Geert Uytterhoeven wrote: > Hi Michel, > On Wed, May 23, 2018 at 11:20 AM, M P wrote: > > On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven > > wrote: > >> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet > >> wrote: > >> > + #address-cells = <1>;

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Michel, On Wed, May 23, 2018 at 11:20 AM, M P wrote: > On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven > wrote: >> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet >> wrote: >> > + #address-cells = <1>; >> > +

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Michel, On Wed, May 23, 2018 at 11:20 AM, M P wrote: > On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven > wrote: >> On Tue, May 22, 2018 at 12:01 PM, Michel Pollet >> wrote: >> > + #address-cells = <1>; >> > + #size-cells = <1>; >> > + >> > + cpus { >> > +

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Geert, On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven wrote: > Hi Michel, > On Tue, May 22, 2018 at 12:01 PM, Michel Pollet > wrote: > > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > > bone support. > > > > This currently

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Geert, On Wed, 23 May 2018 at 10:12, Geert Uytterhoeven wrote: > Hi Michel, > On Tue, May 22, 2018 at 12:01 PM, Michel Pollet > wrote: > > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > > bone support. > > > > This currently only handles generic parts (gic, architected timer) >

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Michel, On Tue, May 22, 2018 at 12:01 PM, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

Hi Michel, On Tue, May 22, 2018 at 12:01 PM, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set the >

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

On Tue, May 22, 2018 at 11:01:24AM +0100, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set the >

Re: [PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

On Tue, May 22, 2018 at 11:01:24AM +0100, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set the >

[PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet

[PATCH v6 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet ---

Re: [PATCH v5 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

On Tue, Apr 17, 2018 at 12:04:19PM +0100, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set the >

Re: [PATCH v5 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

On Tue, Apr 17, 2018 at 12:04:19PM +0100, Michel Pollet wrote: > This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare > bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set the >

[PATCH v5 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet

[PATCH v5 4/6] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet ---

[PATCH v4 6/8] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet

[PATCH v4 6/8] ARM: dts: Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1D (Part #R9A06G032) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet ---

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Simon, Michel, On Fri, Mar 30, 2018 at 09:25:16AM +0200, Simon Horman wrote: > On Thu, Mar 29, 2018 at 01:04:50PM +0200, jacopo mondi wrote: > > Hi Michel > > > > The subject of all your patches for arch/arm should start with: > > > > ARM: dts: > > > > A git log on that directory clearly shows

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Simon, Michel, On Fri, Mar 30, 2018 at 09:25:16AM +0200, Simon Horman wrote: > On Thu, Mar 29, 2018 at 01:04:50PM +0200, jacopo mondi wrote: > > Hi Michel > > > > The subject of all your patches for arch/arm should start with: > > > > ARM: dts: > > > > A git log on that directory clearly shows

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel, On Thu, Mar 29, 2018 at 9:47 AM, Michel Pollet wrote: > This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC > bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel, On Thu, Mar 29, 2018 at 9:47 AM, Michel Pollet wrote: > This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC > bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

On Thu, Mar 29, 2018 at 01:04:50PM +0200, jacopo mondi wrote: > Hi Michel > > The subject of all your patches for arch/arm should start with: > > ARM: dts: > > A git log on that directory clearly shows that's the preferred one. > > I would also say that you are missing a symbol definition in >

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

On Thu, Mar 29, 2018 at 01:04:50PM +0200, jacopo mondi wrote: > Hi Michel > > The subject of all your patches for arch/arm should start with: > > ARM: dts: > > A git log on that directory clearly shows that's the preferred one. > > I would also say that you are missing a symbol definition in >

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel The subject of all your patches for arch/arm should start with: ARM: dts: A git log on that directory clearly shows that's the preferred one. I would also say that you are missing a symbol definition in arch/arm/mach-shmobile/Kconfig (even if you got rid of any board file) I would

Re: [PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel The subject of all your patches for arch/arm should start with: ARM: dts: A git log on that directory clearly shows that's the preferred one. I would also say that you are missing a symbol definition in arch/arm/mach-shmobile/Kconfig (even if you got rid of any board file) I would

[PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet

[PATCH v3 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet ---

Re: [PATCH v2 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel, On Thu, Mar 22, 2018 at 12:44 PM, Michel Pollet wrote: > This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC > bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also

Re: [PATCH v2 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

Hi Michel, On Thu, Mar 22, 2018 at 12:44 PM, Michel Pollet wrote: > This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC > bare bone support. > > This currently only handles generic parts (gic, architected timer) > and a UART. > For simplicity sake, this also relies on the bootloader to set

[PATCH v2 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet

[PATCH v2 6/8] DT: arm: Add Renesas RZ/N1 SoC base device tree file

This adds the Renesas RZ/N1 Family (Part #R9A06G0xx) SoC bare bone support. This currently only handles generic parts (gic, architected timer) and a UART. For simplicity sake, this also relies on the bootloader to set the pinctrl and clocks. Signed-off-by: Michel Pollet ---

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

ee based kernels with U-boots that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux bin

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, c

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

he U-boot >> is broken... >> >> >>> >>>>> Not my choice of H/W, so I cannot change it. >>>>> >>>>> >>>>> === >>>>> OPENWRT: >>>>

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

. >> >> >>> >>>>> Not my choice of H/W, so I cannot change it. >>>>> >>>>> >>>>> ======= >>>>> OPENWRT: >>>>> I noticed when chec

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

oot device tree based kernels with U-boots that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, c

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

oot device tree based kernels with U-boots that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, c

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, c

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

that does not support device trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, c

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

erve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. === It would be usefu

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

erve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. === It would be usefu

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

;> I noticed when checking out the OpenWRT support for the board that >>>> they have a method to avoid having to pass the device tree address >>>> to the kernel, and can thus boot device tree based kernels with >>>> U-boots that does not support device trees.

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

;> I noticed when checking out the OpenWRT support for the board that >>>> they have a method to avoid having to pass the device tree address >>>> to the kernel, and can thus boot device tree based kernels with >>>> U-boots that does not support device trees.

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

nel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. === It would be useful to me, and I could of course patch the mainstream kernel, but first I would like to check if this

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

nel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. === It would be useful to me, and I could of course patch the mainstream kernel, but first I would like to check if this

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

Ulf, On 11/20/17 06:44, Mark Rutland wrote: > On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote: >> adding devicetree list, devicetree maintainers >> >> On 11/18/17 12:59, Ulf Samuelsson wrote: >>> I noticed when checking out the OpenWRT support for the board that they >>> have a

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

Ulf, On 11/20/17 06:44, Mark Rutland wrote: > On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote: >> adding devicetree list, devicetree maintainers >> >> On 11/18/17 12:59, Ulf Samuelsson wrote: >>> I noticed when checking out the OpenWRT support for the board that they >>> have a

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote: > adding devicetree list, devicetree maintainers > > On 11/18/17 12:59, Ulf Samuelsson wrote: > > I noticed when checking out the OpenWRT support for the board that they > > have a method to avoid having to pass the device tree

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote: > adding devicetree list, devicetree maintainers > > On 11/18/17 12:59, Ulf Samuelsson wrote: > > I noticed when checking out the OpenWRT support for the board that they > > have a method to avoid having to pass the device tree

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

;> to the kernel, and can thus boot device tree based kernels with >> U-boots that does not support device trees. >> >> What they do is to reserve 16 kB of kernel space, and tag it with >> an ASCII string "OWRTDTB:". After the kernel and dtb is built, a >&g

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

;> to the kernel, and can thus boot device tree based kernels with >> U-boots that does not support device trees. >> >> What they do is to reserve 16 kB of kernel space, and tag it with >> an ASCII string "OWRTDTB:". After the kernel and dtb is built, a >&g

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

tag it with an ASCII > string "OWRTDTB:". > After the kernel and dtb is built, a utility "patch-dtb" will update the > vmlinux binary, copying in the device tree file. > > === > It would be

Re: RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

tag it with an ASCII > string "OWRTDTB:". > After the kernel and dtb is built, a utility "patch-dtb" will update the > vmlinux binary, copying in the device tree file. > > === > It would be

RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

vice trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. ==

RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

vice trees. What they do is to reserve 16 kB of kernel space, and tag it with an ASCII string "OWRTDTB:". After the kernel and dtb is built, a utility "patch-dtb" will update the vmlinux binary, copying in the device tree file. ==

device tree file

Hi, Can someone point me to a specific device tree file for Intel Atom processor for reference ? Thanks in advance, Karthik Balaguru Disclaimer : This email communication may contain privileged and confidential information and is intended for the use of the addressee only. If you

device tree file

Hi, Can someone point me to a specific device tree file for Intel Atom processor for reference ? Thanks in advance, Karthik Balaguru Disclaimer : This email communication may contain privileged and confidential information and is intended for the use of the addressee only. If you

[PATCH V3 10/12] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-b.dtsi | 117 2 files changed, 118 insertions

[PATCH V3 10/12] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky <thomas.lenda...@amd.com> Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky <thomas.lenda...@amd.com> --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-

[PATCH V2 10/12] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-b.dtsi | 117 2 files changed, 118 insertions

[PATCH V2 10/12] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky <thomas.lenda...@amd.com> Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky <thomas.lenda...@amd.com> --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-

[PATCH 10/13] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-b.dtsi | 117 2 files changed, 118 insertions

[PATCH 10/13] dtb: amd: Add AMD XGBE device tree file

From: Tom Lendacky <thomas.lenda...@amd.com> Add AMD XGBE device tree file, which is available in AMD Seattle RevB. Signed-off-by: Tom Lendacky <thomas.lenda...@amd.com> --- MAINTAINERS | 1 + arch/arm64/boot/dts/amd/amd-seattle-xgbe-

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 03:19:05PM -0500, Li Yang wrote: > On Mon, Sep 28, 2015 at 2:29 PM, Russell King - ARM Linux > wrote: > > However, we can't dictate to people what license they wish to submit > > their work under; though, we can make the decision whether to accept > > it under the license

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 2:29 PM, Russell King - ARM Linux wrote: > On Mon, Sep 28, 2015 at 07:14:30PM +, Li Leo wrote: >> I saw some discussion going on last year about the permissive license >> to be used in ARM device tree files. I know a lot of files have been >> changed to use GPLv2/X11

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 07:14:30PM +, Li Leo wrote: > I saw some discussion going on last year about the permissive license > to be used in ARM device tree files. I know a lot of files have been > changed to use GPLv2/X11 license. But may I know if GPLv2/BSD 3-clause > dual license is still

License for ARM device tree file

Hi All, I saw some discussion going on last year about the permissive license to be used in ARM device tree files. I know a lot of files have been changed to use GPLv2/X11 license. But may I know if GPLv2/BSD 3-clause dual license is still a valid license to use in ARM device tree files. It

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 07:14:30PM +, Li Leo wrote: > I saw some discussion going on last year about the permissive license > to be used in ARM device tree files. I know a lot of files have been > changed to use GPLv2/X11 license. But may I know if GPLv2/BSD 3-clause > dual license is still

License for ARM device tree file

Hi All, I saw some discussion going on last year about the permissive license to be used in ARM device tree files. I know a lot of files have been changed to use GPLv2/X11 license. But may I know if GPLv2/BSD 3-clause dual license is still a valid license to use in ARM device tree files. It

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 03:19:05PM -0500, Li Yang wrote: > On Mon, Sep 28, 2015 at 2:29 PM, Russell King - ARM Linux > wrote: > > However, we can't dictate to people what license they wish to submit > > their work under; though, we can make the decision whether to accept >

Re: License for ARM device tree file

On Mon, Sep 28, 2015 at 2:29 PM, Russell King - ARM Linux wrote: > On Mon, Sep 28, 2015 at 07:14:30PM +, Li Leo wrote: >> I saw some discussion going on last year about the permissive license >> to be used in ARM device tree files. I know a lot of files have been >>

Re: [PATCHv3 5/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

> new file mode 100644 > index ..aa01c2610c6d > --- /dev/null > +++ b/arch/arm/boot/dts/at91-sama5d4ek.dts > @@ -0,0 +1,308 @@ > +/* > + * sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit > + * > + * Copyright (C) 2014 Atmel, > + *

Re: [PATCHv3 5/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

100644 index ..aa01c2610c6d --- /dev/null +++ b/arch/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit + * + * Copyright (C) 2014 Atmel, + *2014 Nicolas Ferre nicolas.fe...@atmel.com

[PATCHv3 5/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

-$(CONFIG_ARCH_AXXIA) += axm5516-amarillo.dtb diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts b/arch/arm/boot/dts/at91-sama5d4ek.dts new file mode 100644 index ..aa01c2610c6d --- /dev/null +++ b/arch/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file

[PATCHv3 4/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre Signed-off-by: Josh Wu Signed-off-by: Bo Shen Signed-off-by: Boris BREZILLON Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/sama5d4.dtsi | 1239 1 file changed, 1239

[PATCHv3 4/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre nicolas.fe...@atmel.com Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com Signed-off-by: Josh Wu josh...@atmel.com Signed-off-by: Bo Shen voice.s...@atmel.com Signed-off-by: Boris BREZILLON boris.brezil...@free-electrons.com Signed-off-by:

[PATCHv3 5/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit + * + * Copyright (C) 2014 Atmel, + *2014 Nicolas Ferre nicolas.fe...@atmel.com + * + * This file is dual-licensed: you can use it either under the terms

[PATCHv2 6/8] ARM: at91: dt: add device tree file for SAMA5D4ek board

-$(CONFIG_ARCH_AXXIA) += axm5516-amarillo.dtb diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts b/arch/arm/boot/dts/at91-sama5d4ek.dts new file mode 100644 index ..aa01c2610c6d --- /dev/null +++ b/arch/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file

[PATCHv2 5/8] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre Signed-off-by: Josh Wu Signed-off-by: Boris BREZILLON Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/sama5d4.dtsi | 1233 1 file changed, 1233 insertions(+) create

[PATCHv2 5/8] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre nicolas.fe...@atmel.com Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com Signed-off-by: Josh Wu josh...@atmel.com Signed-off-by: Boris BREZILLON boris.brezil...@free-electrons.com Signed-off-by: Alexandre Belloni

[PATCHv2 6/8] ARM: at91: dt: add device tree file for SAMA5D4ek board

/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit + * + * Copyright (C) 2014 Atmel, + *2014 Nicolas Ferre nicolas.fe...@atmel.com + * + * This file is dual-licensed: you can use it either under the terms

[PATCH 6/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

-$(CONFIG_ARCH_AXXIA) += axm5516-amarillo.dtb diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts b/arch/arm/boot/dts/at91-sama5d4ek.dts new file mode 100644 index ..aa01c2610c6d --- /dev/null +++ b/arch/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file

[PATCH 5/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre Signed-off-by: Josh Wu Signed-off-by: Boris BREZILLON Signed-off-by: Alexandre Belloni --- arch/arm/boot/dts/sama5d4.dtsi | 1233 1 file changed, 1233 insertions(+) create

[PATCH 5/7] ARM: at91: dt: add device tree file for SAMA5D4 SoC

From: Nicolas Ferre nicolas.fe...@atmel.com Add SAMA5D4 SoC DT file. Signed-off-by: Nicolas Ferre nicolas.fe...@atmel.com Signed-off-by: Josh Wu josh...@atmel.com Signed-off-by: Boris BREZILLON boris.brezil...@free-electrons.com Signed-off-by: Alexandre Belloni

[PATCH 6/7] ARM: at91: dt: add device tree file for SAMA5D4ek board

/arm/boot/dts/at91-sama5d4ek.dts @@ -0,0 +1,308 @@ +/* + * sama5d4ek.dts - Device Tree file for SAMA5D4 Evaluation Kit + * + * Copyright (C) 2014 Atmel, + *2014 Nicolas Ferre nicolas.fe...@atmel.com + * + * This file is dual-licensed: you can use it either under the terms

Re: [PATCH V2 2/2] ARM: tegra: convert device tree file of Dalmore to use pinctrl defines

On 12/03/2013 06:16 AM, Laxman Dewangan wrote: > Signed-off-by: Laxman Dewangan Patch description? Why convert only 1 board DT file? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

  1   2   >