* [GIT PULL] tee dynamic shm fixes for v4.16
From: Olof Johansson @ 2018-01-12 2:05 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180111124456.2fziqy4sdxq5wdlz@jax>
On Thu, Jan 11, 2018 at 01:44:56PM +0100, Jens Wiklander wrote:
> Hello arm-soc maintainers,
>
> Please pull these fixes for the previous tee-drv-dynamic-shm-for-v4.16
> pull request that is currently kept in the drivers/tee-2 branch in the
> arm-soc git.
>
> This pull request addresses the question about registering memory that
> isn't regular memory. I posted those patches some time ago with no feedback
> so far.
>
> There's also three small fixes to the dynamic shm patches that I've
> picked up from the mailing lists.
>
> Thanks,
> Jens
>
>
> The following changes since commit ef8e08d24ca84846ce639b835ebd2f15a943f42b:
>
> tee: shm: inline tee_shm_get_id() (2017-12-15 13:36:21 +0100)
>
> are available in the git repository at:
>
> https://git.linaro.org/people/jens.wiklander/linux-tee.git tee-drv-dynamic-shm+fixes-for-v4.16
>
> for you to fetch changes up to 2490cdf6435b1d3cac0dbf710cd752487c67c296:
>
> tee: shm: Potential NULL dereference calling tee_shm_register() (2018-01-09 14:34:00 +0100)
>
> ----------------------------------------------------------------
> This pull request updates the previous tee-drv-dynamic-shm-for-v4.16 pull
> request with five new patches fixing review comments and errors.
>
> Apart from three small fixes there's two larger patches that in the end
> checks that memory to be registered really is normal cached memory.
Merged into next/drivers. I noticed git.linaro.org is really slow though,
maybe you should look into getting a kernel.org account instead? It took about
a minute for the pull request to complete.
-Olof
^ permalink raw reply
* [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc
From: Olof Johansson @ 2018-01-12 2:07 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <a062d9ed0d3365b578156a780202fa533e725374.1515650104.git.viresh.kumar@linaro.org>
On Thu, Jan 11, 2018 at 11:28:51AM +0530, Viresh Kumar wrote:
> The interrupt-parent of rtc was missing, add it.
>
> Fixes: 8113ba917dfa ("ARM: SPEAr: DT: Update device nodes")
> Cc: stable at vger.kernel.org # v3.8+
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied to next/dt. Is stable really needed on this? It's been broken since
pretty much forever, and nobody has complained... :)
-Olof
^ permalink raw reply
* [PATCH 2/3] arm: spear13xx: Fix dmas cells
From: Olof Johansson @ 2018-01-12 2:07 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <6183c13fd3abcb2a6834a537a4809b6527204f10.1515650104.git.viresh.kumar@linaro.org>
On Thu, Jan 11, 2018 at 11:28:52AM +0530, Viresh Kumar wrote:
> The "dmas" cells for the designware DMA controller need to have only 3
> properties apart from the phandle: request line, src master and
> destination master. But the commit 6e8887f60f60 updated it incorrectly
> while moving from platform code to DT. Fix it.
>
> Cc: stable at vger.kernel.org # v3.10+
> Fixes: 6e8887f60f60 ("ARM: SPEAr13xx: Pass generic DW DMAC platform data from DT")
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied to next/dt.
-Olof
^ permalink raw reply
* [PATCH 3/3] arm: spear13xx: Fix spics gpio controller's warning
From: Olof Johansson @ 2018-01-12 2:07 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <9d8521e3990be6789f1ed3d5757b57c65483117b.1515650104.git.viresh.kumar@linaro.org>
On Thu, Jan 11, 2018 at 11:28:53AM +0530, Viresh Kumar wrote:
> This fixes the following warning by also sending the flags argument for
> gpio controllers:
>
> Property 'cs-gpios', cell 6 is not a phandle reference in
> /ahb/apb/spi at e0100000
>
> Fixes: 8113ba917dfa ("ARM: SPEAr: DT: Update device nodes")
> Cc: stable at vger.kernel.org # v3.8+
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Applied to next/dt.
-Olof
^ permalink raw reply
* [PATCH 2/3] ARM: tegra: paz00: drop nonstandard 'backlight-boot-off'
From: Brian Norris @ 2018-01-12 2:18 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <27065017.X8cFkIFnZg@fb07-iapwap2>
On Wed, Jan 10, 2018 at 12:31:31PM +0100, Marc Dietrich wrote:
> Hi,
>
> Am Samstag, 6. Januar 2018, 01:47:56 CET schrieb Brian Norris:
> > This was used out-of-tree as a hack for resolving issues where some
> > systems expect the backlight to turn on automatically at boot, while
> > others expect to manage the backlight status via a DRM/panel driver.
> > Those issues have since been fixed upstream in pwm_bl.c without device
> > tree hacks, and so this un-documented property should no longer be
> > useful.
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
>
> seems to work again. Thanks!
BTW, I guess I could have put this in the commit message, but the
problem that this out-of-tree property was trying to resolve was fixed
by this (and some other related patches):
d1b812945750 backlight: pwm_bl: Check the PWM state for initial backlight power state
Brian
> Reviewed-by: Marc Dietrich <marvin24@gmx.de>
>
> > ---
> > arch/arm/boot/dts/tegra20-paz00.dts | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/tegra20-paz00.dts
> > b/arch/arm/boot/dts/tegra20-paz00.dts index 30436969adc0..12c63b23ed5e
> > 100644
> > --- a/arch/arm/boot/dts/tegra20-paz00.dts
> > +++ b/arch/arm/boot/dts/tegra20-paz00.dts
> > @@ -504,8 +504,6 @@
> >
> > brightness-levels = <0 16 32 48 64 80 96 112 128 144 160 176 192 208 224
> > 240 255>; default-brightness-level = <10>;
> > -
> > - backlight-boot-off;
> > };
> >
> > clocks {
>
^ permalink raw reply
* [PATCH 0/2] Add reboot modes for LEGO MINDSTORMS EV3
From: David Lechner @ 2018-01-12 2:21 UTC (permalink / raw)
To: linux-arm-kernel
This series adds a new device tree node to declare a special memory
address that is used by the I2C bootloader on LEGO MINDSTORMS EV3
to boot into a special firmware update mode and enables the required
module to use it.
David Lechner (2):
ARM: dts: da850-lego-ev3: Add node for reboot modes
ARM: davinci_all_defconfig: enable SYSCON_REBOOT_MODE
arch/arm/boot/dts/da850-lego-ev3.dts | 17 +++++++++++++++++
arch/arm/configs/davinci_all_defconfig | 1 +
2 files changed, 18 insertions(+)
--
2.7.4
^ permalink raw reply
* [PATCH 1/2] ARM: dts: da850-lego-ev3: Add node for reboot modes
From: David Lechner @ 2018-01-12 2:21 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1515723685-19286-1-git-send-email-david@lechnology.com>
This adds a new node for reboot modes on LEGO MINDSTORMS EV3. The EV3's
bootloader looks for a magic number in the ARM local RAM and if found,
it will boot into a special firmware update mode where the flash memory
can be written via USB.
This has been testing working using the command:
# systemctl reboot loader
Signed-off-by: David Lechner <david@lechnology.com>
---
arch/arm/boot/dts/da850-lego-ev3.dts | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/da850-lego-ev3.dts b/arch/arm/boot/dts/da850-lego-ev3.dts
index e4bbf48..1cb2ff1 100644
--- a/arch/arm/boot/dts/da850-lego-ev3.dts
+++ b/arch/arm/boot/dts/da850-lego-ev3.dts
@@ -212,6 +212,23 @@
compatible = "gpio-backlight";
gpios = <&gpio 44 GPIO_ACTIVE_HIGH>;
};
+
+ /* ARM local RAM */
+ memory at ffff0000 {
+ compatible = "syscon", "simple-mfd";
+ reg = <0xffff0000 0x2000>; /* 8k */
+
+ /*
+ * The I2C bootloader looks for this magic value to either
+ * boot normally or boot into a firmware update mode.
+ */
+ reboot-mode {
+ compatible = "syscon-reboot-mode";
+ offset = <0x1ffc>;
+ mode-normal = <0x00000000>;
+ mode-loader = <0x5555aaaa>;
+ };
+ };
};
&cpu {
--
2.7.4
^ permalink raw reply related
* [PATCH 2/2] ARM: davinci_all_defconfig: enable SYSCON_REBOOT_MODE
From: David Lechner @ 2018-01-12 2:21 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1515723685-19286-1-git-send-email-david@lechnology.com>
This enables SYSCON_REBOOT_MODE as a module. This is used by LEGO
MINDSTORMS EV3 to reboot into a special firmware update mode.
Signed-off-by: David Lechner <david@lechnology.com>
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/davinci_all_defconfig b/arch/arm/configs/davinci_all_defconfig
index 282b3e4..62f853f 100644
--- a/arch/arm/configs/davinci_all_defconfig
+++ b/arch/arm/configs/davinci_all_defconfig
@@ -135,6 +135,7 @@ CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO=y
+CONFIG_SYSCON_REBOOT_MODE=m
CONFIG_BATTERY_LEGO_EV3=m
CONFIG_WATCHDOG=y
CONFIG_DAVINCI_WATCHDOG=m
--
2.7.4
^ permalink raw reply related
* [PATCH 1/2] ARM: dts: da850-lego-ev3: Add node for reboot modes
From: David Lechner @ 2018-01-12 2:22 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1515723685-19286-2-git-send-email-david@lechnology.com>
On 01/11/2018 08:21 PM, David Lechner wrote:
> This adds a new node for reboot modes on LEGO MINDSTORMS EV3. The EV3's
> bootloader looks for a magic number in the ARM local RAM and if found,
> it will boot into a special firmware update mode where the flash memory
> can be written via USB.
>
> This has been testing working using the command:
>
> # systemctl reboot loader
>
> Signed-off-by: David Lechner <david@lechnology.com>
> ---
Doh. I forgot to rebase, so this won't apply cleanly. V2 coming right up.
^ permalink raw reply
* [PATCH v2 0/2] Add reboot modes for LEGO MINDSTORMS EV3
From: David Lechner @ 2018-01-12 2:29 UTC (permalink / raw)
To: linux-arm-kernel
This series adds a new device tree node to declare a special memory
address that is used by the I2C bootloader on LEGO MINDSTORMS EV3
to boot into a special firmware update mode and enables the required
module to use it.
v2 changes:
* rebase on linux-davinci/master
David Lechner (2):
ARM: dts: da850-lego-ev3: Add node for reboot modes
ARM: davinci_all_defconfig: enable SYSCON_REBOOT_MODE
arch/arm/boot/dts/da850-lego-ev3.dts | 17 +++++++++++++++++
arch/arm/configs/davinci_all_defconfig | 1 +
2 files changed, 18 insertions(+)
--
2.7.4
^ permalink raw reply
* [PATCH v2 1/2] ARM: dts: da850-lego-ev3: Add node for reboot modes
From: David Lechner @ 2018-01-12 2:29 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1515724191-30499-1-git-send-email-david@lechnology.com>
This adds a new node for reboot modes on LEGO MINDSTORMS EV3. The EV3's
bootloader looks for a magic number in the ARM local RAM and if found,
it will boot into a special firmware update mode where the flash memory
can be written via USB.
This has been testing working using the command:
# systemctl reboot loader
Signed-off-by: David Lechner <david@lechnology.com>
---
arch/arm/boot/dts/da850-lego-ev3.dts | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/da850-lego-ev3.dts b/arch/arm/boot/dts/da850-lego-ev3.dts
index 81942ae..2e85080 100644
--- a/arch/arm/boot/dts/da850-lego-ev3.dts
+++ b/arch/arm/boot/dts/da850-lego-ev3.dts
@@ -184,6 +184,23 @@
io-channel-names = "voltage", "current";
rechargeable-gpios = <&gpio 136 GPIO_ACTIVE_LOW>;
};
+
+ /* ARM local RAM */
+ memory at ffff0000 {
+ compatible = "syscon", "simple-mfd";
+ reg = <0xffff0000 0x2000>; /* 8k */
+
+ /*
+ * The I2C bootloader looks for this magic value to either
+ * boot normally or boot into a firmware update mode.
+ */
+ reboot-mode {
+ compatible = "syscon-reboot-mode";
+ offset = <0x1ffc>;
+ mode-normal = <0x00000000>;
+ mode-loader = <0x5555aaaa>;
+ };
+ };
};
&pmx_core {
--
2.7.4
^ permalink raw reply related
* [PATCH v2 2/2] ARM: davinci_all_defconfig: enable SYSCON_REBOOT_MODE
From: David Lechner @ 2018-01-12 2:29 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1515724191-30499-1-git-send-email-david@lechnology.com>
This enables SYSCON_REBOOT_MODE as a module. This is used by LEGO
MINDSTORMS EV3 to reboot into a special firmware update mode.
Signed-off-by: David Lechner <david@lechnology.com>
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/davinci_all_defconfig b/arch/arm/configs/davinci_all_defconfig
index 026154c..bcb70c2 100644
--- a/arch/arm/configs/davinci_all_defconfig
+++ b/arch/arm/configs/davinci_all_defconfig
@@ -126,6 +126,7 @@ CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO=y
+CONFIG_SYSCON_REBOOT_MODE=m
CONFIG_BATTERY_LEGO_EV3=m
CONFIG_WATCHDOG=y
CONFIG_DAVINCI_WATCHDOG=m
--
2.7.4
^ permalink raw reply related
* [PATCH] arm64: dts: angler: add pstore-ramoops support
From: Jeremy McNicoll @ 2018-01-12 2:33 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514446709-19347-1-git-send-email-zhuoweizhang@yahoo.com>
On Thu, Dec 28, 2017 at 02:38:29AM -0500, zhuoweizhang at yahoo.com wrote:
> From: Zhuowei Zhang <zhuoweizhang@yahoo.com>
>
> Support pstore-ramoops for retrieving kernel oops and panics after reboot.
>
> The address and configs are taken from the downstream kernel's device tree.
>
> Signed-off-by: Zhuowei Zhang <zhuoweizhang@yahoo.com>
> ---
> arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts b/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> index dfa08f5..9ce3a6e 100644
> --- a/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> +++ b/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> @@ -37,4 +37,19 @@
> pinctrl-1 = <&blsp1_uart2_sleep>;
> };
> };
> +
> + reserved-memory {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + ramoops at 1fe00000 {
> + compatible = "ramoops";
> + reg = <0 0x1fe00000 0 0x00200000>;
Downstream doesn't use 0x0 to denote 0. I am fine with this, if
someone has a concern or issue with it we can change it before merging.
> + console-size = <0x100000>;
> + record-size = <0x10000>;
> + ftrace-size = <0x10000>;
> + pmsg-size = <0x80000>;
We could pad this with leading 0's but I find this much easier
to read.
> + };
> + };
> };
Thank you very much for taking the time to send this.
Acked-by: Jeremy McNicoll <jeremymc@redhat.com>
^ permalink raw reply
* [GIT PULL] TI DaVinci SoC updates for v4.16 (part 2)
From: David Lechner @ 2018-01-12 2:36 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180112013602.q2sm25s6o3oebkbj@localhost>
On 01/11/2018 07:36 PM, Olof Johansson wrote:
> On Wed, Jan 10, 2018 at 04:55:05PM +0530, Sekhar Nori wrote:
>> The following changes since commit 23bbeaef90ab7607d03428bbb708efe44f43c761:
>>
>> ARM: davinci: constify gpio_led (2018-01-05 19:28:41 +0530)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v4.16/soc-p2
>>
>> for you to fetch changes up to 0808d3260456aaba061fe06ead31d578c8bdc936:
>>
>> ARM: davinci: remove watchdog reset (2018-01-10 14:38:07 +0530)
>>
>> ----------------------------------------------------------------
>> A patch to shift to using watchdog timer for DaVinci restart functionality.
>> The driver support is present in linux-next as 71d1f058844d "watchdog:
>> davinci_wdt: add restart function"
>
> Hi,
>
> So if this is merged before the driver is merged, what happens?
Then reboot hangs.
> Might
> be better to hold off a release to avoid regressions?
>
I'll let Sekhar answer this one.
^ permalink raw reply
* [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc
From: Viresh Kumar @ 2018-01-12 3:22 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180112020711.6gp2pnsxxjzelidq@localhost>
On 11-01-18, 18:07, Olof Johansson wrote:
> On Thu, Jan 11, 2018 at 11:28:51AM +0530, Viresh Kumar wrote:
> > The interrupt-parent of rtc was missing, add it.
> >
> > Fixes: 8113ba917dfa ("ARM: SPEAr: DT: Update device nodes")
> > Cc: stable at vger.kernel.org # v3.8+
> > Reported-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Applied to next/dt. Is stable really needed on this? It's been broken since
> pretty much forever, and nobody has complained... :)
Not sure. Just thought it may be useful for someone somewhere :)
--
viresh
^ permalink raw reply
* [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc
From: Olof Johansson @ 2018-01-12 3:23 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180112032223.GK3626@vireshk-i7>
On Thu, Jan 11, 2018 at 7:22 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 11-01-18, 18:07, Olof Johansson wrote:
>> On Thu, Jan 11, 2018 at 11:28:51AM +0530, Viresh Kumar wrote:
>> > The interrupt-parent of rtc was missing, add it.
>> >
>> > Fixes: 8113ba917dfa ("ARM: SPEAr: DT: Update device nodes")
>> > Cc: stable at vger.kernel.org # v3.8+
>> > Reported-by: Arnd Bergmann <arnd@arndb.de>
>> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>>
>> Applied to next/dt. Is stable really needed on this? It's been broken since
>> pretty much forever, and nobody has complained... :)
>
> Not sure. Just thought it may be useful for someone somewhere :)
Ok. Left the tags there, but didn't merge into fixes since we're late
in -rc and this didn't seem critical at this time.
-Olof
^ permalink raw reply
* [PATCH 05/12] arm64: dts: mt7622: add PMIC MT6380 related nodes
From: Sean Wang @ 2018-01-12 3:33 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAOFm3uEkqKGhsziwf6o3i2o0Ua=ah4CHgh-Hr+aC4zHxH3mZzQ@mail.gmail.com>
Hi, Philippe
Currently, I'm really confused about what usage STYLE of SPDX license
identifier I should use for each type of file.
could you point me where I can find the related document describing SPDX
usage style for those files expected by the community in the future?
I found more than one way STYLE of SPDX present at current code, for
example as below. If there's no absolute definition for them, and then
which way that is better?
1)
for *.dts, applied with "// " at head or within " /* */ " not at head
such as
arch/arm/boot/dts/bcm953012hr.dts:2: * SPDX-License-Identifier:
BSD-3-Clause
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts:4: *
SPDX-License-Identifier: (GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-ld6b-ref.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/owl-s500-guitar-bb-rev-b.dts:4: *
SPDX-License-Identifier: (GPL-2.0+ OR MIT)
arch/arm/boot/dts/keystone-k2g-ice.dts:6: * SPDX-License-Identifier:
GPL-2.0
arch/arm/boot/dts/uniphier-pro4-sanji.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/owl-s500-cubieboard6.dts:6: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-pro4-ace.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-sld8-ref.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-pro4-ref.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-pxs2-gentil.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-pxs2-vodka.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm/boot/dts/uniphier-ld4-ref.dts:7: * SPDX-License-Identifier:
(GPL-2.0+ OR MIT)
arch/arm64/boot/dts/nvidia/tegra132-norrin.dts:1://
SPDX-License-Identifier: GPL-2.0
arch/arm64/boot/dts/nvidia/tegra186-p2771-0000.dts:1://
SPDX-License-Identifier: GPL-2.0
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts:1://
SPDX-License-Identifier: GPL-2.0
arch/arm64/boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts:1://
SPDX-License-Identifier: GPL-2.0
arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts:1:// SPDX-License-Identifier:
GPL-2.0
arch/arm64/boot/dts/arm/foundation-v8.dts:1:// SPDX-License-Identifier:
GPL-2.0
arch/arm64/boot/dts/arm/foundation-v8-gicv3.dts:1://
SPDX-License-Identifier: GPL-2.0
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts:1://
SPDX-License-Identifier: GPL-2.0
2)
for *.c, applied with "// " at head or within " /* */ " not at head
such as
drivers/base/memory.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/base/devtmpfs.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/base/node.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/base/dma-coherent.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/cpuidle/cpuidle-pseries.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/cpuidle/cpuidle-powernv.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/mtd/maps/tsunami_flash.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/mtd/maps/physmap_of_gemini.c:1:// SPDX-License-Identifier:
GPL-2.0
drivers/mtd/tests/mtd_test.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/mtd/onenand/onenand_bbt.c:1:// SPDX-License-Identifier: GPL-2.0
drivers/media/common/b2c2/flexcop-i2c.c:1:// SPDX-License-Identifier:
GPL-2.0
drivers/soc/xilinx/zynqmp/pm.c:10: * SPDX-License-Identifier: GPL-2.0+
drivers/soc/amlogic/meson-gx-pwrc-vpu.c:5: * SPDX-License-Identifier:
GPL-2.0+
drivers/soc/amlogic/meson-gx-socinfo.c:5: * SPDX-License-Identifier:
GPL-2.0+
drivers/soc/amlogic/meson-mx-socinfo.c:4: * SPDX-License-Identifier:
GPL-2.0+
drivers/i2c/busses/i2c-sprd.c:4: * SPDX-License-Identifier: (GPL-2.0+ OR
MIT)
drivers/spi/spi-meson-spicc.c:7: * SPDX-License-Identifier: GPL-2.0+
drivers/spi/spi-sprd-adi.c:4: * SPDX-License-Identifier: GPL-2.0
drivers/dma/sprd-dma.c:4: * SPDX-License-Identifier: GPL-2.0
3)
for *.h, applied with "// " at head or within " /* */ " at head
such as
drivers/usb/dwc3/gadget.h:1:// SPDX-License-Identifier: GPL-2.0
drivers/usb/dwc3/io.h:1:// SPDX-License-Identifier: GPL-2.0
drivers/usb/dwc3/debug.h:1:// SPDX-License-Identifier: GPL-2.0
drivers/usb/dwc3/core.h:1:// SPDX-License-Identifier: GPL-2.0
drivers/usb/atm/usbatm.h:1:// SPDX-License-Identifier: GPL-2.0+
drivers/usb/misc/rio500_usb.h:1:// SPDX-License-Identifier: GPL-2.0+
drivers/usb/misc/sisusbvga/sisusb.h:1:// SPDX-License-Identifier:
(GPL-2.0 OR BSD-3-Clause)
drivers/usb/misc/sisusbvga/sisusb_init.h:1:// SPDX-License-Identifier:
(GPL-2.0+ OR BSD-3-Clause)
drivers/usb/misc/sisusbvga/sisusb_struct.h:1:// SPDX-License-Identifier:
(GPL-2.0+ OR BSD-3-Clause)
drivers/usb/misc/usb_u132.h:1:// SPDX-License-Identifier: GPL-2.0
drivers/tty/serial/dz.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/apbuart.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/sunzilog.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/zs.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/sh-sci.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/cpm_uart/cpm_uart_cpm1.h:1:/*
SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/cpm_uart/cpm_uart_cpm2.h:1:/*
SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/sunsab.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/amba-pl011.h:1:/* SPDX-License-Identifier: GPL-2.0 */
drivers/tty/serial/crisv10.h:1:/* SPDX-License-Identifier: GPL-2.0 */
4)
no issue, Makefile, or Kconfig, definitely applied with "# " at head
Sean
On Fri, 2018-01-05 at 09:21 +0100, Philippe Ombredanne wrote:
> Sean,
>
> On Fri, Jan 5, 2018 at 4:42 AM, Sean Wang <sean.wang@mediatek.com> wrote:
> > On Thu, 2018-01-04 at 11:27 +0100, Philippe Ombredanne wrote:
> >> Sean,
> >>
> >> On Thu, Jan 4, 2018 at 10:40 AM, <sean.wang@mediatek.com> wrote:
> >> > From: Sean Wang <sean.wang@mediatek.com>
> >> >
> >> > Enable pwrap and MT6380 on mt7622-rfb1 board. Also add all mt6380
> >> > regulator nodes in an alone file to allow similar boards using MT6380
> >> > able to resue the configuration.
> >> >
> >> > Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> >> > Cc: Mark Brown <broonie@kernel.org>
> >> > Cc: Matthias Brugger <matthias.bgg@gmail.com>
> >> > ---
> >> > arch/arm64/boot/dts/mediatek/mt6380.dtsi | 91 ++++++++++++++++++++++++++++
> >> > arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 8 +++
> >> > arch/arm64/boot/dts/mediatek/mt7622.dtsi | 12 ++++
> >> > 3 files changed, 111 insertions(+)
> >> > create mode 100644 arch/arm64/boot/dts/mediatek/mt6380.dtsi
> >> >
> >> > diff --git a/arch/arm64/boot/dts/mediatek/mt6380.dtsi b/arch/arm64/boot/dts/mediatek/mt6380.dtsi
> >> > new file mode 100644
> >> > index 0000000..7eb7dc2
> >> > --- /dev/null
> >> > +++ b/arch/arm64/boot/dts/mediatek/mt6380.dtsi
> >> > @@ -0,0 +1,91 @@
> >> > +/*
> >> > + * Copyright (c) 2018 MediaTek Inc.
> >> > + * Author: Chenglin Xu <chenglin.xu@mediatek.com>
> >> > + * Sean Wang <sean.wang@mediatek.com>
> >> > + *
> >> > + * This program is free software; you can redistribute it and/or modify
> >> > + * it under the terms of the GNU General Public License version 2 as
> >> > + * published by the Free Software Foundation.
> >> > + *
> >> > + * This program is distributed in the hope that it will be useful,
> >> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> >> > + * GNU General Public License for more details.
> >> > + */
> >>
> >> Would you mind using SPDX tags instead of this fine but long legalese?
> >> This is documented in Thomas patches [1].
> >
> >> Also if you could spread the word in your team, this would earn you
> >> good karma points.
> >> Thank you!
> >>
> >> [1] https://lkml.org/lkml/2017/12/28/323
> >
> >
> > Hi, Philippe
> >
> > thanks for your suggestion
> >
> > Certainly, this can be replaced with
> >
> > SPDX-License-Identifier: GPL-2.0
> >
> > most drivers from MediaTek use the similar disclaimer, it should be fine
> > to use SPDX tags instead.
> >
> > Sean
> >
>
> Thank you! that's great.
>
^ permalink raw reply
* [PATCH] ARM: dts: Fix missing "device_type" in Aspeed memory nodes
From: Benjamin Herrenschmidt @ 2018-01-12 4:56 UTC (permalink / raw)
To: linux-arm-kernel
When Joel removed skeleton.dtsi, the Aspeed boards lost their
"device_type" property in the memory node. Since a number of
these still use old bootloaders that won't patch it properly,
booting breaks as a result.
This adds the property back to the individual nodes.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
Should we just have a skeleton in the g4 and g5 dtsi with just
that property instead ?
---
arch/arm/boot/dts/aspeed-ast2500-evb.dts | 1 +
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 1 +
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 1 +
arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts | 1 +
arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts | 1 +
arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts | 1 +
6 files changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-ast2500-evb.dts b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
index ede11c597673..0c3f14d05046 100644
--- a/arch/arm/boot/dts/aspeed-ast2500-evb.dts
+++ b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
@@ -17,6 +17,7 @@
};
memory at 80000000 {
+ device_type = "memory";
reg = <0x80000000 0x20000000>;
};
};
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts b/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
index 4379d09a261f..9d18cce971be 100644
--- a/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts
@@ -13,6 +13,7 @@
};
memory at 40000000 {
+ device_type = "memory";
reg = <0x40000000 0x20000000>;
};
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts b/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
index 623b6ab42021..cd06d5738782 100644
--- a/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts
@@ -13,6 +13,7 @@
};
memory at 80000000 {
+ device_type = "memory";
reg = <0x80000000 0x20000000>;
};
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
index 5f9049d2c4c3..b64553a083b0 100644
--- a/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
@@ -14,6 +14,7 @@
};
memory at 80000000 {
+ device_type = "memory";
reg = <0x80000000 0x20000000>;
};
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts b/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts
index c881484a85cf..f3f5b3279e52 100644
--- a/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts
@@ -13,6 +13,7 @@
};
memory at 80000000 {
+ device_type = "memory";
reg = <0x80000000 0x40000000>;
};
diff --git a/arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts b/arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts
index 76aa6ea1f988..ca7a4ae9ed08 100644
--- a/arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts
@@ -13,6 +13,7 @@
};
memory at 40000000 {
+ device_type = "memory";
reg = <0x40000000 0x8000000>;
};
^ permalink raw reply related
* [GIT PULL] TI DaVinci SoC updates for v4.16 (part 2)
From: Sekhar Nori @ 2018-01-12 5:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <db68cbec-a3e2-9c9e-e09c-f3d9a9972636@lechnology.com>
Hi Olof,
On Friday 12 January 2018 08:06 AM, David Lechner wrote:
> On 01/11/2018 07:36 PM, Olof Johansson wrote:
>> On Wed, Jan 10, 2018 at 04:55:05PM +0530, Sekhar Nori wrote:
>>> The following changes since commit
>>> 23bbeaef90ab7607d03428bbb708efe44f43c761:
>>>
>>> ?? ARM: davinci: constify gpio_led (2018-01-05 19:28:41 +0530)
>>>
>>> are available in the git repository at:
>>>
>>> ??
>>> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git
>>> tags/davinci-for-v4.16/soc-p2
>>>
>>> for you to fetch changes up to 0808d3260456aaba061fe06ead31d578c8bdc936:
>>>
>>> ?? ARM: davinci: remove watchdog reset (2018-01-10 14:38:07 +0530)
>>>
>>> ----------------------------------------------------------------
>>> A patch to shift to using watchdog timer for DaVinci restart
>>> functionality.
>>> The driver support is present in linux-next as 71d1f058844d "watchdog:
>>> davinci_wdt: add restart function"
>>
>> Hi,
>>
>> So if this is merged before the driver is merged, what happens?
>
> Then reboot hangs.
Yes. I did request[1] an immutable branch with just the driver change
applied, but looks like the message was lost and the current driver
change is applied over many other watchdog changes.
>
>> Might
>> be better to hold off a release to avoid regressions?
The main reason I sent it out anyway is because this cleanup is a
dependency to move to common clock framework and I want to reduce those
to a minimum to have a good chance of migrating to it in v4.17.
If the watchdog driver change never makes it (very low chance), then I
can resend a revert for -rc2. If ARM-SoC is merged before watchdog, yes,
during a short while in merge window reboot will be broken. But I
figured its a risk worth taking to have a chance of getting this into v4.16.
If you have a "send these late" branch, it will be nice to put it in
there. If this is too much uncertainty, then okay, lets hold for v4.17.
Thanks,
Sekhar
[1] https://www.spinics.net/lists/linux-watchdog/msg12965.html
^ permalink raw reply
* [PATCH] phy: work around 'phys' references to usb-phy devices
From: Kishon Vijay Abraham I @ 2018-01-12 6:00 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <87d12guups.fsf@anholt.net>
Hi Arnd,
On Thursday 11 January 2018 11:46 PM, Eric Anholt wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
>> On Thu, Jan 11, 2018 at 2:30 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>> On Thursday 11 January 2018 02:27 AM, Arnd Bergmann wrote:
>>>> On Mon, Jan 8, 2018 at 7:32 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>>>> On Monday 08 January 2018 06:31 PM, Arnd Bergmann wrote:
>>>>>> Stefan Wahren reports a problem with a warning fix that was merged
>>>>>> ---
>>>>>> This obviously needs to be tested, I wrote this up as a reply to
>>>>>> Stefan's bug report. I'm fairly sure that I covered all usb-phy
>>>>>> driver strings here. My goal is to have a fix merged into 4.15
>>>>>> rather than reverting all the DT fixes.
>>>>>
>>>>> Shouldn't the fix be in phy consumer drivers to not return error if it's able
>>>>> to find the phy either using usb-phy or generic phy?
>>>>
>>>> Stefan has posted a patch to that effect now, but I fear that might be
>>>> a little fragile, in particular this short before the release with the
>>>> regression
>>>> in place.
>>>>
>>>> The main problem is that we'd have to change the generic
>>>> usb_add_hcd() function in addition to dwc2 and dwc3 to ignore
>>>> -EPROBE_DEFER from phy_get() whenever usb_get_phy_dev()
>>>> has already succeeded.
>>>>
>>>> If there is any HCD that relies on usb_add_hcd() to get both the
>>>> usb_phy and the phy structures, and it may need to defer probing
>>>> when the latter one isn't ready yet, that fix would break another
>>>> driver.
>>>
>>> hmm.. IMO the better thing right now would be to revert the dt patch which adds
>>> #phy-cells.
>>> We have to see if there are better fixes in order to add #phy-cells warning fix
>>> in stable tree.
>>
>> Let's see which patches that would be, I think this is the full list of
>> nodes that got an extra #phy-cells:
>>
>> c22fe696157d ARM: dts: Fix dm814x missing phy-cells property
>> f0e11ff8ff65 ARM: dts: am33xx: Add missing #phy-cells to ti,am335x-usb-phy
>> c5bbf358b790 arm: dts: nspire: Add missing #phy-cells to usb-nop-xceiv
>> 44e5dced2ef6 arm: dts: marvell: Add missing #phy-cells to usb-nop-xceiv
>> 014d6da6cb25 ARM: dts: bcm283x: Fix DTC warnings about missing phy-cells
>> f568f6f554b8 ARM: dts: omap: Add missing #phy-cells to usb-nop-xceiv
>>
>> plus a couple in linux-next:
>>
>> d745d5f277bf ARM: dts: imx51-zii-rdu1: Add missing #phy-cells to usb-nop-xceiv
>> 915fbe59cbf2 ARM: dts: imx: Add missing #phy-cells to usb-nop-xceiv
>>
>> It's a lot of patches to revert, and I guess it would get us back to hundreds
>> of warnings in an allmodconfig build, so I'd first try to come up with
>> ways to prove that at least some of them can stay.
>>
>> Almost all the warnings are about "usb-nop-xceiv" phys, the only exceptions
>> I could find are the OMAP ones (the first two patches), which use
>> "ti,am335x-usb-phy" and are referenced from a "ti,musb-am33xx". That
>> particular driver is not affected by the bug, so we can leave that in.
>>
>> To deal with all the "usb-nop-xceiv" references including the one that
>> Stefan reported, we could use a much simpler version of my earlier
>> patch, do you think this is any better?
yeah, this looks simpler.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
In case you want to take this patch yourself
Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
(or let me know if I have to create a separate pull request for Greg)
Thanks
Kishon
>>
>> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
>> index b4964b067aec..f056d8fb3921 100644
>> --- a/drivers/phy/phy-core.c
>> +++ b/drivers/phy/phy-core.c
>> @@ -410,6 +410,10 @@ static struct phy *_of_phy_get(struct device_node
>> *np, int index)
>> if (ret)
>> return ERR_PTR(-ENODEV);
>>
>> + /* This phy type handled by the usb-phy subsystem for now */
>> + if (of_device_is_compatible("usb-nop-xceiv"))
>> + return ERR_PTR(-ENODEV);
>> +
>> mutex_lock(&phy_provider_mutex);
>> phy_provider = of_phy_provider_lookup(args.np);
>> if (IS_ERR(phy_provider) || !try_module_get(phy_provider->owner)) {
>
> This seems like a nice workaround!
>
^ permalink raw reply
* [PATCH 1/2] dts: ARM: Aspeed-g5: Add missing USB clock and pinmux
From: Benjamin Herrenschmidt @ 2018-01-12 6:02 UTC (permalink / raw)
To: linux-arm-kernel
This adds the clock and pinmux default references to
the Aspeed G5 SoC base device-tree for USB. The clk and
pinmux drivers already know about these.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/arm/boot/dts/aspeed-g5.dtsi | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index 8b3986a941f5..3c5c9b952ba8 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/arm/boot/dts/aspeed-g5.dtsi
@@ -142,6 +142,7 @@
compatible = "aspeed,ast2500-ehci", "generic-ehci";
reg = <0x1e6a1000 0x100>;
interrupts = <5>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
status = "disabled";
};
@@ -149,6 +150,7 @@
compatible = "aspeed,ast2500-ehci", "generic-ehci";
reg = <0x1e6a3000 0x100>;
interrupts = <13>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBPORT2CLK>;
status = "disabled";
};
@@ -157,6 +159,7 @@
reg = <0x1e6b0000 0x100>;
interrupts = <14>;
#ports = <2>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBUHCICLK>;
status = "disabled";
};
@@ -1387,6 +1390,21 @@
groups = "USBCKI";
};
+ pinctrl_usb2ah_default: usb2ah_default {
+ function = "USB2AH";
+ groups = "USB2AH";
+ };
+
+ pinctrl_usb11bhid_default: usb11bhid_default {
+ function = "USB11BHID";
+ groups = "USB11BHID";
+ };
+
+ pinctrl_usb2bh_default: usb2bh_default {
+ function = "USB2BH";
+ groups = "USB2BH";
+ };
+
pinctrl_vgabiosrom_default: vgabiosrom_default {
function = "VGABIOSROM";
groups = "VGABIOSROM";
--
2.14.3
^ permalink raw reply related
* [PATCH 2/2] dts: ARM: Aspeed: Enable USB ports on eval board
From: Benjamin Herrenschmidt @ 2018-01-12 6:02 UTC (permalink / raw)
To: linux-arm-kernel
This enables both USB ports as host with EHCI and UHCI
attached to them.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/arm/boot/dts/aspeed-ast2500-evb.dts | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-ast2500-evb.dts b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
index 6946c8610c4c..0c3f14d05046 100644
--- a/arch/arm/boot/dts/aspeed-ast2500-evb.dts
+++ b/arch/arm/boot/dts/aspeed-ast2500-evb.dts
@@ -80,3 +80,21 @@
reg = <0x4d>;
};
};
+
+&ehci0 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_usb2ah_default>;
+};
+
+&ehci1 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_usb2bh_default>;
+};
+
+&uhci {
+ status = "okay";
+
+ /* No pinctrl, this follows the above EHCI settings */
+};
^ permalink raw reply related
* [PATCH v5 01/44] dt-bindings: clock: Add new bindings for TI Davinci PLL clocks
From: Sekhar Nori @ 2018-01-12 6:03 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <c1e27013-cbad-3b09-0e0d-f68d75162c1f@lechnology.com>
On Friday 12 January 2018 03:16 AM, David Lechner wrote:
>
> Sekhar, have you had a chance to look at the rest of the patches in the
> series?
Not yet. Sorry about the slow (and piecemeal) review.
>
> I'll wait a bit before I send a v6 to see if any other comments come.
Yes. I will let you know once I am done reviewing the whole series.
Thanks,
Sekhar
^ permalink raw reply
* [PATCH v2 05/12] drm/bridge/synopsys: dw-hdmi: Add deinit callback
From: Chen-Yu Tsai @ 2018-01-12 6:12 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180110192512.19684-6-jernej.skrabec@siol.net>
On Thu, Jan 11, 2018 at 3:25 AM, Jernej Skrabec <jernej.skrabec@siol.net> wrote:
> Some SoCs, like Allwinner A83T, have to do additional cleanup when
> HDMI driver unloads. When using DW HDMI through DRM bridge API, there is
> no place to store driver's private data so it can be accessed in unbind
> function. Because of that, add deinit function which is called at the
> very end, so drivers can do a proper cleanup.
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
8242ecbd597d ("drm/bridge/synopsys: stop clobbering drvdata"), which is
already in drm-misc-next, is a much saner solution. :)
ChenYu
^ permalink raw reply
* [PATCH 1/2 v2] ARM: dts: Add Aspeed SoC USB controllers to device-tree
From: Benjamin Herrenschmidt @ 2018-01-12 6:21 UTC (permalink / raw)
To: linux-arm-kernel
This adds the USB controllers to the DT template of the
AST24xx and AST25xx SoCs.
This patch doesn't enable them by default on any board specific
.dts yet. This will be done when we have the necessary clock/reset
and pinmux support. In the meantime though, this will work if
u-boot configures things properly.
For the AST2400 I only added pinmux definition for port 1
which is dual USB1/USB2. There are additional USB1 only ports
that might require more work but I don't have HW to test at
hand so I'm leaving that to whoever cares.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
v2: Previous patch was missing actually adding the nodes
(which was an old patch in my tree I had forgotten to
merge).
arch/arm/boot/dts/aspeed-g4.dtsi | 27 +++++++++++++++++++++++++++
arch/arm/boot/dts/aspeed-g5.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-g4.dtsi b/arch/arm/boot/dts/aspeed-g4.dtsi
index b0d8431a3700..e55f2ad5de59 100644
--- a/arch/arm/boot/dts/aspeed-g4.dtsi
+++ b/arch/arm/boot/dts/aspeed-g4.dtsi
@@ -103,6 +103,23 @@
status = "disabled";
};
+ ehci0: usb at 1e6a1000 {
+ compatible = "aspeed,ast2400-ehci", "generic-ehci";
+ reg = <0x1e6a1000 0x100>;
+ interrupts = <5>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
+ status = "disabled";
+ };
+
+ uhci: usb at 1e6b0000 {
+ compatible = "aspeed,ast2400-uhci", "generic-uhci";
+ reg = <0x1e6b0000 0x100>;
+ interrupts = <14>;
+ #ports = <3>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBUHCICLK>;
+ status = "disabled";
+ };
+
apb {
compatible = "simple-bus";
#address-cells = <1>;
@@ -1227,6 +1244,16 @@
groups = "USBCKI";
};
+ pinctrl_usb2h_default: usb2h_default {
+ function = "USB2H1";
+ groups = "USB2H1";
+ };
+
+ pinctrl_usb2d_default: usb2d_default {
+ function = "USB2D1";
+ groups = "USB2D1";
+ };
+
pinctrl_vgabios_rom_default: vgabios_rom_default {
function = "VGABIOS_ROM";
groups = "VGABIOS_ROM";
diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index 40de3b66c33f..655258edee24 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/arm/boot/dts/aspeed-g5.dtsi
@@ -138,6 +138,31 @@
status = "disabled";
};
+ ehci0: usb at 1e6a1000 {
+ compatible = "aspeed,ast2500-ehci", "generic-ehci";
+ reg = <0x1e6a1000 0x100>;
+ interrupts = <5>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
+ status = "disabled";
+ };
+
+ ehci1: usb at 1e6a3000 {
+ compatible = "aspeed,ast2500-ehci", "generic-ehci";
+ reg = <0x1e6a3000 0x100>;
+ interrupts = <13>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBPORT2CLK>;
+ status = "disabled";
+ };
+
+ uhci: usb at 1e6b0000 {
+ compatible = "aspeed,ast2500-uhci", "generic-uhci";
+ reg = <0x1e6b0000 0x100>;
+ interrupts = <14>;
+ #ports = <2>;
+ clocks = <&syscon ASPEED_CLK_GATE_USBUHCICLK>;
+ status = "disabled";
+ };
+
apb {
compatible = "simple-bus";
#address-cells = <1>;
@@ -1358,6 +1383,21 @@
groups = "USBCKI";
};
+ pinctrl_usb2ah_default: usb2ah_default {
+ function = "USB2AH";
+ groups = "USB2AH";
+ };
+
+ pinctrl_usb11bhid_default: usb11bhid_default {
+ function = "USB11BHID";
+ groups = "USB11BHID";
+ };
+
+ pinctrl_usb2bh_default: usb2bh_default {
+ function = "USB2BH";
+ groups = "USB2BH";
+ };
+
pinctrl_vgabiosrom_default: vgabiosrom_default {
function = "VGABIOSROM";
groups = "VGABIOSROM";
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox