Re: [PATCH v2 2/2] regmap: soundwire: fix Kconfig select/depend issue

2019-04-21 Thread Vinod Koul
On 19-04-19, 14:46, Pierre-Louis Bossart wrote: > The mechanism should be > > config CODEC_XYX_SDW >depends on SOUNDWIRE >select REGMAP_SOUNDWIRE > > config REGMAP_SOUNDWIRE >select SOUNDWIRE_BUS > > SOUNDWIRE_BUS can be independently selected by the SOC driver. The SOC >

[PATCH] ASoC: DA7219: Fix failure in hw_params by not letting set_rate error out

2019-04-21 Thread Agrawal, Akshu
We need to set minimum bclk 64x of wclk as this is hw constraint in one of the component used. Since, clk_set_rate and clk is enabled in machine driver the clk_set_rate in hw_params of da7219 fails and errors out and when it tries to override the value. In cases like these not only clk_set_rate of

Build regressions/improvements in v5.1-rc6

2019-04-21 Thread Geert Uytterhoeven
Below is the list of build error/warning regressions/improvements in v5.1-rc6[1] compared to v5.0[2]. Summarized: - build errors: +1/-1 - build warnings: +138/-108 JFYI, when comparing v5.1-rc6[1] to v5.1-rc5[3], the summaries are: - build errors: +0/-0 - build warnings: +62/-63 Happy fi

[PATCH 0/1] Forced-wakeup for stop lite states on Powernv

2019-04-21 Thread Abhishek Goel
Currently, the cpuidle governors determine what idle state a idling CPU should enter into based on heuristics that depend on the idle history on that CPU. Given that no predictive heuristic is perfect, there are cases where the governor predicts a shallow idle state, hoping that the CPU will be bus

[PATCH 1/1] cpuidle-powernv : forced wakeup for stop lite states

2019-04-21 Thread Abhishek Goel
Currently, the cpuidle governors determine what idle state a idling CPU should enter into based on heuristics that depend on the idle history on that CPU. Given that no predictive heuristic is perfect, there are cases where the governor predicts a shallow idle state, hoping that the CPU will be bus

[PATCH] KVM: x86: Add Intel CPUID.1F cpuid emulation support

2019-04-21 Thread Like Xu
Expose Intel V2 Extended Topology Enumeration Leaf to guest only when host system has multiple software-visible die within each package. Signed-off-by: Like Xu --- arch/x86/kvm/cpuid.c | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c

[PATCH 2/3] ntb_hw_switchtec: Skip unnecessary re-setup of shared memory window for crosslink case

2019-04-21 Thread Wesley Sheng
In case of NTB crosslink topology, the setting of shared memory window in the virtual partition doesn't reset on peer's reboot. So skip the unnecessary re-setup of shared memory window for that case. Signed-off-by: Wesley Sheng Reviewed-by: Logan Gunthorpe --- drivers/ntb/hw/mscc/ntb_hw_switcht

[PATCH 3/3] ntb_hw_switchtec: Fix setup MW with failure bug

2019-04-21 Thread Wesley Sheng
From: Joey Zhang Switchtec does not support setting multiple MWs simultaneously. The driver takes a hardware lock to ensure that two peers are not doing this simultaneously and it fails if someone else takes the lock. In most cases, this is fine as clients only setup the MWs once on one side of

[PATCH 0/3] Redundant steps removal and bug fix of ntb_hw_switchtec

2019-04-21 Thread Wesley Sheng
Hi, Everyone, This patch series remove redundant steps and fix one bug of the ntb_hw_switchtec module. When a re-initialization is caused by a link event, the driver will re-setup the shared memory windows. But at that time, the shared memory is still valid, and it's unnecessary to free, realloc

[PATCH 1/3] ntb_hw_switchtec: Remove redundant steps of switchtec_ntb_reinit_peer() function

2019-04-21 Thread Wesley Sheng
From: Joey Zhang When a re-initialization is caused by a link event, the driver will re-setup the shared memory window. But at that time, the shared memory is still valid, and it's unnecessary to free, reallocate and then initialize it again. We only need to reconfigure the hardware registers. Re

RE: [PATCH 1/2] soc: imx-sc: add i.MX system controller soc driver support

2019-04-21 Thread Anson Huang
Hi, Shawn Best Regards! Anson Huang > -Original Message- > From: Anson Huang > Sent: Monday, April 22, 2019 8:52 AM > To: Shawn Guo > Cc: stefan.wah...@i2se.com; enric.balle...@collabora.com; linux- > ker...@vger.kernel.org; he...@sntech.de; marc.w.gonza...@free.fr; > ezequ...@collabora.

Re: [PATCH 1/2] arm64: dts: imx8mm: Add SAI nodes

2019-04-21 Thread Daniel Baluta
On Mon, Apr 22, 2019 at 5:45 AM Shawn Guo wrote: > > On Fri, Apr 19, 2019 at 08:20:39PM +, Daniel Baluta wrote: > > i.MX8MM has 5 SAI instances with the following base > > addresses according to RM. > > > > SAI1 base address: 3001_h > > SAI2 base address: 3002_h > > SAI3 base address:

[PATCH v2] signal: trace_signal_deliver when signal_group_exit

2019-04-21 Thread Zhenliang Wei
In the following commit, removing SIGKILL from each thread signal mask and executing "goto fatal" directly will skip the call to "trace_signal_deliver". At this point, the delivery tracking of the SIGKILL signal will be inaccurate. commit cf43a757fd4944 ("signal: Restore the stop PTRACE_EVENT_EXIT

[PATCH] HID: i2c-hid: add iBall Aer3 to descriptor override

2019-04-21 Thread Kai-Heng Feng
This device uses the SIPODEV SP1064 touchpad, which does not supply descriptors, so it has to be added to the override list. BugLink: https://bugs.launchpad.net/bugs/1825718 Signed-off-by: Kai-Heng Feng --- drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 8 1 file changed, 8 insertions(+) d

<    1   2