<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/arch/arm, branch dev-5.3</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.3</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-5.3'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2019-12-11T22:32:06+00:00</updated>
<entry>
<title>Merge tag 'v5.3.15' into dev-5.3</title>
<updated>2019-12-11T22:32:06+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2019-12-11T22:32:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=fdc60468f3e452364d432f1a7c3f83d58bba1b84'/>
<id>urn:sha1:fdc60468f3e452364d432f1a7c3f83d58bba1b84</id>
<content type='text'>
This is the 5.3.15 stable release

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>ARM: dts: stm32: Fix CAN RAM mapping on stm32mp157c</title>
<updated>2019-12-04T21:33:48+00:00</updated>
<author>
<name>Christophe Roullier</name>
<email>christophe.roullier@st.com</email>
</author>
<published>2019-11-04T14:31:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=904c854284168fe507b688d4d0d91550e60d9d48'/>
<id>urn:sha1:904c854284168fe507b688d4d0d91550e60d9d48</id>
<content type='text'>
[ Upstream commit 9df50c2e16de7fd739d11d37303afec9e573b46f ]

Split the 10Kbytes CAN message RAM to be able to use simultaneously
FDCAN1 and FDCAN2 instances.
First 5Kbytes are allocated to FDCAN1 and last 5Kbytes are used for
FDCAN2. To do so, set the offset to 0x1400 in mram-cfg for FDCAN2.

Fixes: d44d6e021301 ("ARM: dts: stm32: change CAN RAM mapping on stm32mp157c")
Signed-off-by: Christophe Roullier &lt;christophe.roullier@st.com&gt;
Signed-off-by: Alexandre Torgue &lt;alexandre.torgue@st.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>ARM: dts: sun8i-a83t-tbs-a711: Fix WiFi resume from suspend</title>
<updated>2019-12-04T21:33:17+00:00</updated>
<author>
<name>Ondrej Jirman</name>
<email>megous@megous.com</email>
</author>
<published>2019-10-28T21:58:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=83e0b5fb2766fabdb52c03bf90acb8029da9a18f'/>
<id>urn:sha1:83e0b5fb2766fabdb52c03bf90acb8029da9a18f</id>
<content type='text'>
[ Upstream commit e614f341253f8541baf0230a8dc6a016b544b1e2 ]

Without enabling keep-power-in-suspend, we can't wake the device
up using WOL packet, and the log is flooded with these messages
on resume:

sunxi-mmc 1c10000.mmc: send stop command failed
sunxi-mmc 1c10000.mmc: data error, sending stop command
sunxi-mmc 1c10000.mmc: send stop command failed
sunxi-mmc 1c10000.mmc: data error, sending stop command

So to make the WiFi really a wakeup-source, we need to keep it powered
during suspend.

Fixes: 0e23372080def7 ("arm: dts: sun8i: Add the TBS A711 tablet devicetree")
Signed-off-by: Ondrej Jirman &lt;megous@megous.com&gt;
Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>ARM: dts: imx6qdl-sabreauto: Fix storm of accelerometer interrupts</title>
<updated>2019-12-04T21:33:11+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@gmail.com</email>
</author>
<published>2019-10-09T20:43:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=46a19e3541702857c38296b42101c9dea36a7fd7'/>
<id>urn:sha1:46a19e3541702857c38296b42101c9dea36a7fd7</id>
<content type='text'>
[ Upstream commit 7e5d0bf6afcc7bd72f78e7f33570e2e0945624f0 ]

Since commit a211b8c55f3c ("ARM: dts: imx6qdl-sabreauto: Add sensors")
a storm of accelerometer interrupts is seen:

[  114.211283] irq 260: nobody cared (try booting with the "irqpoll" option)
[  114.218108] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.3.4 #1
[  114.223960] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[  114.230531] [&lt;c0112858&gt;] (unwind_backtrace) from [&lt;c010cdc8&gt;] (show_stack+0x10/0x14)
[  114.238301] [&lt;c010cdc8&gt;] (show_stack) from [&lt;c0c1aa1c&gt;] (dump_stack+0xd8/0x110)
[  114.245644] [&lt;c0c1aa1c&gt;] (dump_stack) from [&lt;c0193594&gt;] (__report_bad_irq+0x30/0xc0)
[  114.253417] [&lt;c0193594&gt;] (__report_bad_irq) from [&lt;c01933ac&gt;] (note_interrupt+0x108/0x298)
[  114.261707] [&lt;c01933ac&gt;] (note_interrupt) from [&lt;c018ffe4&gt;] (handle_irq_event_percpu+0x70/0x80)
[  114.270433] [&lt;c018ffe4&gt;] (handle_irq_event_percpu) from [&lt;c019002c&gt;] (handle_irq_event+0x38/0x5c)
[  114.279326] [&lt;c019002c&gt;] (handle_irq_event) from [&lt;c019438c&gt;] (handle_level_irq+0xc8/0x154)
[  114.287701] [&lt;c019438c&gt;] (handle_level_irq) from [&lt;c018eda0&gt;] (generic_handle_irq+0x20/0x34)
[  114.296166] [&lt;c018eda0&gt;] (generic_handle_irq) from [&lt;c0534214&gt;] (mxc_gpio_irq_handler+0x30/0xf0)
[  114.304975] [&lt;c0534214&gt;] (mxc_gpio_irq_handler) from [&lt;c0534334&gt;] (mx3_gpio_irq_handler+0x60/0xb0)
[  114.313955] [&lt;c0534334&gt;] (mx3_gpio_irq_handler) from [&lt;c018eda0&gt;] (generic_handle_irq+0x20/0x34)
[  114.322762] [&lt;c018eda0&gt;] (generic_handle_irq) from [&lt;c018f3ac&gt;] (__handle_domain_irq+0x64/0xe0)
[  114.331485] [&lt;c018f3ac&gt;] (__handle_domain_irq) from [&lt;c05215a8&gt;] (gic_handle_irq+0x4c/0xa8)
[  114.339862] [&lt;c05215a8&gt;] (gic_handle_irq) from [&lt;c0101a70&gt;] (__irq_svc+0x70/0x98)
[  114.347361] Exception stack(0xc1301ec0 to 0xc1301f08)
[  114.352435] 1ec0: 00000001 00000006 00000000 c130c340 00000001 c130f688 9785636d c13ea2e8
[  114.360635] 1ee0: 9784907d 0000001a eaf99d78 0000001a 00000000 c1301f10 c0182b00 c0878de4
[  114.368830] 1f00: 20000013 ffffffff
[  114.372349] [&lt;c0101a70&gt;] (__irq_svc) from [&lt;c0878de4&gt;] (cpuidle_enter_state+0x168/0x5f4)
[  114.380464] [&lt;c0878de4&gt;] (cpuidle_enter_state) from [&lt;c08792ac&gt;] (cpuidle_enter+0x28/0x38)
[  114.388751] [&lt;c08792ac&gt;] (cpuidle_enter) from [&lt;c015ef9c&gt;] (do_idle+0x224/0x2a8)
[  114.396168] [&lt;c015ef9c&gt;] (do_idle) from [&lt;c015f3b8&gt;] (cpu_startup_entry+0x18/0x20)
[  114.403765] [&lt;c015f3b8&gt;] (cpu_startup_entry) from [&lt;c1200e54&gt;] (start_kernel+0x43c/0x500)
[  114.411958] handlers:
[  114.414302] [&lt;a01028b8&gt;] irq_default_primary_handler threaded [&lt;fd7a3b08&gt;] mma8452_interrupt
[  114.422974] Disabling IRQ #260

           CPU0       CPU1
....
260:     100001          0  gpio-mxc  31 Level     mma8451

The MMA8451 interrupt triggers as low level, so the GPIO6_IO31 pin
needs to activate its pull up, otherwise it will stay always at low level
generating multiple interrupts.

The current device tree does not configure the IOMUX for this pin, so
it uses whathever comes configured from the bootloader.

The IOMUXC_SW_PAD_CTL_PAD_EIM_BCLK register value comes as 0x8000 from
the bootloader, which has PKE bit cleared, hence disabling the
pull-up.

Instead of relying on a previous configuration from the bootloader,
configure the GPIO6_IO31 pin with pull-up enabled in order to fix
this problem.

Fixes: a211b8c55f3c ("ARM: dts: imx6qdl-sabreauto: Add sensors")
Signed-off-by: Fabio Estevam &lt;festevam@gmail.com&gt;
Reviewed-By: Leonard Crestez &lt;leonard.crestez@nxp.com&gt;
Signed-off-by: Shawn Guo &lt;shawnguo@kernel.org&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>ARM: 8904/1: skip nomap memblocks while finding the lowmem/highmem boundary</title>
<updated>2019-11-29T09:07:58+00:00</updated>
<author>
<name>Chester Lin</name>
<email>clin@suse.com</email>
</author>
<published>2019-08-30T13:30:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=99a1e28ad5ee8685c2ddd2e46ffb37a42032a362'/>
<id>urn:sha1:99a1e28ad5ee8685c2ddd2e46ffb37a42032a362</id>
<content type='text'>
commit 1d31999cf04c21709f72ceb17e65b54a401330da upstream.

adjust_lowmem_bounds() checks every memblocks in order to find the boundary
between lowmem and highmem. However some memblocks could be marked as NOMAP
so they are not used by kernel, which should be skipped while calculating
the boundary.

Signed-off-by: Chester Lin &lt;clin@suse.com&gt;
Reviewed-by: Mike Rapoport &lt;rppt@linux.ibm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@armlinux.org.uk&gt;
Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Merge tag 'v5.3.11' into dev-5.3</title>
<updated>2019-11-13T07:23:33+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2019-11-13T07:23:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=d41fa1fda16b4b0f9a2d098c1de8f259a00cc9bc'/>
<id>urn:sha1:d41fa1fda16b4b0f9a2d098c1de8f259a00cc9bc</id>
<content type='text'>
This is the 5.3.11 stable release

 Conflicts:
	drivers/pinctrl/intel/pinctrl-cherryview.c

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>ARM: dts: aspeed: rainier: Switch PSUs to unknown version</title>
<updated>2019-11-13T07:12:34+00:00</updated>
<author>
<name>Eddie James</name>
<email>eajames@linux.ibm.com</email>
</author>
<published>2019-11-08T21:14:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=3b68da1294e8babbc9972c7c0bf59f56a9db16b5'/>
<id>urn:sha1:3b68da1294e8babbc9972c7c0bf59f56a9db16b5</id>
<content type='text'>
Rainier can use either version of the IBM CFFPS, so don't set the
version in the devicetree so the driver can detect it automatically.

OpenBMC-Staging-Count: 1
Signed-off-by: Eddie James &lt;eajames@linux.ibm.com&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>ARM: dts: stm32: change joystick pinctrl definition on stm32mp157c-ev1</title>
<updated>2019-11-12T18:28:21+00:00</updated>
<author>
<name>Amelie Delaunay</name>
<email>amelie.delaunay@st.com</email>
</author>
<published>2019-11-04T10:55:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e74a78cf2f699385ca043f781f50ec0e8e69fed5'/>
<id>urn:sha1:e74a78cf2f699385ca043f781f50ec0e8e69fed5</id>
<content type='text'>
[ Upstream commit f4d6e0f79bcde7810890563bac8e0f3479fe6d03 ]

Pins used for joystick are all configured as input. "push-pull" is not a
valid setting for an input pin.

Fixes: a502b343ebd0 ("pinctrl: stmfx: update pinconf settings")
Signed-off-by: Alexandre Torgue &lt;alexandre.torgue@st.com&gt;
Signed-off-by: Amelie Delaunay &lt;amelie.delaunay@st.com&gt;
Signed-off-by: Alexandre Torgue &lt;alexandre.torgue@st.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>ARM: dts: imx6-logicpd: Re-enable SNVS power key</title>
<updated>2019-11-12T18:27:10+00:00</updated>
<author>
<name>Adam Ford</name>
<email>aford173@gmail.com</email>
</author>
<published>2019-10-16T14:40:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=6972f6cdf9b4d1367df7e45e4471d9e1124a0b85'/>
<id>urn:sha1:6972f6cdf9b4d1367df7e45e4471d9e1124a0b85</id>
<content type='text'>
commit cabe5f85e63626c00f3b879a670ec27325056a2d upstream.

The baseboard of the Logic PD i.MX6 development kit has a power
button routed which can both power down and power up the board.
It can also wake the board from sleep.  This functionality was
marked as disabled by default in imx6qdl.dtsi, so it needs to
be explicitly enabled for each board.

This patch enables the snvs power key again.

Signed-off-by: Adam Ford &lt;aford173@gmail.com&gt;
Fixes: 770856f0da5d ("ARM: dts: imx6qdl: Enable SNVS power key according to board design")
Cc: stable &lt;stable@vger.kernel.org&gt; #5.3+
Signed-off-by: Shawn Guo &lt;shawnguo@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ARM: sunxi: Fix CPU powerdown on A83T</title>
<updated>2019-11-12T18:27:09+00:00</updated>
<author>
<name>Ondrej Jirman</name>
<email>megous@megous.com</email>
</author>
<published>2019-10-28T21:49:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=88fd55d3dd2537a8c0f0b60f8ed43396c96b4ca8'/>
<id>urn:sha1:88fd55d3dd2537a8c0f0b60f8ed43396c96b4ca8</id>
<content type='text'>
commit e690053e97e7a9c968df9a97cef9089dfa8e6a44 upstream.

PRCM_PWROFF_GATING_REG has CPU0 at bit 4 on A83T. So without this
patch, instead of gating the CPU0, the whole cluster was power gated,
when shutting down first CPU in the cluster.

Fixes: 6961275e72a8c1 ("ARM: sun8i: smp: Add support for A83T")
Signed-off-by: Ondrej Jirman &lt;megous@megous.com&gt;
Acked-by: Chen-Yu Tsai &lt;wens@csie.org&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
