From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC
Date: Wed, 1 Oct 2014 12:23:33 +0100 [thread overview]
Message-ID: <20141001112332.GB13759@leverpostej> (raw)
In-Reply-To: <1411992293-7729-3-git-send-email-zhang.lyra@gmail.com>
On Mon, Sep 29, 2014 at 01:04:49PM +0100, zhang.lyra at gmail.com wrote:
> From: "zhizhou.zhang" <zhizhou.zhang@spreadtrum.com>
>
> Adds the device tree support for Spreadtrum Shark64 SoC based on ARMv8 architecture.
>
> Signed-off-by: zhizhou.zhang <zhizhou.zhang@spreadtrum.com>
> Signed-off-by: chunyan.zhang <chunyan.zhang@spreadtrum.com>
> ---
> arch/arm64/boot/dts/sprd_shark64.dts | 110 ++++++++++++++++++++++++++++++++++
> 1 file changed, 110 insertions(+)
> create mode 100644 arch/arm64/boot/dts/sprd_shark64.dts
>
> diff --git a/arch/arm64/boot/dts/sprd_shark64.dts b/arch/arm64/boot/dts/sprd_shark64.dts
> new file mode 100644
> index 0000000..537cd6d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/sprd_shark64.dts
> @@ -0,0 +1,110 @@
> +/*
> + * dts file for Spreadtrum(sprd) Shark64 SOC
> + *
> + * Copyright (C) 2014, Spreadtrum Communications Inc.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation; either version 2 of
> + * the License, or (at your option) any later version.
> + */
> +
> +/dts-v1/;
> +
> +/memreserve/ 0x80000000 0x00010000;
What is this protecting?
Please add a comment.
> +
> +/ {
> + model = "shark64 Board";
> + compatible = "sprd,shark64";
This feels like it would make more sense as an SoC dtsi to be included
by various boards (which can override the model and compatible).
> + interrupt-parent = <&gic>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + chosen {
> + bootargs = "earlycon=serial_sprd,0x70000000";
Can we not use stdout-path for this?
> + };
> +
> + cpus {
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + cpu at 0 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
Can we have the particular CPU name, please?
> + reg = <0x0 0x0>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
No PSCI?
What are you using for your bootloader/firmware?
If you must use spin-table, please give each CPU a unique release
address.
> + };
> + cpu at 1 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x1>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu at 2 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x2>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu at 3 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x3>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + };
> +
> + memory at 80000000 {
> + device_type = "memory";
> + reg = <0 0x80000000 0 0x20000000>;
> + };
> +
> + aliases {
> + serial0 = &uart0;
> + serial1 = &uart1;
> + };
Could you move this up above chosen, please?
> +
> + gic: interrupt-controller at 12001000 {
> + compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x12001000 0 0x1000>,
> + <0 0x12002000 0 0x1000>;
No GICH or GICV?
Which exception level do your CPUs boot in?
I would strongly recommend booting at EL2. That gives the kernel more
flexibility to perform fixups (e.g. zeroing CNTVOFF), and requires less
work in your bootloader.
> + };
> +
> + intc:interrupt-controller at 71400000 {
> + compatible = "sprd,intc";
> + #interrupt-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x71400000 0 0x1000>,
> + <0 0x71500000 0 0x1000>,
> + <0 0x71600000 0 0x1000>,
> + <0 0x71700000 0 0x1000>;
> + };
This binding doesn't exist in mainline, and isn't added by this series.
I'm especially confused by the #interrupt-cells = <0>.
What exactly is this, and how do you intend to use it?
> +
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <1 13 0xff01>,
> + <1 14 0xff01>,
> + <1 11 0xff01>,
> + <1 10 0xff01>;
> + clock-frequency = <26000000>;
Please have your FW or bootloader program CNTFRQ_EL1 on each CPU, and
get rid of the clock-frequency property here.
> + };
> +
> + uart0: uart at 70000000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70000000 0 0x100>;
> + interrupts = <0 2 0xf04>;
> + };
No clocks/dmas/etc necessary?
Mark.
> +
> + uart1: uart at 70100000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70100000 0 0x100>;
> + interrupts = <0 3 0xf04>;
> + };
> +};
> --
> 1.7.9.5
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: "zhang.lyra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<zhang.lyra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Catalin Marinas <Catalin.Marinas-5wv7dgnIgG8@public.gmane.org>,
"gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org"
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
"ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org"
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
"jslaby-AlSwsSmVLrQ@public.gmane.org"
<jslaby-AlSwsSmVLrQ@public.gmane.org>,
"galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
<galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"m-karicheri2-l0cyMroinI0@public.gmane.org"
<m-karicheri2-l0cyMroinI0@public.gmane.org>,
Pawel Moll <Pawel.Moll-5wv7dgnIgG8@public.gmane.org>,
"artagnon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<artagnon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"rrichter-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org"
<rrichter-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Will Deacon <Will.Deacon-5wv7dgnIgG8@public.gmane.org>,
"orsonzhai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<orsonzhai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"geng.ren-lxIno14LUO0EEoCn2XhGlw@public.gmane.org"
<geng.ren-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>,
"zhizhou.zhang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org"
<zhizhou.zhang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kern>
Subject: Re: [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC
Date: Wed, 1 Oct 2014 12:23:33 +0100 [thread overview]
Message-ID: <20141001112332.GB13759@leverpostej> (raw)
In-Reply-To: <1411992293-7729-3-git-send-email-zhang.lyra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, Sep 29, 2014 at 01:04:49PM +0100, zhang.lyra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> From: "zhizhou.zhang" <zhizhou.zhang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>
>
> Adds the device tree support for Spreadtrum Shark64 SoC based on ARMv8 architecture.
>
> Signed-off-by: zhizhou.zhang <zhizhou.zhang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>
> Signed-off-by: chunyan.zhang <chunyan.zhang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>
> ---
> arch/arm64/boot/dts/sprd_shark64.dts | 110 ++++++++++++++++++++++++++++++++++
> 1 file changed, 110 insertions(+)
> create mode 100644 arch/arm64/boot/dts/sprd_shark64.dts
>
> diff --git a/arch/arm64/boot/dts/sprd_shark64.dts b/arch/arm64/boot/dts/sprd_shark64.dts
> new file mode 100644
> index 0000000..537cd6d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/sprd_shark64.dts
> @@ -0,0 +1,110 @@
> +/*
> + * dts file for Spreadtrum(sprd) Shark64 SOC
> + *
> + * Copyright (C) 2014, Spreadtrum Communications Inc.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation; either version 2 of
> + * the License, or (at your option) any later version.
> + */
> +
> +/dts-v1/;
> +
> +/memreserve/ 0x80000000 0x00010000;
What is this protecting?
Please add a comment.
> +
> +/ {
> + model = "shark64 Board";
> + compatible = "sprd,shark64";
This feels like it would make more sense as an SoC dtsi to be included
by various boards (which can override the model and compatible).
> + interrupt-parent = <&gic>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + chosen {
> + bootargs = "earlycon=serial_sprd,0x70000000";
Can we not use stdout-path for this?
> + };
> +
> + cpus {
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + cpu@0 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
Can we have the particular CPU name, please?
> + reg = <0x0 0x0>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
No PSCI?
What are you using for your bootloader/firmware?
If you must use spin-table, please give each CPU a unique release
address.
> + };
> + cpu@1 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x1>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu@2 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x2>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu@3 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x3>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + };
> +
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0 0x80000000 0 0x20000000>;
> + };
> +
> + aliases {
> + serial0 = &uart0;
> + serial1 = &uart1;
> + };
Could you move this up above chosen, please?
> +
> + gic: interrupt-controller@12001000 {
> + compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x12001000 0 0x1000>,
> + <0 0x12002000 0 0x1000>;
No GICH or GICV?
Which exception level do your CPUs boot in?
I would strongly recommend booting at EL2. That gives the kernel more
flexibility to perform fixups (e.g. zeroing CNTVOFF), and requires less
work in your bootloader.
> + };
> +
> + intc:interrupt-controller@71400000 {
> + compatible = "sprd,intc";
> + #interrupt-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x71400000 0 0x1000>,
> + <0 0x71500000 0 0x1000>,
> + <0 0x71600000 0 0x1000>,
> + <0 0x71700000 0 0x1000>;
> + };
This binding doesn't exist in mainline, and isn't added by this series.
I'm especially confused by the #interrupt-cells = <0>.
What exactly is this, and how do you intend to use it?
> +
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <1 13 0xff01>,
> + <1 14 0xff01>,
> + <1 11 0xff01>,
> + <1 10 0xff01>;
> + clock-frequency = <26000000>;
Please have your FW or bootloader program CNTFRQ_EL1 on each CPU, and
get rid of the clock-frequency property here.
> + };
> +
> + uart0: uart@70000000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70000000 0 0x100>;
> + interrupts = <0 2 0xf04>;
> + };
No clocks/dmas/etc necessary?
Mark.
> +
> + uart1: uart@70100000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70100000 0 0x100>;
> + interrupts = <0 3 0xf04>;
> + };
> +};
> --
> 1.7.9.5
>
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: "zhang.lyra@gmail.com" <zhang.lyra@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"jslaby@suse.cz" <jslaby@suse.cz>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"broonie@linaro.org" <broonie@linaro.org>,
"m-karicheri2@ti.com" <m-karicheri2@ti.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"artagnon@gmail.com" <artagnon@gmail.com>,
"rrichter@cavium.com" <rrichter@cavium.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"orsonzhai@gmail.com" <orsonzhai@gmail.com>,
"geng.ren@spreadtrum.com" <geng.ren@spreadtrum.com>,
"zhizhou.zhang@spreadtrum.com" <zhizhou.zhang@spreadtrum.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chunyan.zhang" <chunyan.zhang@spreadtrum.com>
Subject: Re: [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC
Date: Wed, 1 Oct 2014 12:23:33 +0100 [thread overview]
Message-ID: <20141001112332.GB13759@leverpostej> (raw)
In-Reply-To: <1411992293-7729-3-git-send-email-zhang.lyra@gmail.com>
On Mon, Sep 29, 2014 at 01:04:49PM +0100, zhang.lyra@gmail.com wrote:
> From: "zhizhou.zhang" <zhizhou.zhang@spreadtrum.com>
>
> Adds the device tree support for Spreadtrum Shark64 SoC based on ARMv8 architecture.
>
> Signed-off-by: zhizhou.zhang <zhizhou.zhang@spreadtrum.com>
> Signed-off-by: chunyan.zhang <chunyan.zhang@spreadtrum.com>
> ---
> arch/arm64/boot/dts/sprd_shark64.dts | 110 ++++++++++++++++++++++++++++++++++
> 1 file changed, 110 insertions(+)
> create mode 100644 arch/arm64/boot/dts/sprd_shark64.dts
>
> diff --git a/arch/arm64/boot/dts/sprd_shark64.dts b/arch/arm64/boot/dts/sprd_shark64.dts
> new file mode 100644
> index 0000000..537cd6d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/sprd_shark64.dts
> @@ -0,0 +1,110 @@
> +/*
> + * dts file for Spreadtrum(sprd) Shark64 SOC
> + *
> + * Copyright (C) 2014, Spreadtrum Communications Inc.
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License as
> + * published by the Free Software Foundation; either version 2 of
> + * the License, or (at your option) any later version.
> + */
> +
> +/dts-v1/;
> +
> +/memreserve/ 0x80000000 0x00010000;
What is this protecting?
Please add a comment.
> +
> +/ {
> + model = "shark64 Board";
> + compatible = "sprd,shark64";
This feels like it would make more sense as an SoC dtsi to be included
by various boards (which can override the model and compatible).
> + interrupt-parent = <&gic>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + chosen {
> + bootargs = "earlycon=serial_sprd,0x70000000";
Can we not use stdout-path for this?
> + };
> +
> + cpus {
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + cpu@0 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
Can we have the particular CPU name, please?
> + reg = <0x0 0x0>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
No PSCI?
What are you using for your bootloader/firmware?
If you must use spin-table, please give each CPU a unique release
address.
> + };
> + cpu@1 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x1>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu@2 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x2>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + cpu@3 {
> + device_type = "cpu";
> + compatible = "arm,armv8";
> + reg = <0x0 0x3>;
> + enable-method = "spin-table";
> + cpu-release-addr = <0x0 0x8000fff8>;
> + };
> + };
> +
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0 0x80000000 0 0x20000000>;
> + };
> +
> + aliases {
> + serial0 = &uart0;
> + serial1 = &uart1;
> + };
Could you move this up above chosen, please?
> +
> + gic: interrupt-controller@12001000 {
> + compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic";
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x12001000 0 0x1000>,
> + <0 0x12002000 0 0x1000>;
No GICH or GICV?
Which exception level do your CPUs boot in?
I would strongly recommend booting at EL2. That gives the kernel more
flexibility to perform fixups (e.g. zeroing CNTVOFF), and requires less
work in your bootloader.
> + };
> +
> + intc:interrupt-controller@71400000 {
> + compatible = "sprd,intc";
> + #interrupt-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x71400000 0 0x1000>,
> + <0 0x71500000 0 0x1000>,
> + <0 0x71600000 0 0x1000>,
> + <0 0x71700000 0 0x1000>;
> + };
This binding doesn't exist in mainline, and isn't added by this series.
I'm especially confused by the #interrupt-cells = <0>.
What exactly is this, and how do you intend to use it?
> +
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts = <1 13 0xff01>,
> + <1 14 0xff01>,
> + <1 11 0xff01>,
> + <1 10 0xff01>;
> + clock-frequency = <26000000>;
Please have your FW or bootloader program CNTFRQ_EL1 on each CPU, and
get rid of the clock-frequency property here.
> + };
> +
> + uart0: uart@70000000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70000000 0 0x100>;
> + interrupts = <0 2 0xf04>;
> + };
No clocks/dmas/etc necessary?
Mark.
> +
> + uart1: uart@70100000 {
> + compatible = "sprd,serial";
> + reg = <0 0x70100000 0 0x100>;
> + interrupts = <0 3 0xf04>;
> + };
> +};
> --
> 1.7.9.5
>
>
next prev parent reply other threads:[~2014-10-01 11:23 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 12:04 [PATCH 0/6] Add Spreadtrum Shark64 SoC support zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 12:04 ` zhang.lyra-Re5JQEeQqe8AvxtiuMwx3w
2014-09-29 12:04 ` [PATCH 1/6] Documentation: DT: Add bindings for Spreadtrum serial zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 13:39 ` Arnd Bergmann
2014-09-29 13:39 ` Arnd Bergmann
2014-10-01 11:21 ` Mark Rutland
2014-10-01 11:21 ` Mark Rutland
2014-10-01 11:21 ` Mark Rutland
2014-10-02 15:08 ` Orson Zhai
2014-10-02 15:08 ` Orson Zhai
2014-10-02 15:08 ` Orson Zhai
2014-09-29 12:04 ` [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 13:47 ` Arnd Bergmann
2014-09-29 13:47 ` Arnd Bergmann
2014-09-29 13:47 ` Arnd Bergmann
2014-10-01 11:17 ` Catalin Marinas
2014-10-01 11:17 ` Catalin Marinas
2014-10-01 11:17 ` Catalin Marinas
2014-10-15 3:17 ` Lyra Zhang
2014-10-15 3:17 ` Lyra Zhang
2014-10-15 3:17 ` Lyra Zhang
2014-10-20 19:00 ` Arnd Bergmann
2014-10-20 19:00 ` Arnd Bergmann
2014-10-21 1:28 ` Lyra Zhang
2014-10-21 1:28 ` Lyra Zhang
2014-10-21 1:28 ` Lyra Zhang
2014-10-01 11:23 ` Mark Rutland [this message]
2014-10-01 11:23 ` Mark Rutland
2014-10-01 11:23 ` Mark Rutland
2014-09-29 12:04 ` [PATCH 3/6] arm64: dts/Makefile: Add " zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 14:47 ` Mark Brown
2014-09-29 14:47 ` Mark Brown
2014-09-29 14:47 ` Mark Brown
2014-09-30 9:26 ` Lyra Zhang
2014-09-30 9:51 ` Lyra Zhang
2014-09-30 9:51 ` Lyra Zhang
2014-09-30 9:51 ` Lyra Zhang
2014-09-29 12:04 ` [PATCH 4/6] arm64: Add support for Spreadtrum's Shark64 SoC in Kconfig and defconfig zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 12:04 ` [PATCH 5/6] tty/serial: Add Spreadtrum's serial earlycon zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 13:36 ` Arnd Bergmann
2014-09-29 13:36 ` Arnd Bergmann
2014-10-01 13:55 ` Rob Herring
2014-10-01 13:55 ` Rob Herring
2014-10-01 13:55 ` Rob Herring
2014-09-29 14:53 ` Mark Brown
2014-09-29 14:53 ` Mark Brown
2014-09-29 14:53 ` Mark Brown
2014-09-29 12:04 ` [PATCH 6/6] Documentation: Add entry for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 12:04 ` zhang.lyra
2014-09-29 13:30 ` Arnd Bergmann
2014-09-29 13:30 ` Arnd Bergmann
2014-09-29 13:30 ` Arnd Bergmann
2014-09-29 13:59 ` Arnd Bergmann
2014-09-29 13:59 ` Arnd Bergmann
2014-09-30 7:05 ` Lyra Zhang
2014-09-30 10:08 ` Lyra Zhang
2014-09-30 10:08 ` Lyra Zhang
2014-09-29 14:08 ` [PATCH 0/6] Add Spreadtrum Shark64 SoC support Arnd Bergmann
2014-09-29 14:08 ` Arnd Bergmann
2014-09-29 14:08 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-09-29 11:48 zhang.lyra at gmail.com
2014-09-29 11:48 ` [PATCH 2/6] arm64: Add DTS support for Spreadtrum's Shark64 SoC zhang.lyra at gmail.com
2014-09-29 11:48 ` zhang.lyra
2014-09-29 14:55 ` Andreas Färber
2014-09-29 14:55 ` Andreas Färber
2014-09-29 14:55 ` Andreas Färber
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=20141001112332.GB13759@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.