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 del
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 6
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 DLL
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
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 DLL
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
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
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.
> >
> > S
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
> +++ b/arch/arm/b
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 100644
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>;
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 {
>> > + #ad
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)
> >
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
> p
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
> pinct
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
---
arch/arm/boot/dts/r9a06g03
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
> pinct
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
---
arch/arm/boot/dts/r9a06g03
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
---
arch/arm/boot/dts/r9a06g03
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
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 th
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
>
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 ex
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
---
arch/arm/boot/dts/r9
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 t
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
---
arch/arm/boot/dts/r9
t 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
gt;>
>>
>>>
>>>>> Not my choice of H/W, so I cannot change it.
>>>>>
>>>>>
>>>>> =======
>>>>> OPENWRT:
>>>>> I noticed when checkin
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
t 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
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
;> 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.
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
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 metho
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 address
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
>> u
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
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.
=
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 are not an
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
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
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
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 t
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 l
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 a
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
> 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,
> + *
-$(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 for
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 i
-$(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 for
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 mod
-$(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 for
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 mod
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 http://vger
On 12/03/2013 10:51 PM, Laxman Dewangan wrote:
> On Wednesday 04 December 2013 01:39 AM, Stephen Warren wrote:
>> On 12/02/2013 06:55 AM, Laxman Dewangan wrote:
>>> Signed-off-by: Laxman Dewangan
>> Patch description?
>>
>> BTW, did you compile all the Tegra DT files before and after this
>> chang
On Wednesday 04 December 2013 01:39 AM, Stephen Warren wrote:
On 12/02/2013 06:55 AM, Laxman Dewangan wrote:
Signed-off-by: Laxman Dewangan
Patch description?
BTW, did you compile all the Tegra DT files before and after this
change, and make sure that there's zero difference between them (i.e
On 12/02/2013 06:55 AM, Laxman Dewangan wrote:
> Signed-off-by: Laxman Dewangan
Patch description?
BTW, did you compile all the Tegra DT files before and after this
change, and make sure that there's zero difference between them (i.e.
they're identical byte-for-byte when compiled)? I don't feel
Signed-off-by: Laxman Dewangan
---
Changes from V1:
- Changes as per new macros.
arch/arm/boot/dts/tegra114-dalmore.dts | 549
1 files changed, 275 insertions(+), 274 deletions(-)
diff --git a/arch/arm/boot/dts/tegra114-dalmore.dts
b/arch/arm/boot/dts/tegra114
Signed-off-by: Laxman Dewangan
---
arch/arm/boot/dts/tegra114-dalmore.dts | 549
1 files changed, 275 insertions(+), 274 deletions(-)
diff --git a/arch/arm/boot/dts/tegra114-dalmore.dts
b/arch/arm/boot/dts/tegra114-dalmore.dts
index cb5ec23..ea0eb31 100644
---
On 04/15/2013 05:47 PM, Jason Cooper wrote:
> On Fri, Apr 12, 2013 at 04:29:05PM +0200, Gregory CLEMENT wrote:
>> Hi Jason,
>>
>> I have just rebased the commits that you haven't applied yet. They are
>> rebased on mvebu/dt. I check that all the dtb can be built.
>>
>> Thanks,
>>
>> Gregory CLEMENT
On Fri, Apr 12, 2013 at 04:29:05PM +0200, Gregory CLEMENT wrote:
> Hi Jason,
>
> I have just rebased the commits that you haven't applied yet. They are
> rebased on mvebu/dt. I check that all the dtb can be built.
>
> Thanks,
>
> Gregory CLEMENT (3):
> ARM: dts: mvebu: Convert all the mvebu fi
Hi Jason,
I have just rebased the commits that you haven't applied yet. They are
rebased on mvebu/dt. I check that all the dtb can be built.
Thanks,
Gregory CLEMENT (3):
ARM: dts: mvebu: Convert all the mvebu files to use the range
property
ARM: dts: mvebu: introduce internal-regs node
On 14 March 2013 02:10, Doug Anderson wrote:
> Add the device tree entry for the device-tree enabled ADC driver that
> recently landed in the iio tree.
>
> Signed-off-by: Doug Anderson
I've not used the "clock" binding yet, Will test with that and give a tag.
> ---
> Changes in v2: None
>
> arc
Add the device tree entry for the device-tree enabled ADC driver that
recently landed in the iio tree.
Signed-off-by: Doug Anderson
---
Changes in v2: None
arch/arm/boot/dts/exynos5250.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arc
Add the device tree entry for the device-tree enabled ADC driver that
recently landed in the iio tree.
Signed-off-by: Doug Anderson
---
arch/arm/boot/dts/exynos5250.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
b/arch/arm/boot/dts/exynos
On Mon, Nov 12, 2012 at 09:28:33PM +0100, Philippe Reynes wrote:
> Signed-off-by: Philippe Reynes
> Signed-off-by: Eric Jarrige
> ---
>
> v4: update model to use the same format as apf28
> remove some empty line
> v3: set 26M clock to 0 (not used)
> v2: avoid enable again the watchdog
>
>
Signed-off-by: Philippe Reynes
Signed-off-by: Eric Jarrige
---
v4: update model to use the same format as apf28
remove some empty line
v3: set 26M clock to 0 (not used)
v2: avoid enable again the watchdog
arch/arm/boot/dts/imx27-apf27.dts | 89 +
1 fil
Signed-off-by: Philippe Reynes
Signed-off-by: Eric Jarrige
---
v3: set 26M clock to 0 (not used)
v2: avoid enable again the watchdog
arch/arm/boot/dts/imx27-apf27.dts | 92 +
1 files changed, 92 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/bo
On Tue, Oct 30, 2012 at 07:55:44PM +, Philippe Reynes wrote:
>
>
> Hi Sascha,
> >> + osc26m {
>
> >> + compatible = "fsl,imx-osc26m", "fixed-clock";
> >> + clock-frequency = <33554432>;
>
> >Is this really correct? The Datasheet specificies 26MHz, some boards
>
v2: avoid enable again the watchdog
Signed-off-by: Philippe Reynes
Signed-off-by: Eric Jarrige
---
arch/arm/boot/dts/imx27-apf27.dts | 92 +
1 files changed, 92 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts/imx27-apf27.dts
diff --git
On Fri, Oct 26, 2012 at 06:29:40PM +0200, Philippe Reynes wrote:
> Signed-off-by: Philippe Reynes
> Signed-off-by: Eric Jarrige
> ---
> arch/arm/boot/dts/imx27-apf27.dts | 96
> +
> 1 files changed, 96 insertions(+), 0 deletions(-)
> create mode 100644 arc
Signed-off-by: Philippe Reynes
Signed-off-by: Eric Jarrige
---
arch/arm/boot/dts/imx27-apf27.dts | 96 +
1 files changed, 96 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/boot/dts/imx27-apf27.dts
diff --git a/arch/arm/boot/dts/imx27-apf27.dts
72 matches
Mail list logo
