* [PATCH] ARM: Fix i2c-gpio GPIO descriptor tables
From: Linus Walleij @ 2018-05-26 16:37 UTC (permalink / raw)
To: linux-arm-kernel
I used bad names in my clumsiness when rewriting many board
files to use GPIO descriptors instead of platform data. A few
had the platform_device ID set to -1 which would indeed give
the device name "i2c-gpio".
But several had it set to >=0 which gives the names
"i2c-gpio.0", "i2c-gpio.1" ...
Fix the offending instances in the ARM tree. Sorry for the
mess.
Fixes: b2e63555592f ("i2c: gpio: Convert to use descriptors")
Cc: Wolfram Sang <wsa@the-dreams.de>
Cc: Simon Guinot <simon.guinot@sequanux.org>
Reported-by: Simon Guinot <simon.guinot@sequanux.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
ARM SoC folks: please apply this directly for fixes if
it check out fine.
(The fact that it took so long to discover tells us something
about how used these board files are.)
---
arch/arm/mach-ep93xx/core.c | 2 +-
arch/arm/mach-ixp4xx/avila-setup.c | 2 +-
arch/arm/mach-ixp4xx/dsmg600-setup.c | 2 +-
arch/arm/mach-ixp4xx/fsg-setup.c | 2 +-
arch/arm/mach-ixp4xx/ixdp425-setup.c | 2 +-
arch/arm/mach-ixp4xx/nas100d-setup.c | 2 +-
arch/arm/mach-ixp4xx/nslu2-setup.c | 2 +-
arch/arm/mach-pxa/palmz72.c | 2 +-
arch/arm/mach-pxa/viper.c | 4 ++--
arch/arm/mach-sa1100/simpad.c | 2 +-
10 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-ep93xx/core.c b/arch/arm/mach-ep93xx/core.c
index e70feec6fad5..0581ffbedddd 100644
--- a/arch/arm/mach-ep93xx/core.c
+++ b/arch/arm/mach-ep93xx/core.c
@@ -323,7 +323,7 @@ void __init ep93xx_register_eth(struct ep93xx_eth_data *data, int copy_addr)
/* All EP93xx devices use the same two GPIO pins for I2C bit-banging */
static struct gpiod_lookup_table ep93xx_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
/* Use local offsets on gpiochip/port "G" */
GPIO_LOOKUP_IDX("G", 1, NULL, 0,
diff --git a/arch/arm/mach-ixp4xx/avila-setup.c b/arch/arm/mach-ixp4xx/avila-setup.c
index 77def6169f50..44cbbce6bda6 100644
--- a/arch/arm/mach-ixp4xx/avila-setup.c
+++ b/arch/arm/mach-ixp4xx/avila-setup.c
@@ -51,7 +51,7 @@ static struct platform_device avila_flash = {
};
static struct gpiod_lookup_table avila_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", AVILA_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-ixp4xx/dsmg600-setup.c b/arch/arm/mach-ixp4xx/dsmg600-setup.c
index 0f5c99941a7d..397190f3a8da 100644
--- a/arch/arm/mach-ixp4xx/dsmg600-setup.c
+++ b/arch/arm/mach-ixp4xx/dsmg600-setup.c
@@ -70,7 +70,7 @@ static struct platform_device dsmg600_flash = {
};
static struct gpiod_lookup_table dsmg600_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", DSMG600_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-ixp4xx/fsg-setup.c b/arch/arm/mach-ixp4xx/fsg-setup.c
index 033f79b35d51..f0a152e365b1 100644
--- a/arch/arm/mach-ixp4xx/fsg-setup.c
+++ b/arch/arm/mach-ixp4xx/fsg-setup.c
@@ -56,7 +56,7 @@ static struct platform_device fsg_flash = {
};
static struct gpiod_lookup_table fsg_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", FSG_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-ixp4xx/ixdp425-setup.c b/arch/arm/mach-ixp4xx/ixdp425-setup.c
index b168e2fbdbeb..3ec829d52cdd 100644
--- a/arch/arm/mach-ixp4xx/ixdp425-setup.c
+++ b/arch/arm/mach-ixp4xx/ixdp425-setup.c
@@ -124,7 +124,7 @@ static struct platform_device ixdp425_flash_nand = {
#endif /* CONFIG_MTD_NAND_PLATFORM */
static struct gpiod_lookup_table ixdp425_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", IXDP425_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-ixp4xx/nas100d-setup.c b/arch/arm/mach-ixp4xx/nas100d-setup.c
index 76dfff03cb71..4138d6aa4c52 100644
--- a/arch/arm/mach-ixp4xx/nas100d-setup.c
+++ b/arch/arm/mach-ixp4xx/nas100d-setup.c
@@ -102,7 +102,7 @@ static struct platform_device nas100d_leds = {
};
static struct gpiod_lookup_table nas100d_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", NAS100D_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-ixp4xx/nslu2-setup.c b/arch/arm/mach-ixp4xx/nslu2-setup.c
index 91da63a7d7b5..341b263482ef 100644
--- a/arch/arm/mach-ixp4xx/nslu2-setup.c
+++ b/arch/arm/mach-ixp4xx/nslu2-setup.c
@@ -70,7 +70,7 @@ static struct platform_device nslu2_flash = {
};
static struct gpiod_lookup_table nslu2_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("IXP4XX_GPIO_CHIP", NSLU2_SDA_PIN,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-pxa/palmz72.c b/arch/arm/mach-pxa/palmz72.c
index 5877e547cecd..0adb1bd6208e 100644
--- a/arch/arm/mach-pxa/palmz72.c
+++ b/arch/arm/mach-pxa/palmz72.c
@@ -322,7 +322,7 @@ static struct soc_camera_link palmz72_iclink = {
};
static struct gpiod_lookup_table palmz72_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("gpio-pxa", 118, NULL, 0,
GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-pxa/viper.c b/arch/arm/mach-pxa/viper.c
index 90d0f277de55..207dcc2e94e7 100644
--- a/arch/arm/mach-pxa/viper.c
+++ b/arch/arm/mach-pxa/viper.c
@@ -460,7 +460,7 @@ static struct platform_device smc91x_device = {
/* i2c */
static struct gpiod_lookup_table viper_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.1",
.table = {
GPIO_LOOKUP_IDX("gpio-pxa", VIPER_RTC_I2C_SDA_GPIO,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
@@ -789,7 +789,7 @@ static int __init viper_tpm_setup(char *str)
__setup("tpm=", viper_tpm_setup);
struct gpiod_lookup_table viper_tpm_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.2",
.table = {
GPIO_LOOKUP_IDX("gpio-pxa", VIPER_TPM_I2C_SDA_GPIO,
NULL, 0, GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
diff --git a/arch/arm/mach-sa1100/simpad.c b/arch/arm/mach-sa1100/simpad.c
index ace010479eb6..f45aed2519ba 100644
--- a/arch/arm/mach-sa1100/simpad.c
+++ b/arch/arm/mach-sa1100/simpad.c
@@ -327,7 +327,7 @@ static struct platform_device simpad_gpio_leds = {
* i2c
*/
static struct gpiod_lookup_table simpad_i2c_gpiod_table = {
- .dev_id = "i2c-gpio",
+ .dev_id = "i2c-gpio.0",
.table = {
GPIO_LOOKUP_IDX("gpio", 21, NULL, 0,
GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN),
--
2.17.0
^ permalink raw reply related
* i2c-gpio and boards conversions to GPIO descriptors
From: Linus Walleij @ 2018-05-26 16:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180525154144.GC19100@kw.sim.vm.gnt>
On Fri, May 25, 2018 at 5:41 PM, Simon Guinot <simon.guinot@sequanux.org> wrote:
> Hi Linus,
>
> I think your patch b2e63555592f "i2c: gpio: Convert to use descriptors"
> may have broken i2c-gpio support for some boards using old fashion
> platform_device declarations.
>
> Indeed when an "i2c-gpio" platform_device is registered with a fixed id
> e.g. 0, then I think the device name becomes "i2c-gpio.0". And then this
> won't match a lookup table registered with an "i2c-gpio" dev_id.
Yeah what a mess, I'm sending patches to fix it up, the ARM
patch already sent, I will send a separate one for the MIPS
machines.
Sorry for the mess! :(
Yours,
Linus Walleij
^ permalink raw reply
* [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma
From: Peter Rosin @ 2018-05-26 17:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <a25ca617-d3da-d401-1ba9-8e5887f8a8e5@microchip.com>
On 2018-05-25 16:51, Tudor Ambarus wrote:
> Hi, Peter,
>
> On 04/11/2018 06:34 PM, Nicolas Ferre wrote:
>> I'll try to move forward with your detailed explanation and with my
>> contacts within the "product" team internally.
>
> We have talked with the hardware team, looks like there is an error in
> the description of the Master to Slave Access matrix. CPU accesses DDR2
> port0 through AXI matrix and not AHB. There is no conflict between CPU
> and LCDC DMA when accessing DDR2 ports. This explains why using CPU
> helps.
>
> The slave numbers from "Table 14-3 Master to Slave Access" are wrong.
> The 7th row should be removed and all the other rows from below it,
> shifted up with one level (DDR2 Port 1 is Slave no 7, DDR2 port 2 is
> Slave no 8, ... , APB1 is slave no 11).
Yes, the fact that row 7 (the 8th row, since there is a row 0, but I get
what you mean) should be removed was pretty much what I had guessed. But
what about the other strange things I found? To reiterate, this is my
PRxSy register content (zeroes shown as -):
PRxS0 33--3--3--3333--
PRxS1 33--3--3--3333--
PRxS2 33--------------
PRxS3 -3--------333---
PRxS4 33--------------
PRxS5 3---------------
PRxS6 33--33-33333333-
PRxS7 --3-3--3--------
PRxS8 -3---3--3--3----
PRxS9 --3-3--3-33-333-
PRxS10 3--3------------
PRxS11 3-----3---------
PRxS12 ----------------
PRxS13 ----------------
PRxS14 ----------------
PRxS15 ----------------
So, PRxS7 matches row 8 (DDR2 port 1) in the datasheet.
And PRxS8 matches row 9 (DDR2 port 2) in the datasheet.
But PRxS9 is not matching row 10 (DDR2 port 3)!
And PRxS10-11 match rows 11-12 (APB 0-1) in the datasheet.
But also look at PRxS3 (Internal ROM), there's a missing 3 in the
first slot (A5)! Maybe the priority of that one can't be changed
for some fundamental reason? But there is no hint to that effect
in the datasheet AFAICT...
> We think the best way is to keep LCD on DDR Ports 2 and 3 (8th and 9th
> slaves), to have maximum bandwidth and to use DMA on DDR port 1 for NAND
> (7th slave).
I think I tried to arrange for that last time around. Not sure though,
so I will try again next week...
> Also, some information about your configuration is useful. Can you
> please tell us what NAND DMA configuration did you use? Are you using
> NAND storage for the videos that you are playing on the LCD screen?
Not sure what level of detail you are after?
We use W949D2CBJX5E LPDDR1 memories from Winbond. Years ago, I wrote some
LPDDR1 patches for at91bootstrap to driver/ddramc.c (which predate the
current upstream support) and to board/sama5d3xek/sama5d3xek.c (which doesn't
to this day support LPDDR1 upstream, but I guess it shouldn't and that we
should have a board of our own, so that part isn't really clean and also the
reason I never upstreamed it). Anyway, some other trivial glue was also
needed, but the meat are in those files. I just had a brief look at the
LPDDR1 support in the upstream ddramc.c file and our code is very similar.
But I did notice some differences and I will look into if that difference
is something that matters. I can show provide patches if you think they
are relevant?
We use this in the sam-ba .qml file when we flash the devices with sam-ba and
the nandflash applet (don't know if it's relevant, but it shows that we have
a 16-bit bus):
device: SAMA5D3 {
name: "sama5d3-linea"
aliases: []
description: "SAMA5D3 Linea"
config {
nandflash {
ioset: 1
busWidth: 16
header: 0xc0902405
}
}
}
*time passes*
Oh dear ... you said NAND *DMA* configuration. Nothing special that I know
of. So, the default? Anything specific I should check?
Further, we are not playing any video. The artifacts are visible on a
static screen on an otherwise "idle" system (i.e. just showing whatever
on the screen and accessing the DRAM with DMA is enough to trigger the
visual glitches).
Cheers,
Peter
^ permalink raw reply
* [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs
From: Wei Xu @ 2018-05-26 18:00 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <0754957a2c3842cf4e36fa27231d327fd8d6d499.1527225682.git.viresh.kumar@linaro.org>
Hi Viresh,
On 2018/5/25 6:40, Viresh Kumar wrote:
> The cooling device properties, like "#cooling-cells" and
> "dynamic-power-coefficient", should either be present for all the CPUs
> of a cluster or none. If these are present only for a subset of CPUs of
> a cluster then things will start falling apart as soon as the CPUs are
> brought online in a different order. For example, this will happen
> because the operating system looks for such properties in the CPU node
> it is trying to bring up, so that it can register a cooling device.
>
> Add such missing properties.
>
> Do minor rearrangement as well to keep ordering consistent.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks!
Applied to the hisilicon fix tree.
Best Regards,
Wei
> ---
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> index 586b281cd531..247024df714f 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> @@ -88,8 +88,8 @@
> next-level-cache = <&CLUSTER0_L2>;
> clocks = <&stub_clock 0>;
> operating-points-v2 = <&cpu_opp_table>;
> - #cooling-cells = <2>; /* min followed by max */
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> dynamic-power-coefficient = <311>;
> };
>
> @@ -101,6 +101,8 @@
> next-level-cache = <&CLUSTER0_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu2: cpu at 2 {
> @@ -111,6 +113,8 @@
> next-level-cache = <&CLUSTER0_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu3: cpu at 3 {
> @@ -121,6 +125,8 @@
> next-level-cache = <&CLUSTER0_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu4: cpu at 100 {
> @@ -131,6 +137,8 @@
> next-level-cache = <&CLUSTER1_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu5: cpu at 101 {
> @@ -141,6 +149,8 @@
> next-level-cache = <&CLUSTER1_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu6: cpu at 102 {
> @@ -151,6 +161,8 @@
> next-level-cache = <&CLUSTER1_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> cpu7: cpu at 103 {
> @@ -161,6 +173,8 @@
> next-level-cache = <&CLUSTER1_L2>;
> operating-points-v2 = <&cpu_opp_table>;
> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
> + #cooling-cells = <2>; /* min followed by max */
> + dynamic-power-coefficient = <311>;
> };
>
> CLUSTER0_L2: l2-cache0 {
>
^ permalink raw reply
* [GIT PULL] arm64: hisilicon fixes for 4.17
From: Wei Xu @ 2018-05-26 18:08 UTC (permalink / raw)
To: linux-arm-kernel
Hi Olof, Hi Arnd,
Please help to pull the following fixes.
Sorry for the late fix pull since we got the patches at last week.
And if it is too late, I will rebase them after 4.18-rc1 released.
Thanks!
Best Regards,
Wei
---
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-4.17
for you to fetch changes up to 7734370471922ad8b1d9077c876bb0774059f807:
arm64: dts: hisilicon: Add missing cooling device properties for CPUs (2018-05-26 18:15:27 +0100)
----------------------------------------------------------------
ARM64: hisi fixes for 4.17
- Remove eMMC max-frequency property to fix eMMC corruption on hikey board
- Add missing cooling related properties to avoid falling apart when the
CPUs are brought oneline in a different order on hi6220 SoC
----------------------------------------------------------------
John Stultz (1):
arm64: dts: hikey: Fix eMMC corruption regression
Viresh Kumar (1):
arm64: dts: hisilicon: Add missing cooling device properties for CPUs
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 -
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 16 +++++++++++++++-
2 files changed, 15 insertions(+), 2 deletions(-)
^ permalink raw reply
* [GIT PULL] Allwinner core changes for 4.18
From: Olof Johansson @ 2018-05-26 18:21 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAGb2v64Febv7ZLZbcTqR6+say38xu25gj0n+dbY-8KAyygDpJw@mail.gmail.com>
On Sat, May 26, 2018 at 6:22 PM, Chen-Yu Tsai <wens@csie.org> wrote:
> On Fri, May 25, 2018 at 2:02 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Mon, May 21, 2018 at 01:41:56PM +0200, Maxime Ripard wrote:
>>> Hi,
>>>
>>> Here is our mach-sunxi changes for the next merge window, thanks!
>>> Maxime
>>>
>>> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>>>
>>> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>>>
>>> are available in the Git repository at:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-core-for-4.18
>>>
>>> for you to fetch changes up to 6961275e72a8c15cc4ebf108a81eee758480a6a2:
>>>
>>> ARM: sun8i: smp: Add support for A83T (2018-05-08 15:00:20 +0200)
>>>
>>> ----------------------------------------------------------------
>>> Allwinner core changes for 4.18
>>>
>>> The A83t, unlike the other Allwinner SoCs, cannot use PSCI because of a
>>> silicon bug. As such, we needed to have some smp_ops in order to bringup
>>> the various cores (and clusters) found on this SoC.
>>
>> Hrm. that's unfortunate. Is there any public documentation of what the bug is?
>
> The security extensions in the A80 and A83T is not entirely enabled.
> The security bit is not forwarded on to the bus, so all accesses from
> non-secure become secure. This is not documented, but was the result
> of some tests I did.
>
> See https://lists.denx.de/pipermail/u-boot/2017-June/294672.html
> for a summary (in the quotes) of what we think is the issue.
>
> Marc's suggestion is that if virtualization doesn't work on it, then
> there's no point in running it non-secure. [1]
So it sounds like you can still use PSCI even if there's nothing that
stops the kernel from also doing the same operations. It doesn't buy
you any security benefits, but you can use the same standard
interfaces as everybody else does. I think there's still value in
that. Or am I missing some aspect of the errata implications?
-Olof
^ permalink raw reply
* [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs
From: Wei Xu @ 2018-05-26 18:21 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <5B09A0B4.2080400@hisilicon.com>
Hi Viresh,
On 2018/5/26 19:00, Wei Xu wrote:
> Hi Viresh,
>
> On 2018/5/25 6:40, Viresh Kumar wrote:
>> The cooling device properties, like "#cooling-cells" and
>> "dynamic-power-coefficient", should either be present for all the CPUs
>> of a cluster or none. If these are present only for a subset of CPUs of
>> a cluster then things will start falling apart as soon as the CPUs are
>> brought online in a different order. For example, this will happen
>> because the operating system looks for such properties in the CPU node
>> it is trying to bring up, so that it can register a cooling device.
>>
>> Add such missing properties.
>>
>> Do minor rearrangement as well to keep ordering consistent.
>>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Thanks!
> Applied to the hisilicon fix tree.
Sorry for the noise!
It seems this patch is still under discussion.
I will drop it firstly.
Best Regards,
Wei
>
> Best Regards,
> Wei
>
>> ---
>> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 16 +++++++++++++++-
>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> index 586b281cd531..247024df714f 100644
>> --- a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> +++ b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
>> @@ -88,8 +88,8 @@
>> next-level-cache = <&CLUSTER0_L2>;
>> clocks = <&stub_clock 0>;
>> operating-points-v2 = <&cpu_opp_table>;
>> - #cooling-cells = <2>; /* min followed by max */
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> dynamic-power-coefficient = <311>;
>> };
>>
>> @@ -101,6 +101,8 @@
>> next-level-cache = <&CLUSTER0_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu2: cpu at 2 {
>> @@ -111,6 +113,8 @@
>> next-level-cache = <&CLUSTER0_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu3: cpu at 3 {
>> @@ -121,6 +125,8 @@
>> next-level-cache = <&CLUSTER0_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu4: cpu at 100 {
>> @@ -131,6 +137,8 @@
>> next-level-cache = <&CLUSTER1_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu5: cpu at 101 {
>> @@ -141,6 +149,8 @@
>> next-level-cache = <&CLUSTER1_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu6: cpu at 102 {
>> @@ -151,6 +161,8 @@
>> next-level-cache = <&CLUSTER1_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> cpu7: cpu at 103 {
>> @@ -161,6 +173,8 @@
>> next-level-cache = <&CLUSTER1_L2>;
>> operating-points-v2 = <&cpu_opp_table>;
>> cpu-idle-states = <&CPU_SLEEP &CLUSTER_SLEEP>;
>> + #cooling-cells = <2>; /* min followed by max */
>> + dynamic-power-coefficient = <311>;
>> };
>>
>> CLUSTER0_L2: l2-cache0 {
>>
^ permalink raw reply
* [GIT PULL] arm64: hisilicon fixes for 4.17
From: Wei Xu @ 2018-05-26 18:23 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <5B09A2AB.2040002@hisilicon.com>
Hi Olof, Hi Arnd,
Please ignore this pull because of the cooling patch.
I will send another one without that.
Sorry for the noise!
Best Regards,
Wei
On 2018/5/26 19:08, Wei Xu wrote:
> Hi Olof, Hi Arnd,
>
> Please help to pull the following fixes.
> Sorry for the late fix pull since we got the patches at last week.
> And if it is too late, I will rebase them after 4.18-rc1 released.
> Thanks!
>
> Best Regards,
> Wei
>
> ---
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-4.17
>
> for you to fetch changes up to 7734370471922ad8b1d9077c876bb0774059f807:
>
> arm64: dts: hisilicon: Add missing cooling device properties for CPUs (2018-05-26 18:15:27 +0100)
>
> ----------------------------------------------------------------
> ARM64: hisi fixes for 4.17
>
> - Remove eMMC max-frequency property to fix eMMC corruption on hikey board
> - Add missing cooling related properties to avoid falling apart when the
> CPUs are brought oneline in a different order on hi6220 SoC
>
> ----------------------------------------------------------------
> John Stultz (1):
> arm64: dts: hikey: Fix eMMC corruption regression
>
> Viresh Kumar (1):
> arm64: dts: hisilicon: Add missing cooling device properties for CPUs
>
> arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 -
> arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 16 +++++++++++++++-
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
>
^ permalink raw reply
* ARM: dts: imx6: enable OTG on wandboard and riotboard
From: Alexander Kurz @ 2018-05-26 18:30 UTC (permalink / raw)
To: linux-arm-kernel
Both boards wandboard and riotboard feature an USB OTG connector.
Change the DT regulator nodes to match the convention, fix the
GPIO regulator polatity for the riotboard and add enable OTG
including the regulator infrastructure on the riotboard.
^ permalink raw reply
* [PATCH 1/3] ARM: dts: imx6 wandboard and riotboard: remove regulators bus node
From: Alexander Kurz @ 2018-05-26 18:30 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180526183053.14029-1-akurz@blala.de>
To match the convention, move regulator-fixed nodes directly into
the root node.
Signed-off-by: Alexander Kurz <akurz@blala.de>
---
arch/arm/boot/dts/imx6dl-riotboard.dts | 55 +++++++++++++-------------------
arch/arm/boot/dts/imx6qdl-wandboard.dtsi | 40 ++++++++++-------------
2 files changed, 39 insertions(+), 56 deletions(-)
diff --git a/arch/arm/boot/dts/imx6dl-riotboard.dts b/arch/arm/boot/dts/imx6dl-riotboard.dts
index 2e98c92adff7..a52e05934e3a 100644
--- a/arch/arm/boot/dts/imx6dl-riotboard.dts
+++ b/arch/arm/boot/dts/imx6dl-riotboard.dts
@@ -19,38 +19,6 @@
reg = <0x10000000 0x40000000>;
};
- regulators {
- compatible = "simple-bus";
- #address-cells = <1>;
- #size-cells = <0>;
-
- reg_2p5v: regulator at 0 {
- compatible = "regulator-fixed";
- reg = <0>;
- regulator-name = "2P5V";
- regulator-min-microvolt = <2500000>;
- regulator-max-microvolt = <2500000>;
- };
-
- reg_3p3v: regulator at 1 {
- compatible = "regulator-fixed";
- reg = <1>;
- regulator-name = "3P3V";
- regulator-min-microvolt = <3300000>;
- regulator-max-microvolt = <3300000>;
- };
-
- reg_usb_otg_vbus: regulator at 2 {
- compatible = "regulator-fixed";
- reg = <2>;
- regulator-name = "usb_otg_vbus";
- regulator-min-microvolt = <5000000>;
- regulator-max-microvolt = <5000000>;
- gpio = <&gpio3 22 0>;
- enable-active-high;
- };
- };
-
leds {
compatible = "gpio-leds";
pinctrl-names = "default";
@@ -82,6 +50,29 @@
mux-int-port = <1>;
mux-ext-port = <3>;
};
+
+ reg_2p5v: fixedregulator at 0 {
+ compatible = "regulator-fixed";
+ regulator-name = "2P5V";
+ regulator-min-microvolt = <2500000>;
+ regulator-max-microvolt = <2500000>;
+ };
+
+ reg_3p3v: fixedregulator at 1 {
+ compatible = "regulator-fixed";
+ regulator-name = "3P3V";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ };
+
+ reg_usb_otg_vbus: fixedregulator at 2 {
+ compatible = "regulator-fixed";
+ regulator-name = "usb_otg_vbus";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ gpio = <&gpio3 22 0>;
+ enable-active-high;
+ };
};
&audmux {
diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
index ed96d7b5feab..ff7e824dfd28 100644
--- a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
@@ -12,30 +12,6 @@
#include <dt-bindings/gpio/gpio.h>
/ {
- regulators {
- compatible = "simple-bus";
- #address-cells = <1>;
- #size-cells = <0>;
-
- reg_2p5v: regulator at 0 {
- compatible = "regulator-fixed";
- reg = <0>;
- regulator-name = "2P5V";
- regulator-min-microvolt = <2500000>;
- regulator-max-microvolt = <2500000>;
- regulator-always-on;
- };
-
- reg_3p3v: regulator at 1 {
- compatible = "regulator-fixed";
- reg = <1>;
- regulator-name = "3P3V";
- regulator-min-microvolt = <3300000>;
- regulator-max-microvolt = <3300000>;
- regulator-always-on;
- };
- };
-
sound {
compatible = "fsl,imx6-wandboard-sgtl5000",
"fsl,imx-audio-sgtl5000";
@@ -56,6 +32,22 @@
spdif-controller = <&spdif>;
spdif-out;
};
+
+ reg_2p5v: fixedregulator at 0 {
+ compatible = "regulator-fixed";
+ regulator-name = "2P5V";
+ regulator-min-microvolt = <2500000>;
+ regulator-max-microvolt = <2500000>;
+ regulator-always-on;
+ };
+
+ reg_3p3v: fixedregulator at 1 {
+ compatible = "regulator-fixed";
+ regulator-name = "3P3V";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ regulator-always-on;
+ };
};
&audmux {
--
2.11.0
^ permalink raw reply related
* [PATCH 2/3] ARM: dts: imx6qdl-wandboard: enable USB OTG
From: Alexander Kurz @ 2018-05-26 18:30 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180526183053.14029-1-akurz@blala.de>
Enable USB OTG (dual-role) on the Wandboard.
Note, that the USB_OTG_VBUS current is quite limited due to a 22R resistor
in the power line. Hence, the overcurrent signal of 1A will never be
triggered on this board.
Signed-off-by: Alexander Kurz <akurz@blala.de>
---
arch/arm/boot/dts/imx6qdl-wandboard.dtsi | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
index ff7e824dfd28..4ac8ee355c42 100644
--- a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-wandboard.dtsi
@@ -48,6 +48,16 @@
regulator-max-microvolt = <3300000>;
regulator-always-on;
};
+
+ reg_usb_otg_vbus: fixedregulator at 2 {
+ compatible = "regulator-fixed";
+ regulator-name = "usb_otg_vbus";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_usbotgvbus>;
+ gpio = <&gpio3 22 GPIO_ACTIVE_LOW>;
+ };
};
&audmux {
@@ -162,6 +172,12 @@
>;
};
+ pinctrl_usbotgvbus: usbotgvbusgrp {
+ fsl,pins = <
+ MX6QDL_PAD_EIM_D22__GPIO3_IO22 0x130b0
+ >;
+ };
+
pinctrl_usdhc1: usdhc1grp {
fsl,pins = <
MX6QDL_PAD_SD1_CMD__SD1_CMD 0x17059
@@ -236,10 +252,11 @@
};
&usbotg {
+ vbus-supply = <®_usb_otg_vbus>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usbotg>;
disable-over-current;
- dr_mode = "peripheral";
+ dr_mode = "otg";
status = "okay";
};
--
2.11.0
^ permalink raw reply related
* [PATCH 3/3] ARM: dts: imx6dl-riotboard: fix OTG regulator polarity
From: Alexander Kurz @ 2018-05-26 18:30 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180526183053.14029-1-akurz@blala.de>
USB OTG power is switched on when the GPIO is pulled low.
Signed-off-by: Alexander Kurz <akurz@blala.de>
---
arch/arm/boot/dts/imx6dl-riotboard.dts | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/imx6dl-riotboard.dts b/arch/arm/boot/dts/imx6dl-riotboard.dts
index a52e05934e3a..ef3b270c15e5 100644
--- a/arch/arm/boot/dts/imx6dl-riotboard.dts
+++ b/arch/arm/boot/dts/imx6dl-riotboard.dts
@@ -70,8 +70,7 @@
regulator-name = "usb_otg_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
- gpio = <&gpio3 22 0>;
- enable-active-high;
+ gpio = <&gpio3 22 GPIO_ACTIVE_LOW>;
};
};
--
2.11.0
^ permalink raw reply related
* [GIT PULL v2] arm64: hisilicon fixes for 4.17
From: Wei Xu @ 2018-05-26 18:37 UTC (permalink / raw)
To: linux-arm-kernel
Hi Olof, Hi Arnd,
Please help to pull the following fix.
Sorry for the late fix pull since we just got the patch.
And if the pull is too late, I will rebase the patch after 4.18-rc1 released.
Thanks!
Best Regards,
Wei
---
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-4.17v2
for you to fetch changes up to 9c6d26df1fae6ad4718d51c48e6517913304ed27:
arm64: dts: hikey: Fix eMMC corruption regression (2018-05-26 17:51:47 +0100)
----------------------------------------------------------------
ARM64: hisi fixes for 4.17
- Remove eMMC max-frequency property to fix eMMC corruption on hikey board
----------------------------------------------------------------
John Stultz (1):
arm64: dts: hikey: Fix eMMC corruption regression
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 -
1 file changed, 1 deletion(-)
^ permalink raw reply
* [PATCH] ARM: Fix i2c-gpio GPIO descriptor tables
From: Olof Johansson @ 2018-05-26 18:44 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180526163734.30098-1-linus.walleij@linaro.org>
On Sat, May 26, 2018 at 06:37:34PM +0200, Linus Walleij wrote:
> I used bad names in my clumsiness when rewriting many board
> files to use GPIO descriptors instead of platform data. A few
> had the platform_device ID set to -1 which would indeed give
> the device name "i2c-gpio".
>
> But several had it set to >=0 which gives the names
> "i2c-gpio.0", "i2c-gpio.1" ...
>
> Fix the offending instances in the ARM tree. Sorry for the
> mess.
>
> Fixes: b2e63555592f ("i2c: gpio: Convert to use descriptors")
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Simon Guinot <simon.guinot@sequanux.org>
> Reported-by: Simon Guinot <simon.guinot@sequanux.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ARM SoC folks: please apply this directly for fixes if
> it check out fine.
> (The fact that it took so long to discover tells us something
> about how used these board files are.)
Applied to fixes, I've got one last batch going in today so I'll include it
there.
-Olof
^ permalink raw reply
* [GIT PULL] ARM: at91: DT for 4.18
From: Olof Johansson @ 2018-05-26 18:45 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180525225033.GA26989@piout.net>
On Sat, May 26, 2018 at 12:50:33AM +0200, Alexandre Belloni wrote:
> Arnd, Olof,
>
> I'm a bit late for this very small PR, as I had to extend the expiration
> date for my GPG signature key.
>
> Two small DT changes that have no functional impact.
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/at91-ab-4.18-dt
>
> for you to fetch changes up to a642693882ce417683012a211ca9d6e65bae1dc4:
>
> ARM: dts: at91-sama5d2_xplained: Use IRQ_TYPE specifier (2018-05-14 15:29:52 +0200)
>
> ----------------------------------------------------------------
> AT91 DT for 4.18:
>
> - small DT improvements without functional changes
>
> ----------------------------------------------------------------
> Dmitry Torokhov (1):
> ARM: dts: at91: sama5d4ek: use canonical compatible for touchscreen
>
> Hern?n Gonzalez (1):
> ARM: dts: at91-sama5d2_xplained: Use IRQ_TYPE specifier
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Qualcomm Driver updates for 4.18 - RESEND
From: Olof Johansson @ 2018-05-26 18:52 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1527287624-26491-1-git-send-email-andy.gross@linaro.org>
On Fri, May 25, 2018 at 05:33:44PM -0500, Andy Gross wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-drivers-for-4.18
>
> for you to fetch changes up to 6d361c1db7b69fddf5748cf212169ab57bb13a6e:
>
> soc: qcom: smem: introduce qcom_smem_virt_to_phys() (2018-05-25 15:53:59 -0500)
Merged into next/late; if there's an -rc7 it'll go in with the regular pull
requests.
-Olof
^ permalink raw reply
* [GIT PULL] Qualcomm ARM64 Defconfig updates for 4.18
From: Olof Johansson @ 2018-05-26 18:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1527287693-26646-1-git-send-email-andy.gross@linaro.org>
On Fri, May 25, 2018 at 05:34:53PM -0500, Andy Gross wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-arm64-defconfig-for-4.18
>
> for you to fetch changes up to b741377f1ff72a17e3b06e4b506b13f5c6158b1c:
>
> arm64: defconfig: Enable PCIe on msm8996 and db820c (2018-05-25 15:49:12 -0500)
>
> ----------------------------------------------------------------
> Qualcomm ARM64 Based defconfig Updates for v4.18
>
> * Enable UFS and PCIe for Qualcomm msm8996/db820c
Thanks, merged into next/defconfig
-Olof
^ permalink raw reply
* [GIT PULL] Qualcomm ARM64 DT updates for 4.18 - Part 2
From: Olof Johansson @ 2018-05-26 18:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1527288065-27438-1-git-send-email-andy.gross@linaro.org>
On Fri, May 25, 2018 at 05:41:05PM -0500, Andy Gross wrote:
> The following changes since commit 57fc67ef0d35af11fbb1b928e359b370889994ae:
>
> arm64: dts: qcom: msm8996: Add ufs related nodes (2018-05-22 23:29:03 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-arm64-for-4.18-2
>
> for you to fetch changes up to d8f8d467f53a192041193fc17176ceb013f4d041:
>
> arm64: dts: apq8096-db820c: Removed bt-en-1-8v regulator (2018-05-25 16:21:05 -0500)
>
> ----------------------------------------------------------------
> Qualcomm ARM64 Updates for v4.18 Part 2
>
> * Fix UFS GDSC on msm8996
> * Remove unused BT node regulator
> * Correct WLAN PCIe regulator endpoint name
Thanks, merged into next/dt.
-Olof
^ permalink raw reply
* [GIT PULL] Qualcomm Device Tree updates for 4.18 - Part 2
From: Olof Johansson @ 2018-05-26 18:59 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1527288081-27486-1-git-send-email-andy.gross@linaro.org>
On Fri, May 25, 2018 at 05:41:21PM -0500, Andy Gross wrote:
> The following changes since commit 90ce62659994b87723ec6ba26815f9634c18e449:
>
> ARM: dts: qcom-apq8064: use correct pci address for address translation (2018-05-14 15:22:28 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-dts-for-4.18-2
>
> for you to fetch changes up to 0e4c982096f873f893d0e7b59f5abb3ef234e667:
>
> ARM: dts: ipq8074: Enable few peripherals for hk01 board (2018-05-25 15:40:21 -0500)
>
> ----------------------------------------------------------------
> Qualcomm Device Tree Changes for v4.18 - Part 2
>
> * Numerous updates for IPQ8074 and IPQ4019 based devices
> * Add support for Sony Xperia Z1 Compact
Thanks, merged into next/dt.
-Olof
^ permalink raw reply
* [GIT PULL v2] arm64: hisilicon fixes for 4.17
From: Olof Johansson @ 2018-05-26 19:10 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <5B09A971.6030506@hisilicon.com>
On Sat, May 26, 2018 at 07:37:37PM +0100, Wei Xu wrote:
> Hi Olof, Hi Arnd,
>
> Please help to pull the following fix.
> Sorry for the late fix pull since we just got the patch.
> And if the pull is too late, I will rebase the patch after 4.18-rc1 released.
> Thanks!
>
> Best Regards,
> Wei
>
> ---
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-4.17v2
>
> for you to fetch changes up to 9c6d26df1fae6ad4718d51c48e6517913304ed27:
>
> arm64: dts: hikey: Fix eMMC corruption regression (2018-05-26 17:51:47 +0100)
>
> ----------------------------------------------------------------
> ARM64: hisi fixes for 4.17
>
> - Remove eMMC max-frequency property to fix eMMC corruption on hikey board
>
> ----------------------------------------------------------------
> John Stultz (1):
> arm64: dts: hikey: Fix eMMC corruption regression
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v4.18
From: Olof Johansson @ 2018-05-26 19:37 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1526548577.git.horms+renesas@verge.net.au>
On Fri, May 18, 2018 at 01:16:25PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC defconfig updates for v4.18.
>
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-defconfig-for-v4.18
>
> for you to fetch changes up to eedd7902366b17f95f4fe687c54dcfa186a53158:
>
> ARM: multi_v7_defconfig: Enable RENESAS_WDT (2018-05-16 11:08:35 +0200)
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC DT Bindings Updates for v4.18
From: Olof Johansson @ 2018-05-26 19:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1526549153.git.horms+renesas@verge.net.au>
On Fri, May 18, 2018 at 01:16:44PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC DT bindings updates for v4.18.
>
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-bindings-for-v4.18
>
> for you to fetch changes up to c92db4a4a4c6c176c34604e456d6d355803d9ada:
>
> dt-bindings: arm: document Renesas V3HSK board bindings (2018-05-15 09:17:45 +0200)
>
> ----------------------------------------------------------------
> Renesas ARM Based SoC DT Bindings Updates for v4.18
>
> Document bindings for:
>
> * V3H Starter Kit, a board used with the R-Car V3H (r8a77980) SoC
> * R-Car E3 (R8A77990) SoC and its Ebisu board
> * iWave Systems RZ/G1C Single Board Computer (iW-RainboW-G23S)
> which uses an RZ/G1C (R8A77470) SoC
> * RZ/G1M (R8A7743) and RZ/G1N (R8A7744) CMT support
>
> Cleanup:
> * Consistently name r8a77965 as R-Car M3-N
>
> ----------------------------------------------------------------
> Biju Das (1):
> dt-bindings: arm: Document iW-RainboW-G23S single board computer
>
> Fabrizio Castro (1):
> dt-bindings: timer: renesas, cmt: Document r8a774[35] CMT support
>
> Sergei Shtylyov (1):
> dt-bindings: arm: document Renesas V3HSK board bindings
>
> Simon Horman (1):
> dt-bindings: arm: consistently name r8a77965 as M3-N
>
> Yoshihiro Shimoda (2):
> dt-bindings: arm: Document R-Car E3 SoC DT bindings
> dt-bindings: arm: Document Renesas Ebisu board DT bindings
>
> Documentation/devicetree/bindings/arm/shmobile.txt | 10 +++++++++-
> Documentation/devicetree/bindings/timer/renesas,cmt.txt | 14 ++++++++++----
> 2 files changed, 19 insertions(+), 5 deletions(-)
Merged, thanks.
-Olof
^ permalink raw reply
* [GIT PULL] ARM: SoC fixes
From: Olof Johansson @ 2018-05-26 21:01 UTC (permalink / raw)
To: linux-arm-kernel
Hi Linus,
Please merge. Thanks!
-Olof
The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11:
Linux 4.17-rc6 (2018-05-20 15:31:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes
for you to fetch changes up to e5dd61546a777d19d4fe35e2d0a2b664ca49f6b2:
Merge tag 'hisi-fixes-for-4.17v2' of git://github.com/hisilicon/linux-hisi into fixes (2018-05-26 12:12:44 -0700)
----------------------------------------------------------------
ARM: SoC fixes for 4.17-rc
A few more fixes for v4.17:
- A fix for a crash in scm_call_atomic on qcom platforms
- Display fix for Allwinner A10
- A fix that re-enables ethernet on Allwinner H3 (C.H.I.P et al)
- A fix for eMMC corruption on hikey
- i2c-gpio descriptor tables for ixp4xx
+ a small typo fix
----------------------------------------------------------------
Chen-Yu Tsai (1):
ARM: dts: sun8i: h3: Re-enable EMAC on Orange Pi One
Colin Ian King (1):
ARM: sun8i: v3s: fix spelling mistake: "disbaled" -> "disabled"
John Stultz (1):
arm64: dts: hikey: Fix eMMC corruption regression
Linus Walleij (1):
ARM: Fix i2c-gpio GPIO descriptor tables
Niklas Cassel (1):
firmware: qcom: scm: Fix crash in qcom_scm_call_atomic1()
Olof Johansson (3):
Merge tag 'sunxi-fixes-for-4.17' of https://git.kernel.org/.../sunxi/linux into fixes
Merge tag 'qcom-fixes-for-4.17-rc7' of git://git.kernel.org/.../agross/linux into fixes
Merge tag 'hisi-fixes-for-4.17v2' of git://github.com/hisilicon/linux-hisi into fixes
Pascal Roeleven (1):
ARM: dts: sun4i: Fix incorrect clocks for displays
arch/arm/boot/dts/sun4i-a10.dtsi | 6 +++---
arch/arm/boot/dts/sun8i-h3-orangepi-one.dts | 1 +
arch/arm/boot/dts/sun8i-v3s-licheepi-zero-dock.dts | 2 +-
arch/arm/mach-ep93xx/core.c | 2 +-
arch/arm/mach-ixp4xx/avila-setup.c | 2 +-
arch/arm/mach-ixp4xx/dsmg600-setup.c | 2 +-
arch/arm/mach-ixp4xx/fsg-setup.c | 2 +-
arch/arm/mach-ixp4xx/ixdp425-setup.c | 2 +-
arch/arm/mach-ixp4xx/nas100d-setup.c | 2 +-
arch/arm/mach-ixp4xx/nslu2-setup.c | 2 +-
arch/arm/mach-pxa/palmz72.c | 2 +-
arch/arm/mach-pxa/viper.c | 4 ++--
arch/arm/mach-sa1100/simpad.c | 2 +-
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 -
drivers/firmware/qcom_scm-32.c | 8 ++++----
15 files changed, 20 insertions(+), 20 deletions(-)
^ permalink raw reply
* [GIT PULL] Renesas ARM64 Based SoC DT Updates for v4.18
From: Olof Johansson @ 2018-05-26 21:14 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1526637994.git.horms+renesas@verge.net.au>
Hi Simon,
On Fri, May 18, 2018 at 01:16:00PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM64 based SoC DT updates for v4.18.
>
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm64-dt-for-v4.18
>
> for you to fetch changes up to 908001d778eba06ee1d832863d4e9a1e2cfd4746:
>
> arm64: dts: renesas: salvator-common: Add ADV7482 support (2018-05-18 11:52:03 +0200)
This pull request is really, really hard for us to digest. The tag
description is very large, and it repeats several SoCs several times,
making it hard to get an overview of what is in it. The verbosity of "<x>
says.." makes it harder on this size of a pull request as well.
For example:
> * Condor board with R-Car V3H (r8a77980) SoC
> - Enable eMMC
>
> Sergei Shtylyov says "We're adding the R8A77980 MMC (SDHI)
> device nodes and then enable eMMC support on the Condor board."
The "Enable eMMC" line is just fine here.
> ----------------------------------------------------------------
> Geert Uytterhoeven (11):
> arm64: dts: renesas: draak: Rename EtherAVB "mdc" pin group to "mdio"
> arm64: dts: renesas: salvator-common: Rename EtherAVB "mdc" pin group to "mdio"
> arm64: dts: renesas: ulcb: Rename EtherAVB "mdc" pin group to "mdio"
Why can't these be done in one commit?
> arm64: dts: renesas: r8a7795: Correct whitespace
> arm64: dts: renesas: r8a7796: Correct whitespace
> arm64: dts: renesas: r8a77965: Correct whitespace
Do these really need to be three commits to fix some whitespace?
> arm64: dts: renesas: ulcb: Add BD9571 PMIC
> arm64: dts: renesas: salvator-common: Add PMIC DDR Backup Power config
> arm64: dts: renesas: ulcb: Add PMIC DDR Backup Power config
> arm64: dts: renesas: r8a77970: Add secondary CA53 CPU core
> arm64: dts: renesas: r8a77970: Add Cortex-A53 PMU node
Why can't these be done in the same commit?
> Kieran Bingham (7):
> arm64: dts: renesas: r8a77965: Add FCPF and FCPV instances
> arm64: dts: renesas: r8a77965: Add VSP instances
> arm64: dts: renesas: r8a77965: Populate the DU instance placeholder
> arm64: dts: renesas: r8a77965: Add HDMI encoder instance
> arm64: dts: renesas: r8a77965-salvator-x: Enable DU external clocks and HDMI
> arm64: dts: renesas: r8a77965-salvator-xs: Enable DU external clocks and HDMI
These two can probably be in one commit as well.
> arm64: dts: renesas: salvator-common: Add ADV7482 support
>
> Kuninori Morimoto (8):
> arm64: dts: renesas: r8a7795: add HDMI sound support
> arm64: dts: renesas: r8a7796: add HDMI sound support
... starting to see a trend?
> arm64: dts: renesas: salvator-common: use audio-graph-card for Sound
> arm64: dts: renesas: r8a7795-es1-salvator-x: enable HDMI sound
> arm64: dts: renesas: r8a7795-salvator-xs: enable HDMI sound
> arm64: dts: renesas: r8a7796-salvator-xs: enable HDMI sound
> arm64: dts: renesas: r8a7795-salvator-x: enable HDMI sound
> arm64: dts: renesas: r8a7796-salvator-x: enable HDMI sound
... and more.
>
> Magnus Damm (5):
> arm64: dts: renesas: r8a77970: Update IPMMU DS1 bit number
> arm64: dts: renesas: r8a7795: Enable IPMMU devices
> arm64: dts: renesas: r8a7796: Enable IPMMU devices
> arm64: dts: renesas: r8a77970: Enable IPMMU devices
> arm64: dts: renesas: r8a77995: Enable IPMMU devices
I think these 4 could be in one commit too.
>
> Niklas S?derlund (11):
> arm64: dts: renesas: r8a7795: decrease temperature hysteresis
> arm64: dts: renesas: r8a7796: decrease temperature hysteresis
> arm64: dts: renesas: r8a77965: use r8a77965-sysc binding definitions
> arm64: dts: renesas: r8a77965: Add R-Car Gen3 thermal support
> arm64: dts: renesas: r8a77965: add I2C support
> arm64: dts: renesas: r8a7795: add VIN and CSI-2 nodes
> arm64: dts: renesas: r8a7795-es1: add CSI-2 node
> arm64: dts: renesas: r8a7796: add VIN and CSI-2 nodes
> arm64: dts: renesas: r8a77965: add VIN and CSI-2 nodes
> arm64: dts: renesas: r8a77970: add VIN and CSI-2 nodes
.... etc, etc. I'll stop here.
I haven't merged this branch yet, will need to set aside more time to review
the contents. I can't guarantee that it'll make v4.18 but I'll try.
-Olof
^ permalink raw reply
* [GIT PULL] Renesas ARM Based SoC Updates for v4.18
From: Olof Johansson @ 2018-05-26 21:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <cover.1526639075.git.horms+renesas@verge.net.au>
On Fri, May 18, 2018 at 01:18:11PM +0200, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC updates for v4.18.
>
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc-for-v4.18
>
> for you to fetch changes up to 086b399965a7ee7e50c3b3c57f2dba30ff0334b0:
>
> soc: renesas: r8a77990-sysc: Add workaround for 3DG-{A,B} (2018-05-16 10:57:44 +0200)
Merged, thanks.
-Olof
^ permalink raw reply
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