Re: [alsa-devel] [PATCH 4/4] ASoC: simple-card: Support for selecting system clocks by ID

On 04/22/16 01:29, Stephen Boyd wrote: >>> The first issue with converting the McASP to use CCF internally for clock >>> selection, muxing and rate configuration is that the daVinci platform does >>> not >>> use CCF at all. Given that the davinci-mcasp driver is used by daVinci, we >>> need to

Re: [alsa-devel] [PATCH 4/4] ASoC: simple-card: Support for selecting system clocks by ID

On 04/22/16 01:29, Stephen Boyd wrote: >>> The first issue with converting the McASP to use CCF internally for clock >>> selection, muxing and rate configuration is that the daVinci platform does >>> not >>> use CCF at all. Given that the davinci-mcasp driver is used by daVinci, we >>> need to

Re: [PATCH 10/11] arm64: tegra: Add clock properties on cpu0 for Tegra210

Hi Penny, On 22/04/16 11:31, Penny Chiu wrote: > Add clocks, clock-names, and clock-latency into cpu0 node. > These properties will be used by cpufreq driver. > > Signed-off-by: Penny Chiu > --- > arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 ++ > 1 file changed, 6

Re: [PATCH 10/11] arm64: tegra: Add clock properties on cpu0 for Tegra210

Hi Penny, On 22/04/16 11:31, Penny Chiu wrote: > Add clocks, clock-names, and clock-latency into cpu0 node. > These properties will be used by cpufreq driver. > > Signed-off-by: Penny Chiu > --- > arch/arm64/boot/dts/nvidia/tegra210.dtsi | 6 ++ > 1 file changed, 6 insertions(+) > > diff

Re: [PATCH v1 08/23] ata: sata_dwc_460ex: don't call ata_sff_qc_issue() on DMA commands

On Friday, April 22, 2016 11:32:00 AM David Laight wrote: > From: Andy Shevchenko > > Sent: 21 April 2016 19:15 > > ata_sff_qc_issue() can't handle DMA commands and thus we have to avoid it > > for > > them. Do call ata_bmdma_qc_issue() instead for this case. > > > > Suggested-by: Christian

Re: [PATCH v1 08/23] ata: sata_dwc_460ex: don't call ata_sff_qc_issue() on DMA commands

On Friday, April 22, 2016 11:32:00 AM David Laight wrote: > From: Andy Shevchenko > > Sent: 21 April 2016 19:15 > > ata_sff_qc_issue() can't handle DMA commands and thus we have to avoid it > > for > > them. Do call ata_bmdma_qc_issue() instead for this case. > > > > Suggested-by: Christian

Re: [PATCH v7 6/7] iommu/arm-smmu: do not advertise IOMMU_CAP_INTR_REMAP

Hi Robin, On 04/22/2016 01:16 PM, Robin Murphy wrote: > Hi Eric, Alex, > > On 19/04/16 18:24, Eric Auger wrote: >> Do not advertise IOMMU_CAP_INTR_REMAP for arm-smmu(-v3). Indeed the >> irq_remapping capability is abstracted on irqchip side for ARM as >> opposed to Intel IOMMU featuring IRQ

Re: [PATCH v7 6/7] iommu/arm-smmu: do not advertise IOMMU_CAP_INTR_REMAP

Hi Robin, On 04/22/2016 01:16 PM, Robin Murphy wrote: > Hi Eric, Alex, > > On 19/04/16 18:24, Eric Auger wrote: >> Do not advertise IOMMU_CAP_INTR_REMAP for arm-smmu(-v3). Indeed the >> irq_remapping capability is abstracted on irqchip side for ARM as >> opposed to Intel IOMMU featuring IRQ

[PATCH 3.12 08/78] qmi_wwan: add the second QMI/network interface for Sierra Wireless MC7305/MC7355

From: Reinhard Speyerer 3.12-stable review patch. If anyone has any objections, please let me know. === commit e3426ca7bc2957ee072f61360c2b81b4adb629ad upstream. Sierra Wireless MC7305/MC7355 with USB ID 1199:9041 also provide a second QMI/network interface like

[PATCH 3.12 08/78] qmi_wwan: add the second QMI/network interface for Sierra Wireless MC7305/MC7355

From: Reinhard Speyerer 3.12-stable review patch. If anyone has any objections, please let me know. === commit e3426ca7bc2957ee072f61360c2b81b4adb629ad upstream. Sierra Wireless MC7305/MC7355 with USB ID 1199:9041 also provide a second QMI/network interface like the MC73xx with

[PATCH 3.12 00/78] 3.12.59-stable review

This is the start of the stable review cycle for the 3.12.59 release. There are 78 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Apr 26 13:05:33 CEST 2016. Anything

[PATCH 3.12 00/78] 3.12.59-stable review

This is the start of the stable review cycle for the 3.12.59 release. There are 78 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Apr 26 13:05:33 CEST 2016. Anything

[PATCH 3.12 09/78] qmi_wwan: Add support for Dell Wireless 5809e 4G Modem

From: Pieter Hollants 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2070c48cf2b78af89ba529c00992eaaa18df8ef7 upstream. Added the USB IDs 0x413c:0x81b1 for the "Dell Wireless 5809e Gobi(TM) 4G LTE Mobile Broadband

[PATCH v8 08/24] iio: imu: inv_mpu6050: convert to use an explicit i2c mux core

Allocate an explicit i2c mux core to handle parent and child adapters etc. Update the select/deselect ops to be in terms of the i2c mux core instead of the child adapter. Acked-by: Jonathan Cameron Signed-off-by: Peter Rosin ---

[PATCH 3.12 07/78] net: qmi_wwan: interface #11 in Sierra Wireless MC73xx is not QMI

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit fc0d6e9cd0aefbe5de5ebafb1805f2c59539725b upstream. This interface is unusable, as the cdc-wdm character device doesn't reply to any QMI

[PATCH v8 08/24] iio: imu: inv_mpu6050: convert to use an explicit i2c mux core

Allocate an explicit i2c mux core to handle parent and child adapters etc. Update the select/deselect ops to be in terms of the i2c mux core instead of the child adapter. Acked-by: Jonathan Cameron Signed-off-by: Peter Rosin --- drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c | 2 +-

[PATCH 3.12 07/78] net: qmi_wwan: interface #11 in Sierra Wireless MC73xx is not QMI

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit fc0d6e9cd0aefbe5de5ebafb1805f2c59539725b upstream. This interface is unusable, as the cdc-wdm character device doesn't reply to any QMI command. Also, the out-of-tree

[PATCH 3.12 09/78] qmi_wwan: Add support for Dell Wireless 5809e 4G Modem

From: Pieter Hollants 3.12-stable review patch. If anyone has any objections, please let me know. === commit 2070c48cf2b78af89ba529c00992eaaa18df8ef7 upstream. Added the USB IDs 0x413c:0x81b1 for the "Dell Wireless 5809e Gobi(TM) 4G LTE Mobile Broadband Card", a Dell-branded

[PATCH 3.12 13/78] net: qmi_wwan: remove 1199:9070 device id

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit 544c8f6507303e921979ac99f46f00a88b42b6e8 upstream. This turned out to be a bootloader device ID. No need for that in this driver. It will only provide a single

[PATCH 3.12 14/78] net: qmi_wwan: Add WeTelecom-WPD600N

From: Kristian Evensen 3.12-stable review patch. If anyone has any objections, please let me know. === commit e439bd4a4fdeb29488f48f14845ad35607e6302c upstream. The WeTelecom-WPD600N is an LTE module that, in addition to supporting most "normal" bands,

[PATCH 3.12 11/78] net: qmi_wwan: Sierra Wireless MC73xx -> Sierra Wireless MC7304/MC7354

From: David Ward 3.12-stable review patch. If anyone has any objections, please let me know. === commit e704059272aae2aaa5e5ce7a76e4c27c492e947e upstream. Other Sierra Wireless MC73xx devices exist, with different USB IDs. Cc: Bjørn Mork

[PATCH 3.12 13/78] net: qmi_wwan: remove 1199:9070 device id

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit 544c8f6507303e921979ac99f46f00a88b42b6e8 upstream. This turned out to be a bootloader device ID. No need for that in this driver. It will only provide a single serial

[PATCH 3.12 14/78] net: qmi_wwan: Add WeTelecom-WPD600N

From: Kristian Evensen 3.12-stable review patch. If anyone has any objections, please let me know. === commit e439bd4a4fdeb29488f48f14845ad35607e6302c upstream. The WeTelecom-WPD600N is an LTE module that, in addition to supporting most "normal" bands, also supports LTE over

[PATCH 3.12 11/78] net: qmi_wwan: Sierra Wireless MC73xx -> Sierra Wireless MC7304/MC7354

From: David Ward 3.12-stable review patch. If anyone has any objections, please let me know. === commit e704059272aae2aaa5e5ce7a76e4c27c492e947e upstream. Other Sierra Wireless MC73xx devices exist, with different USB IDs. Cc: Bjørn Mork Signed-off-by: David Ward

[PATCH 3.12 12/78] qmi_wwan: add Sierra Wireless MC74xx/EM74xx

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit 0db65fcfcded76fe4f74e3ca9f4e2baf67b683ef upstream. New device IDs shamelessly lifted from the vendor driver. Signed-off-by: Bjørn Mork

[PATCH 3.12 12/78] qmi_wwan: add Sierra Wireless MC74xx/EM74xx

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit 0db65fcfcded76fe4f74e3ca9f4e2baf67b683ef upstream. New device IDs shamelessly lifted from the vendor driver. Signed-off-by: Bjørn Mork Signed-off-by: David S. Miller

[PATCH 3.12 10/78] net: qmi_wwan: add HP lt4111 LTE/EV-DO/HSPA+ Gobi 4G Module

From: David Ward 3.12-stable review patch. If anyone has any objections, please let me know. === commit a8079092c1bbf9aec3756b35256c7816b8845af7 upstream. This is an HP-branded Sierra Wireless EM7355: https://bugzilla.redhat.com/show_bug.cgi?id=1223646#c2

Re: [PATCHv5 3/3] selftest/x86: add mremap vdso 32-bit test

On 04/21/2016 11:01 PM, Andy Lutomirski wrote: On Mon, Apr 18, 2016 at 6:43 AM, Dmitry Safonov wrote: Should print on success: [root@localhost ~]# ./test_mremap_vdso_32 AT_SYSINFO_EHDR is 0xf773f000 [NOTE] Moving vDSO: [f773f000, f774] -> [a00,

[PATCH 3.12 10/78] net: qmi_wwan: add HP lt4111 LTE/EV-DO/HSPA+ Gobi 4G Module

From: David Ward 3.12-stable review patch. If anyone has any objections, please let me know. === commit a8079092c1bbf9aec3756b35256c7816b8845af7 upstream. This is an HP-branded Sierra Wireless EM7355: https://bugzilla.redhat.com/show_bug.cgi?id=1223646#c2 Signed-off-by: David

Re: [PATCHv5 3/3] selftest/x86: add mremap vdso 32-bit test

On 04/21/2016 11:01 PM, Andy Lutomirski wrote: On Mon, Apr 18, 2016 at 6:43 AM, Dmitry Safonov wrote: Should print on success: [root@localhost ~]# ./test_mremap_vdso_32 AT_SYSINFO_EHDR is 0xf773f000 [NOTE] Moving vDSO: [f773f000, f774] -> [a00, a001000] [OK] Or segfault if

Re: [RFC][PATCH 04/31] locking,arm: Implement atomic{,64}_fetch_{add,sub,and,andnot,or,xor}{,_relaxed,_acquire,_release}()

On Fri, Apr 22, 2016 at 11:04:17AM +0200, Peter Zijlstra wrote: > Implement FETCH-OP atomic primitives, these are very similar to the > existing OP-RETURN primitives we already have, except they return the > value of the atomic variable _before_ modification. > > This is especially useful for

[PATCH 3.12 16/78] Add Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card (rev3) to qmi_wwan

From: Patrik Halfar 3.12-stable review patch. If anyone has any objections, please let me know. === commit fb5eb24cdd5cdb83be77d3e4b2f16e92e06bd9e9 upstream. New revison of Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card has new idProduct Bus

Re: [RFC][PATCH 04/31] locking,arm: Implement atomic{,64}_fetch_{add,sub,and,andnot,or,xor}{,_relaxed,_acquire,_release}()

On Fri, Apr 22, 2016 at 11:04:17AM +0200, Peter Zijlstra wrote: > Implement FETCH-OP atomic primitives, these are very similar to the > existing OP-RETURN primitives we already have, except they return the > value of the atomic variable _before_ modification. > > This is especially useful for

[PATCH 3.12 16/78] Add Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card (rev3) to qmi_wwan

From: Patrik Halfar 3.12-stable review patch. If anyone has any objections, please let me know. === commit fb5eb24cdd5cdb83be77d3e4b2f16e92e06bd9e9 upstream. New revison of Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card has new idProduct Bus 002 Device 006: ID

[PATCH 3.12 15/78] net: qmi_wwan: Add SIMCom 7230E

From: Kristian Evensen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 18715b261541f35ccede9b8686ee3ebaac697d38 upstream. SIMCom 7230E is a QMI LTE module with support for most "normal" bands. Manual testing has

[PATCH 3.12 05/78] net: qmi_wwan: add Netgear AirCard 341U

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit 4324be1e0bab67194a263be263b7e48c176d43c7 upstream. Signed-off-by: Aleksander Morgado Acked-by: Bjørn Mork

[PATCH 3.12 19/78] qmi_wwan/cdc_ether: move Novatel E371 (1410:9011) to qmi_wwan

From: Yegor Yefremov 3.12-stable review patch. If anyone has any objections, please let me know. === commit 7b5939ba591e9affbe4f336935b0985fd250a2b3 upstream. This device provides QMI and ethernet functionality via a standard CDC ethernet descriptor.

[PATCH 3.12 05/78] net: qmi_wwan: add Netgear AirCard 341U

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit 4324be1e0bab67194a263be263b7e48c176d43c7 upstream. Signed-off-by: Aleksander Morgado Acked-by: Bjørn Mork Signed-off-by: David S. Miller Signed-off-by: Jiri Slaby

[PATCH 3.12 19/78] qmi_wwan/cdc_ether: move Novatel E371 (1410:9011) to qmi_wwan

From: Yegor Yefremov 3.12-stable review patch. If anyone has any objections, please let me know. === commit 7b5939ba591e9affbe4f336935b0985fd250a2b3 upstream. This device provides QMI and ethernet functionality via a standard CDC ethernet descriptor. But when driven by

[PATCH 3.12 15/78] net: qmi_wwan: Add SIMCom 7230E

From: Kristian Evensen 3.12-stable review patch. If anyone has any objections, please let me know. === commit 18715b261541f35ccede9b8686ee3ebaac697d38 upstream. SIMCom 7230E is a QMI LTE module with support for most "normal" bands. Manual testing has showed that only interface

[PATCH 3.12 04/78] qmi_wwan: add "D-Link DWM-221 B1" device id

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit e84810c7b85a2d7897797b3ad3e879168a8e032a upstream. Thomas reports: "Windows: 00 diagnostics 01 modem 02 at-port 03 nmea 04 nic Linux: T: Bus=02 Lev=01

[PATCH 3.12 04/78] qmi_wwan: add "D-Link DWM-221 B1" device id

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit e84810c7b85a2d7897797b3ad3e879168a8e032a upstream. Thomas reports: "Windows: 00 diagnostics 01 modem 02 at-port 03 nmea 04 nic Linux: T: Bus=02 Lev=01 Prnt=01 Port=03

RE: [PATCH v1 08/23] ata: sata_dwc_460ex: don't call ata_sff_qc_issue() on DMA commands

From: Andy Shevchenko > Sent: 21 April 2016 19:15 > ata_sff_qc_issue() can't handle DMA commands and thus we have to avoid it for > them. Do call ata_bmdma_qc_issue() instead for this case. > > Suggested-by: Christian Lamparter > Signed-off-by: Andy Shevchenko

RE: [PATCH v1 08/23] ata: sata_dwc_460ex: don't call ata_sff_qc_issue() on DMA commands

From: Andy Shevchenko > Sent: 21 April 2016 19:15 > ata_sff_qc_issue() can't handle DMA commands and thus we have to avoid it for > them. Do call ata_bmdma_qc_issue() instead for this case. > > Suggested-by: Christian Lamparter > Signed-off-by: Andy Shevchenko > --- >

[PATCH 3.12 21/78] cdc_ncm: toggle altsetting to force reset before setup

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 48906f62c96cc2cd35753e59310cb70eb08cc6a5 ] Some devices will silently fail setup unless they are reset first. This is necessary even if the data

Re: [PATCH v10 1/2] perf config: Prepare all default configs

Hi, On 04/22/2016 07:21 PM, Taeung Song wrote: To precisely manage configs, prepare all default perf's configs that contain default section name, variable name, value and correct type, not string type. In the near future, this will be used when checking type of config variable or showing all

[PATCH 3.12 06/78] net: qmi_wwan: add additional Sierra Wireless QMI devices

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9a793e71ebd6fc4a2649f33811589a9c4fe7f4e8 upstream. A set of new VID/PIDs retrieved from the out-of-tree GobiNet/GobiSerial Sierra Wireless

[PATCH 3.12 21/78] cdc_ncm: toggle altsetting to force reset before setup

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 48906f62c96cc2cd35753e59310cb70eb08cc6a5 ] Some devices will silently fail setup unless they are reset first. This is necessary even if the data interface is already

Re: [PATCH v10 1/2] perf config: Prepare all default configs

Hi, On 04/22/2016 07:21 PM, Taeung Song wrote: To precisely manage configs, prepare all default perf's configs that contain default section name, variable name, value and correct type, not string type. In the near future, this will be used when checking type of config variable or showing all

[PATCH 3.12 06/78] net: qmi_wwan: add additional Sierra Wireless QMI devices

From: Aleksander Morgado 3.12-stable review patch. If anyone has any objections, please let me know. === commit 9a793e71ebd6fc4a2649f33811589a9c4fe7f4e8 upstream. A set of new VID/PIDs retrieved from the out-of-tree GobiNet/GobiSerial Sierra Wireless drivers. Signed-off-by:

[PATCH 3.12 24/78] sh_eth: fix NULL pointer dereference in sh_eth_ring_format()

From: Sergei Shtylyov 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit c1b7fca65070bfadca94dd53a4e6b71cd4f69715 ] In a low memory situation, if netdev_alloc_skb() fails on a first RX ring loop

[PATCH 3.12 23/78] udp6: fix UDP/IPv6 encap resubmit path

From: Bill Sommerfeld 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 59dca1d8a6725a121dae6c452de0b2611d5865dc ] IPv4 interprets a negative return value from a protocol handler as a request to redispatch to

[PATCH 3.12 25/78] macvtap: always pass ethernet header in linear

From: Willem de Bruijn 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 8e2ad4113ce4671686740f808ff2795395c39eef ] The stack expects link layer headers in the skb linear section. Macvtap can create skbs with

[PATCH 3.12 01/78] tunnel: Clear IPCB(skb)->opt before dst_link_failure called

From: Bernie Harris 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 5146d1f151122e868e594c7b45115d64825aee5f ] IPCB may contain data from previous layers (in the observed case the qdisc layer).

[PATCH 3.12 24/78] sh_eth: fix NULL pointer dereference in sh_eth_ring_format()

From: Sergei Shtylyov 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit c1b7fca65070bfadca94dd53a4e6b71cd4f69715 ] In a low memory situation, if netdev_alloc_skb() fails on a first RX ring loop iteration in sh_eth_ring_format(),

[PATCH 3.12 23/78] udp6: fix UDP/IPv6 encap resubmit path

From: Bill Sommerfeld 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 59dca1d8a6725a121dae6c452de0b2611d5865dc ] IPv4 interprets a negative return value from a protocol handler as a request to redispatch to a new protocol. In

[PATCH 3.12 25/78] macvtap: always pass ethernet header in linear

From: Willem de Bruijn 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 8e2ad4113ce4671686740f808ff2795395c39eef ] The stack expects link layer headers in the skb linear section. Macvtap can create skbs with llheader in frags in

[PATCH 3.12 01/78] tunnel: Clear IPCB(skb)->opt before dst_link_failure called

From: Bernie Harris 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 5146d1f151122e868e594c7b45115d64825aee5f ] IPCB may contain data from previous layers (in the observed case the qdisc layer). In the observed scenario, the data

[PATCH V2 7/9] cpufreq: sunxi: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Maxime Ripard Cc: Chen-Yu Tsai Signed-off-by: Viresh Kumar Acked-by: Arnd

[PATCH V2 4/9] cpufreq: omap: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Tony Lindgren Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann ---

[PATCH V2 7/9] cpufreq: sunxi: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Maxime Ripard Cc: Chen-Yu Tsai Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- arch/arm/mach-sunxi/sunxi.c | 9 -

[PATCH V2 4/9] cpufreq: omap: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Tony Lindgren Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- arch/arm/mach-omap2/pm.c | 7 ++-

Re: [PATCH v7 01/10] iommu: Add DOMAIN_ATTR_MSI_MAPPING attribute

On 20/04/16 16:58, Eric Auger wrote: Hi Robin, On 04/20/2016 02:47 PM, Robin Murphy wrote: Hi Eric, On 19/04/16 17:56, Eric Auger wrote: Introduce a new DOMAIN_ATTR_MSI_MAPPING domain attribute. If supported, this means the MSI addresses need to be mapped in the IOMMU. x86 IOMMUs typically

[PATCH V2 2/9] cpufreq: berlin: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Sebastian Hesselbarth Signed-off-by: Viresh Kumar Acked-by: Antoine Tenart

[PATCH V2 2/9] cpufreq: berlin: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Sebastian Hesselbarth Signed-off-by: Viresh Kumar Acked-by: Antoine Tenart Acked-by: Arnd Bergmann --- arch/arm/mach-berlin/berlin.c| 6 --

Re: [PATCH v7 01/10] iommu: Add DOMAIN_ATTR_MSI_MAPPING attribute

On 20/04/16 16:58, Eric Auger wrote: Hi Robin, On 04/20/2016 02:47 PM, Robin Murphy wrote: Hi Eric, On 19/04/16 17:56, Eric Auger wrote: Introduce a new DOMAIN_ATTR_MSI_MAPPING domain attribute. If supported, this means the MSI addresses need to be mapped in the IOMMU. x86 IOMMUs typically

[PATCH V2 5/9] cpufreq: rockchip: Use generic platdev driver

From: Finley Xiao This patch add rockchip's compatible string to the compat list and remove similar code from platform code for supporting generic platdev driver. Signed-off-by: Finley Xiao Acked-by: Viresh Kumar

[PATCH V2 3/9] cpufreq: imx: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Note that the complete routine imx27_dt_init() is removed as of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); has same effect as a NULL

[PATCH V2 5/9] cpufreq: rockchip: Use generic platdev driver

From: Finley Xiao This patch add rockchip's compatible string to the compat list and remove similar code from platform code for supporting generic platdev driver. Signed-off-by: Finley Xiao Acked-by: Viresh Kumar Acked-by: Arnd Bergmann Signed-off-by: Viresh Kumar ---

[PATCH V2 3/9] cpufreq: imx: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Note that the complete routine imx27_dt_init() is removed as of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); has same effect as a NULL

[PATCH V2 8/9] cpufreq: zynq: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Michal Simek Cc: Sören Brinkmann Signed-off-by: Viresh Kumar Acked-by:

[PATCH V2 9/9] cpufreq: hisilicon: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Leo Yan Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- drivers/cpufreq/Kconfig.arm

[PATCH V2 1/9] cpufreq: dt: Mark platdev machines array as __initconst

The machines array in cpufreq-dt-platdev is used only once at boot time and so should be marked with __initconst, so that kernel can free up memory used for it, if required. Suggested-by: Geert Uytterhoeven Signed-off-by: Viresh Kumar ---

[PATCH V2 8/9] cpufreq: zynq: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Michal Simek Cc: Sören Brinkmann Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- arch/arm/mach-zynq/common.c | 2 --

[PATCH V2 9/9] cpufreq: hisilicon: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Leo Yan Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- drivers/cpufreq/Kconfig.arm | 9 drivers/cpufreq/Makefile

[PATCH V2 1/9] cpufreq: dt: Mark platdev machines array as __initconst

The machines array in cpufreq-dt-platdev is used only once at boot time and so should be marked with __initconst, so that kernel can free up memory used for it, if required. Suggested-by: Geert Uytterhoeven Signed-off-by: Viresh Kumar --- drivers/cpufreq/cpufreq-dt-platdev.c | 2 +- 1 file

[PATCH V2 6/9] cpufreq: shmobile: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Simon Horman Cc: Magnus Damm Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann

[PATCH 3.12 26/78] net: Fix use after free in the recvmmsg exit path

From: Arnaldo Carvalho de Melo 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 34b88a68f26a75e4fded796f1a49c40f82234b7d ] The syzkaller fuzzer hit the following use-after-free: Call Trace: []

[PATCH 3.12 26/78] net: Fix use after free in the recvmmsg exit path

From: Arnaldo Carvalho de Melo 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit 34b88a68f26a75e4fded796f1a49c40f82234b7d ] The syzkaller fuzzer hit the following use-after-free: Call Trace: []

[PATCH V2 6/9] cpufreq: shmobile: Use generic platdev driver

The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Cc: Simon Horman Cc: Magnus Damm Signed-off-by: Viresh Kumar Acked-by: Arnd Bergmann --- arch/arm/mach-shmobile/Makefile | 1 -

[PATCH 3.12 17/78] qmi_wwan: add Sierra Wireless EM74xx device ID

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit bf13c94ccb33c3182efc92ce4989506a0f541243 upstream. The MC74xx and EM74xx modules use different IDs by default, according to the Lenovo EM7455 driver for Windows.

[PATCH 3.12 17/78] qmi_wwan: add Sierra Wireless EM74xx device ID

From: Bjørn Mork 3.12-stable review patch. If anyone has any objections, please let me know. === commit bf13c94ccb33c3182efc92ce4989506a0f541243 upstream. The MC74xx and EM74xx modules use different IDs by default, according to the Lenovo EM7455 driver for Windows.

[PATCH 3.12 27/78] mlx4: add missing braces in verify_qp_parameters

From: Arnd Bergmann 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit baefd7015cdb304ce6c94f9679d0486c71954766 ] The implementation of QP paravirtualization back in linux-3.7 included some code that looks very

[PATCH 3.12 28/78] farsync: fix off-by-one bug in fst_add_one

From: Arnd Bergmann 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit e725a66c0202b5f36c2f9d59d26a65c53bbf21f7 ] gcc-6 finds an out of bounds access in the fst_add_one function when calculating the end of the mmio

[PATCH 3.12 27/78] mlx4: add missing braces in verify_qp_parameters

From: Arnd Bergmann 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit baefd7015cdb304ce6c94f9679d0486c71954766 ] The implementation of QP paravirtualization back in linux-3.7 included some code that looks very dubious, and gcc-6 has

[PATCH 3.12 28/78] farsync: fix off-by-one bug in fst_add_one

From: Arnd Bergmann 3.12-stable review patch. If anyone has any objections, please let me know. === [ Upstream commit e725a66c0202b5f36c2f9d59d26a65c53bbf21f7 ] gcc-6 finds an out of bounds access in the fst_add_one function when calculating the end of the mmio area:

Re: [PATCH 4/5] regulator: core: Add early supply resolution for a bypassed regulator

On 22/04/16 11:48, Mark Brown wrote: > * PGP Signed by an unknown key > > On Thu, Apr 21, 2016 at 05:12:00PM +0100, Jon Hunter wrote: > >> A regulator that is in bypass will fail to be registered because we will >> attempt to get the voltage of the regulator (ie. it's bypass voltage) >> before

[PATCH v4 3/5] irqchip/gic: Restore CPU interface checking

From: Marc Zyngier When introducing the whole CPU feature detection framework, we lost the capability to detect a mismatched GIC configuration (using the GICv2 MMIO interface, but having the system register interface enabled). In order to solve this, use the new

[PATCH v4 2/5] arm64: Allow a capability to be checked on a single CPU

From: Marc Zyngier Now that the capabilities are only available once all the CPUs have booted, we're unable to check for a particular feature in any subsystem that gets initialized before then. In order to support this, introduce a local_cpu_has_cap() function that tests

Re: [PATCH 4/5] regulator: core: Add early supply resolution for a bypassed regulator

On 22/04/16 11:48, Mark Brown wrote: > * PGP Signed by an unknown key > > On Thu, Apr 21, 2016 at 05:12:00PM +0100, Jon Hunter wrote: > >> A regulator that is in bypass will fail to be registered because we will >> attempt to get the voltage of the regulator (ie. it's bypass voltage) >> before

[PATCH v4 3/5] irqchip/gic: Restore CPU interface checking

From: Marc Zyngier When introducing the whole CPU feature detection framework, we lost the capability to detect a mismatched GIC configuration (using the GICv2 MMIO interface, but having the system register interface enabled). In order to solve this, use the new this_cpu_has_cap() helper. Also

[PATCH v4 2/5] arm64: Allow a capability to be checked on a single CPU

From: Marc Zyngier Now that the capabilities are only available once all the CPUs have booted, we're unable to check for a particular feature in any subsystem that gets initialized before then. In order to support this, introduce a local_cpu_has_cap() function that tests for the presence of a

[PATCH v8] Bluetooth: hci_uart: Support firmware download for Marvell

From: Ganapathi Bhat This patch implement firmware download feature for Marvell Bluetooth devices. If firmware is already downloaded, it will skip downloading. Signed-off-by: Ganapathi Bhat Signed-off-by: Amitkumar Karwar --- v2:

[PATCH v8] Bluetooth: hci_uart: Support firmware download for Marvell

From: Ganapathi Bhat This patch implement firmware download feature for Marvell Bluetooth devices. If firmware is already downloaded, it will skip downloading. Signed-off-by: Ganapathi Bhat Signed-off-by: Amitkumar Karwar --- v2: Fixed compilation warning reported by kbuild test robot v3:

[PATCH v4 1/5] arm64: cpufeature: Add scope for capability check

Add scope parameter to the arm64_cpu_capabilities::matches(), so that this can be reused for checking the capability on a given CPU vs the system wide. The system uses the default scope associated with the capability for initialising the CPU_HWCAPs and ELF_HWCAPs. Cc: James Morse

[PATCH v4 0/5] arm64: Fix behavior of maxcpus=n

This series is an attempt at fixing the maxcpus=n behavior on arm64. So far we have disabled hotplugging a CPU > n, when maxcpus=n is in effect, due to following reasons. 1) Possible cpu feature incompatibilities with the new CPU in heterogeneous systems. 2) New CPU requiring an errata work

[PATCH v4 5/5] arm64: Fix behavior of maxcpus=N

maxcpu=n sets the number of CPUs activated at boot time to a max of n, but allowing the remaining CPUs to be brought up later if the user decides to do so. However, on arm64 due to various reasons, we disallowed hotplugging CPUs beyond n, by marking them not present. Now that we have checks in

[PATCH v4 5/5] arm64: Fix behavior of maxcpus=N

maxcpu=n sets the number of CPUs activated at boot time to a max of n, but allowing the remaining CPUs to be brought up later if the user decides to do so. However, on arm64 due to various reasons, we disallowed hotplugging CPUs beyond n, by marking them not present. Now that we have checks in

[PATCH v4 1/5] arm64: cpufeature: Add scope for capability check

Add scope parameter to the arm64_cpu_capabilities::matches(), so that this can be reused for checking the capability on a given CPU vs the system wide. The system uses the default scope associated with the capability for initialising the CPU_HWCAPs and ELF_HWCAPs. Cc: James Morse Cc: Marc

[PATCH v4 0/5] arm64: Fix behavior of maxcpus=n

This series is an attempt at fixing the maxcpus=n behavior on arm64. So far we have disabled hotplugging a CPU > n, when maxcpus=n is in effect, due to following reasons. 1) Possible cpu feature incompatibilities with the new CPU in heterogeneous systems. 2) New CPU requiring an errata work

<    6   7   8   9   10   11   12   13   14   15   >