<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/arch/arm, branch v5.1.18</title>
<subtitle>Clone of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git</subtitle>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/'/>
<entry>
<title>ARM: davinci: da8xx: specify dma_coherent_mask for lcdc</title>
<updated>2019-07-14T06:09:42+00:00</updated>
<author>
<name>Bartosz Golaszewski</name>
<email>bgolaszewski@baylibre.com</email>
</author>
<published>2019-06-07T14:33:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=658031eab6241a3c7ffc72066f65c19ad3f22b49'/>
<id>658031eab6241a3c7ffc72066f65c19ad3f22b49</id>
<content type='text'>
[ Upstream commit 68f2515bb31a664ba3e2bc1eb78dd9f529b10067 ]

The lcdc device is missing the dma_coherent_mask definition causing the
following warning on da850-evm:

da8xx_lcdc da8xx_lcdc.0: found Sharp_LK043T1DG01 panel
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at kernel/dma/mapping.c:247 dma_alloc_attrs+0xc8/0x110
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.0-rc3-00077-g16d72dd4891f #18
Hardware name: DaVinci DA850/OMAP-L138/AM18x EVM
[&lt;c000fce8&gt;] (unwind_backtrace) from [&lt;c000d900&gt;] (show_stack+0x10/0x14)
[&lt;c000d900&gt;] (show_stack) from [&lt;c001a4f8&gt;] (__warn+0xec/0x114)
[&lt;c001a4f8&gt;] (__warn) from [&lt;c001a634&gt;] (warn_slowpath_null+0x3c/0x48)
[&lt;c001a634&gt;] (warn_slowpath_null) from [&lt;c0065860&gt;] (dma_alloc_attrs+0xc8/0x110)
[&lt;c0065860&gt;] (dma_alloc_attrs) from [&lt;c02820f8&gt;] (fb_probe+0x228/0x5a8)
[&lt;c02820f8&gt;] (fb_probe) from [&lt;c02d3e9c&gt;] (platform_drv_probe+0x48/0x9c)
[&lt;c02d3e9c&gt;] (platform_drv_probe) from [&lt;c02d221c&gt;] (really_probe+0x1d8/0x2d4)
[&lt;c02d221c&gt;] (really_probe) from [&lt;c02d2474&gt;] (driver_probe_device+0x5c/0x168)
[&lt;c02d2474&gt;] (driver_probe_device) from [&lt;c02d2728&gt;] (device_driver_attach+0x58/0x60)
[&lt;c02d2728&gt;] (device_driver_attach) from [&lt;c02d27b0&gt;] (__driver_attach+0x80/0xbc)
[&lt;c02d27b0&gt;] (__driver_attach) from [&lt;c02d047c&gt;] (bus_for_each_dev+0x64/0xb4)
[&lt;c02d047c&gt;] (bus_for_each_dev) from [&lt;c02d1590&gt;] (bus_add_driver+0xe4/0x1d8)
[&lt;c02d1590&gt;] (bus_add_driver) from [&lt;c02d301c&gt;] (driver_register+0x78/0x10c)
[&lt;c02d301c&gt;] (driver_register) from [&lt;c000a5c0&gt;] (do_one_initcall+0x48/0x1bc)
[&lt;c000a5c0&gt;] (do_one_initcall) from [&lt;c05cae6c&gt;] (kernel_init_freeable+0x10c/0x1d8)
[&lt;c05cae6c&gt;] (kernel_init_freeable) from [&lt;c048a000&gt;] (kernel_init+0x8/0xf4)
[&lt;c048a000&gt;] (kernel_init) from [&lt;c00090e0&gt;] (ret_from_fork+0x14/0x34)
Exception stack(0xc6837fb0 to 0xc6837ff8)
7fa0:                                     00000000 00000000 00000000 00000000
7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
---[ end trace 8a8073511be81dd2 ]---

Add a 32-bit mask to the platform device's definition.

Signed-off-by: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;

Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[ Upstream commit 68f2515bb31a664ba3e2bc1eb78dd9f529b10067 ]

The lcdc device is missing the dma_coherent_mask definition causing the
following warning on da850-evm:

da8xx_lcdc da8xx_lcdc.0: found Sharp_LK043T1DG01 panel
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at kernel/dma/mapping.c:247 dma_alloc_attrs+0xc8/0x110
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.0-rc3-00077-g16d72dd4891f #18
Hardware name: DaVinci DA850/OMAP-L138/AM18x EVM
[&lt;c000fce8&gt;] (unwind_backtrace) from [&lt;c000d900&gt;] (show_stack+0x10/0x14)
[&lt;c000d900&gt;] (show_stack) from [&lt;c001a4f8&gt;] (__warn+0xec/0x114)
[&lt;c001a4f8&gt;] (__warn) from [&lt;c001a634&gt;] (warn_slowpath_null+0x3c/0x48)
[&lt;c001a634&gt;] (warn_slowpath_null) from [&lt;c0065860&gt;] (dma_alloc_attrs+0xc8/0x110)
[&lt;c0065860&gt;] (dma_alloc_attrs) from [&lt;c02820f8&gt;] (fb_probe+0x228/0x5a8)
[&lt;c02820f8&gt;] (fb_probe) from [&lt;c02d3e9c&gt;] (platform_drv_probe+0x48/0x9c)
[&lt;c02d3e9c&gt;] (platform_drv_probe) from [&lt;c02d221c&gt;] (really_probe+0x1d8/0x2d4)
[&lt;c02d221c&gt;] (really_probe) from [&lt;c02d2474&gt;] (driver_probe_device+0x5c/0x168)
[&lt;c02d2474&gt;] (driver_probe_device) from [&lt;c02d2728&gt;] (device_driver_attach+0x58/0x60)
[&lt;c02d2728&gt;] (device_driver_attach) from [&lt;c02d27b0&gt;] (__driver_attach+0x80/0xbc)
[&lt;c02d27b0&gt;] (__driver_attach) from [&lt;c02d047c&gt;] (bus_for_each_dev+0x64/0xb4)
[&lt;c02d047c&gt;] (bus_for_each_dev) from [&lt;c02d1590&gt;] (bus_add_driver+0xe4/0x1d8)
[&lt;c02d1590&gt;] (bus_add_driver) from [&lt;c02d301c&gt;] (driver_register+0x78/0x10c)
[&lt;c02d301c&gt;] (driver_register) from [&lt;c000a5c0&gt;] (do_one_initcall+0x48/0x1bc)
[&lt;c000a5c0&gt;] (do_one_initcall) from [&lt;c05cae6c&gt;] (kernel_init_freeable+0x10c/0x1d8)
[&lt;c05cae6c&gt;] (kernel_init_freeable) from [&lt;c048a000&gt;] (kernel_init+0x8/0xf4)
[&lt;c048a000&gt;] (kernel_init) from [&lt;c00090e0&gt;] (ret_from_fork+0x14/0x34)
Exception stack(0xc6837fb0 to 0xc6837ff8)
7fa0:                                     00000000 00000000 00000000 00000000
7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
---[ end trace 8a8073511be81dd2 ]---

Add a 32-bit mask to the platform device's definition.

Signed-off-by: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;

Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: davinci: da850-evm: call regulator_has_full_constraints()</title>
<updated>2019-07-14T06:09:41+00:00</updated>
<author>
<name>Bartosz Golaszewski</name>
<email>bgolaszewski@baylibre.com</email>
</author>
<published>2019-06-07T09:02:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=06004e683ee1138dcf5dae105326460e568a2da4'/>
<id>06004e683ee1138dcf5dae105326460e568a2da4</id>
<content type='text'>
[ Upstream commit 0c0c9b5753cd04601b17de09da1ed2885a3b42fe ]

The BB expander at 0x21 i2c bus 1 fails to probe on da850-evm because
the board doesn't set has_full_constraints to true in the regulator
API.

Call regulator_has_full_constraints() at the end of board registration
just like we do in da850-lcdk and da830-evm.

Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;
Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[ Upstream commit 0c0c9b5753cd04601b17de09da1ed2885a3b42fe ]

The BB expander at 0x21 i2c bus 1 fails to probe on da850-evm because
the board doesn't set has_full_constraints to true in the regulator
API.

Call regulator_has_full_constraints() at the end of board registration
just like we do in da850-lcdk and da830-evm.

Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Bartosz Golaszewski &lt;bgolaszewski@baylibre.com&gt;
Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: dts: am335x phytec boards: Fix cd-gpios active level</title>
<updated>2019-07-14T06:09:40+00:00</updated>
<author>
<name>Teresa Remmet</name>
<email>t.remmet@phytec.de</email>
</author>
<published>2019-05-24T13:19:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=3379bbd0fce938edcb8a35bfe2cb690b888119a8'/>
<id>3379bbd0fce938edcb8a35bfe2cb690b888119a8</id>
<content type='text'>
[ Upstream commit 8a0098c05a272c9a68f6885e09755755b612459c ]

Active level of the mmc1 cd gpio needs to be low instead of high.
Fix PCM-953 and phyBOARD-WEGA.

Signed-off-by: Teresa Remmet &lt;t.remmet@phytec.de&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[ Upstream commit 8a0098c05a272c9a68f6885e09755755b612459c ]

Active level of the mmc1 cd gpio needs to be low instead of high.
Fix PCM-953 and phyBOARD-WEGA.

Signed-off-by: Teresa Remmet &lt;t.remmet@phytec.de&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: dts: Drop bogus CLKSEL for timer12 on dra7</title>
<updated>2019-07-14T06:09:37+00:00</updated>
<author>
<name>Tony Lindgren</name>
<email>tony@atomide.com</email>
</author>
<published>2019-05-30T07:25:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=af5275fc48d2c8e5cd6a72148068be2e9bafc88f'/>
<id>af5275fc48d2c8e5cd6a72148068be2e9bafc88f</id>
<content type='text'>
[ Upstream commit 34f61de87017aff3c8306280d196dddb1e168a88 ]

There is no CLKSEL for timer12 on dra7 unlike for timer1. This
causes issues on booting the device that Tomi noticed if
DEBUG_SLAB is enabled and the clkctrl clock does not properly
handle non-existing clock. Let's drop the bogus CLKSEL clock,
the clkctrl clock handling gets fixed separately.

Cc: Peter Ujfalusi &lt;peter.ujfalusi@ti.com&gt;
Cc: Tero Kristo &lt;t-kristo@ti.com&gt;
Cc: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Reported-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Tested-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Tested-by: Peter Ujfalusi &lt;peter.ujfalusi@ti.com&gt;
Fixes: 4ed0dfe3cf39 ("ARM: dts: dra7: Move l4 child devices to probe them with ti-sysc")
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[ Upstream commit 34f61de87017aff3c8306280d196dddb1e168a88 ]

There is no CLKSEL for timer12 on dra7 unlike for timer1. This
causes issues on booting the device that Tomi noticed if
DEBUG_SLAB is enabled and the clkctrl clock does not properly
handle non-existing clock. Let's drop the bogus CLKSEL clock,
the clkctrl clock handling gets fixed separately.

Cc: Peter Ujfalusi &lt;peter.ujfalusi@ti.com&gt;
Cc: Tero Kristo &lt;t-kristo@ti.com&gt;
Cc: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Reported-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Tested-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
Tested-by: Peter Ujfalusi &lt;peter.ujfalusi@ti.com&gt;
Fixes: 4ed0dfe3cf39 ("ARM: dts: dra7: Move l4 child devices to probe them with ti-sysc")
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node</title>
<updated>2019-07-10T07:52:30+00:00</updated>
<author>
<name>Joshua Scott</name>
<email>joshua.scott@alliedtelesis.co.nz</email>
</author>
<published>2019-06-25T22:11:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=09cc58c8671330bb46294611e61a498f9e817f17'/>
<id>09cc58c8671330bb46294611e61a498f9e817f17</id>
<content type='text'>
commit 80031361747aec92163464f2ee08870fec33bcb0 upstream.

Switch to the "marvell,armada-38x-uart" driver variant to empty
the UART buffer before writing to the UART_LCR register.

Signed-off-by: Joshua Scott &lt;joshua.scott@alliedtelesis.co.nz&gt;
Tested-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Acked-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;.
Cc: stable@vger.kernel.org
Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236")
Signed-off-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 80031361747aec92163464f2ee08870fec33bcb0 upstream.

Switch to the "marvell,armada-38x-uart" driver variant to empty
the UART buffer before writing to the UART_LCR register.

Signed-off-by: Joshua Scott &lt;joshua.scott@alliedtelesis.co.nz&gt;
Tested-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Acked-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;.
Cc: stable@vger.kernel.org
Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236")
Signed-off-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: dts: am57xx-idk: Remove support for voltage switching for SD card</title>
<updated>2019-06-25T03:34:54+00:00</updated>
<author>
<name>Faiz Abbas</name>
<email>faiz_abbas@ti.com</email>
</author>
<published>2019-05-02T08:47:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=e56759725d6e9b641296bcd8deead47d572a162e'/>
<id>e56759725d6e9b641296bcd8deead47d572a162e</id>
<content type='text'>
commit 88a748419b84187fd1da05637b8e5928b04a1e06 upstream.

If UHS speed modes are enabled, a compatible SD card switches down to
1.8V during enumeration. If after this a software reboot/crash takes
place and on-chip ROM tries to enumerate the SD card, the difference in
IO voltages (host @ 3.3V and card @ 1.8V) may end up damaging the card.

The fix for this is to have support for power cycling the card in
hardware (with a PORz/soft-reset line causing a power cycle of the
card). Since am571x-, am572x- and am574x-idk don't have this
capability, disable voltage switching for these boards.

The major effect of this is that the maximum supported speed
mode is now high speed(50 MHz) down from SDR104(200 MHz).

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Faiz Abbas &lt;faiz_abbas@ti.com&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit 88a748419b84187fd1da05637b8e5928b04a1e06 upstream.

If UHS speed modes are enabled, a compatible SD card switches down to
1.8V during enumeration. If after this a software reboot/crash takes
place and on-chip ROM tries to enumerate the SD card, the difference in
IO voltages (host @ 3.3V and card @ 1.8V) may end up damaging the card.

The fix for this is to have support for power cycling the card in
hardware (with a PORz/soft-reset line causing a power cycle of the
card). Since am571x-, am572x- and am574x-idk don't have this
capability, disable voltage switching for these boards.

The major effect of this is that the maximum supported speed
mode is now high speed(50 MHz) down from SDR104(200 MHz).

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Faiz Abbas &lt;faiz_abbas@ti.com&gt;
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: dts: dra76x: Update MMC2_HS200_MANUAL1 iodelay values</title>
<updated>2019-06-25T03:34:54+00:00</updated>
<author>
<name>Faiz Abbas</name>
<email>faiz_abbas@ti.com</email>
</author>
<published>2019-04-30T06:08:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=5cf95590ecee866791172ff4cb273eb6a8e96b34'/>
<id>5cf95590ecee866791172ff4cb273eb6a8e96b34</id>
<content type='text'>
commit c3c0b70cd3f801bded7a548198ee1c9851a0ca82 upstream.

Update the MMC2_HS200_MANUAL1 iodelay values to match with the latest
dra76x data manual[1]. The new iodelay values will have better marginality
and should prevent issues in corner cases.

Also this particular pinctrl-array is using spaces instead of tabs for
spacing between the values and the comments. Fix this as well.

[1] http://www.ti.com/lit/ds/symlink/dra76p.pdf

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Faiz Abbas &lt;faiz_abbas@ti.com&gt;
[tony@atomide.com: updated description with a bit more info]
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit c3c0b70cd3f801bded7a548198ee1c9851a0ca82 upstream.

Update the MMC2_HS200_MANUAL1 iodelay values to match with the latest
dra76x data manual[1]. The new iodelay values will have better marginality
and should prevent issues in corner cases.

Also this particular pinctrl-array is using spaces instead of tabs for
spacing between the values and the comments. Fix this as well.

[1] http://www.ti.com/lit/ds/symlink/dra76p.pdf

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Faiz Abbas &lt;faiz_abbas@ti.com&gt;
[tony@atomide.com: updated description with a bit more info]
Signed-off-by: Tony Lindgren &lt;tony@atomide.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: mvebu_v7_defconfig: fix Ethernet on Clearfog</title>
<updated>2019-06-25T03:34:54+00:00</updated>
<author>
<name>Jan Kundrát</name>
<email>jan.kundrat@cesnet.cz</email>
</author>
<published>2019-05-17T15:01:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=092686925bf5026e2d517aa5593ca9a2a313af6f'/>
<id>092686925bf5026e2d517aa5593ca9a2a313af6f</id>
<content type='text'>
commit cc538ca4308372e81b824be08561c466b1d73b72 upstream.

Compared to kernel 5.0, patches merged for 5.1 added support for A38x'
PHY guarded by a config option which was not enabled by default. As a
result, there was no eth1 and eth2 on a Solid Run Clearfog Base.

Ensure that A38x PHY is enabled on mvebu.

[gregory: issue appeared in 5.1 not in 5.2 and added Fixes tag]

Signed-off-by: Jan Kundrát &lt;jan.kundrat@cesnet.cz&gt;
Cc: Baruch Siach &lt;baruch@tkos.co.il&gt;
Cc: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Cc: Russell King &lt;rmk+kernel@armlinux.org.uk&gt;
Cc: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Maxime Chevallier &lt;maxime.chevallier@bootlin.com&gt;
Fixes: a10c1c8191e0 ("net: marvell: neta: add comphy support")
Cc: stable@kernel.org
Signed-off-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit cc538ca4308372e81b824be08561c466b1d73b72 upstream.

Compared to kernel 5.0, patches merged for 5.1 added support for A38x'
PHY guarded by a config option which was not enabled by default. As a
result, there was no eth1 and eth2 on a Solid Run Clearfog Base.

Ensure that A38x PHY is enabled on mvebu.

[gregory: issue appeared in 5.1 not in 5.2 and added Fixes tag]

Signed-off-by: Jan Kundrát &lt;jan.kundrat@cesnet.cz&gt;
Cc: Baruch Siach &lt;baruch@tkos.co.il&gt;
Cc: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Cc: Russell King &lt;rmk+kernel@armlinux.org.uk&gt;
Cc: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Maxime Chevallier &lt;maxime.chevallier@bootlin.com&gt;
Fixes: a10c1c8191e0 ("net: marvell: neta: add comphy support")
Cc: stable@kernel.org
Signed-off-by: Gregory CLEMENT &lt;gregory.clement@bootlin.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX</title>
<updated>2019-06-25T03:34:54+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@gmail.com</email>
</author>
<published>2019-05-13T03:15:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=84d2456e0c0cadb7843339f61eeabb005401f328'/>
<id>84d2456e0c0cadb7843339f61eeabb005401f328</id>
<content type='text'>
commit b25af2ff7c07bd19af74e3f64ff82e2880d13d81 upstream.

Since commit 1e434b703248 ("ARM: imx: update the cpu power up timing
setting on i.mx6sx") some characters loss is noticed on i.MX6ULL UART
as reported by Christoph Niedermaier.

The intention of such commit was to increase the SW2ISO field for i.MX6SX
only, but since cpuidle-imx6sx is also used on i.MX6UL/i.MX6ULL this caused
unintended side effects on other SoCs.

Fix this problem by keeping the original SW2ISO value for i.MX6UL/i.MX6ULL
and only increase SW2ISO in the i.MX6SX case.

Cc: stable@vger.kernel.org
Fixes: 1e434b703248 ("ARM: imx: update the cpu power up timing setting on i.mx6sx")
Reported-by: Christoph Niedermaier &lt;cniedermaier@dh-electronics.com&gt;
Signed-off-by: Fabio Estevam &lt;festevam@gmail.com&gt;
Tested-by: Sébastien Szymanski &lt;sebastien.szymanski@armadeus.com&gt;
Tested-by: Christoph Niedermaier &lt;cniedermaier@dh-electronics.com&gt;
Signed-off-by: Shawn Guo &lt;shawnguo@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit b25af2ff7c07bd19af74e3f64ff82e2880d13d81 upstream.

Since commit 1e434b703248 ("ARM: imx: update the cpu power up timing
setting on i.mx6sx") some characters loss is noticed on i.MX6ULL UART
as reported by Christoph Niedermaier.

The intention of such commit was to increase the SW2ISO field for i.MX6SX
only, but since cpuidle-imx6sx is also used on i.MX6UL/i.MX6ULL this caused
unintended side effects on other SoCs.

Fix this problem by keeping the original SW2ISO value for i.MX6UL/i.MX6ULL
and only increase SW2ISO in the i.MX6SX case.

Cc: stable@vger.kernel.org
Fixes: 1e434b703248 ("ARM: imx: update the cpu power up timing setting on i.mx6sx")
Reported-by: Christoph Niedermaier &lt;cniedermaier@dh-electronics.com&gt;
Signed-off-by: Fabio Estevam &lt;festevam@gmail.com&gt;
Tested-by: Sébastien Szymanski &lt;sebastien.szymanski@armadeus.com&gt;
Tested-by: Christoph Niedermaier &lt;cniedermaier@dh-electronics.com&gt;
Signed-off-by: Shawn Guo &lt;shawnguo@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</pre>
</div>
</content>
</entry>
<entry>
<title>KVM: arm/arm64: Move cc/it checks under hyp's Makefile to avoid instrumentation</title>
<updated>2019-06-19T06:00:11+00:00</updated>
<author>
<name>James Morse</name>
<email>james.morse@arm.com</email>
</author>
<published>2019-05-22T17:47:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.exis.tech/linux.git/commit/?id=cf2a3bd43c54b94e4bcd38856c38a164fc43e40c'/>
<id>cf2a3bd43c54b94e4bcd38856c38a164fc43e40c</id>
<content type='text'>
[ Upstream commit 623e1528d4090bd1abaf93ec46f047dee9a6fb32 ]

KVM has helpers to handle the condition codes of trapped aarch32
instructions. These are marked __hyp_text and used from HYP, but they
aren't built by the 'hyp' Makefile, which has all the runes to avoid ASAN
and KCOV instrumentation.

Move this code to a new hyp/aarch32.c to avoid a hyp-panic when starting
an aarch32 guest on a host built with the ASAN/KCOV debug options.

Fixes: 021234ef3752f ("KVM: arm64: Make kvm_condition_valid32() accessible from EL2")
Fixes: 8cebe750c4d9a ("arm64: KVM: Make kvm_skip_instr32 available to HYP")
Signed-off-by: James Morse &lt;james.morse@arm.com&gt;
Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[ Upstream commit 623e1528d4090bd1abaf93ec46f047dee9a6fb32 ]

KVM has helpers to handle the condition codes of trapped aarch32
instructions. These are marked __hyp_text and used from HYP, but they
aren't built by the 'hyp' Makefile, which has all the runes to avoid ASAN
and KCOV instrumentation.

Move this code to a new hyp/aarch32.c to avoid a hyp-panic when starting
an aarch32 guest on a host built with the ASAN/KCOV debug options.

Fixes: 021234ef3752f ("KVM: arm64: Make kvm_condition_valid32() accessible from EL2")
Fixes: 8cebe750c4d9a ("arm64: KVM: Make kvm_skip_instr32 available to HYP")
Signed-off-by: James Morse &lt;james.morse@arm.com&gt;
Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
