From: Jérôme Pouiller
These files are shared with firmware sources. Only a subset of these
definitions are used by driver but, for now, it is easier to import all.
API defines 3 kinds of messages:
- Requests (req) are sent from host to chip
- Confirmations (cnf) are sent by chip and are al
From: Jérôme Pouiller
Signed-off-by: Jérôme Pouiller
---
drivers/staging/wfx/data_rx.c | 26 +
drivers/staging/wfx/data_tx.c | 16 +
drivers/staging/wfx/debug.c |2 +
drivers/staging/wfx/hif_rx.c | 53 ++
drivers/staging/wfx/hif_tx.c |1 +
drivers/staging/wfx/main.c| 137
From: Jérôme Pouiller
bh_work() is in charge to schedule all HIF message from/to chip.
On normal operation, when an IRQ is received, driver can get size of
next message in control register. In order to save control register
access, when chip send a message, it also appends a copy of control
regi
On Wed, Sep 18, 2019 at 01:10:04PM -0700, Vineet Gupta wrote:
> On 9/18/19 11:56 AM, Greg Kroah-Hartman wrote:
> > So is this only needed in 4.9.y and 4.4.y?
>
> Yes indeed !
It doesn't apply there at all, can you provide a working backport for
those kernels so that I can queue it up?
thanks,
g
From: Jérôme Pouiller
Allocate a struct ieee80211_hw but do not yet register it.
Signed-off-by: Jérôme Pouiller
---
drivers/staging/wfx/Makefile | 1 +
drivers/staging/wfx/debug.c | 12 ++
drivers/staging/wfx/debug.h | 15
drivers/staging/wfx/main.c | 41 +
From: Jérôme Pouiller
Some tracepoints are useful for debugging.
Signed-off-by: Jérôme Pouiller
---
drivers/staging/wfx/Makefile | 6 +-
drivers/staging/wfx/debug.c | 10 +++
drivers/staging/wfx/hwio.c | 11 +++
drivers/staging/wfx/traces.h | 154 +++
4 f
From: Jérôme Pouiller
Introduce bus level communication layer. At this level, 7 registers can
be addressed.
Notice that SPI driver is able to manage chip reset. SDIO mode relies
on an external driver (`mmc-pwrseq`) to reset chip.
Signed-off-by: Jérôme Pouiller
---
drivers/staging/wfx/bus.h
From: Jérôme Pouiller
Provide an abstraction for HIF commands.
Signed-off-by: Jérôme Pouiller
---
drivers/staging/wfx/hif_tx.c | 375 +++
drivers/staging/wfx/hif_tx.h | 33 +++
drivers/staging/wfx/hif_tx_mib.h | 281 +++
drivers/staging/
From: Jérôme Pouiller
A few tasks remain to be done in order to finish chip initial
configuration:
- configure chip to use multi-tx confirmation (speed up data
transfer)
- configure chip to use wake-up feature (save power consumption
during runtime)
- set hardware configuration
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Paul Walmsley
> Sent: Thursday, September 19, 2019 3:56 PM
> To: Xiang Wang
> Cc: pal...@sifive.com; a...@eecs.berkeley.edu; linux-
> ri...@lists.infradead.org; linux-kernel@vger.kernel.
On Tue 2019-09-17 19:19:55, Guido Günther wrote:
> The driver currently reports successful initialization on every failure
> as long as it's able to power off the regulator. Don't check the return
> value of regulator_disable to avoid that.
>
> Signed-off-by: Guido Günther
> ---
> drivers/leds/l
On Thu, Sep 19, 2019 at 06:48:32PM +0800, Kyle Tso wrote:
> Ping! Anyone still reviewing this patch?
> I have another change related to AMS.
> I will group them as a set and re-send it.
Please rebase resend the patch. It does not apply any more.
thanks,
--
heikki
On 19/09/19 11:46, Jianyong Wu (Arm Technology China) wrote:
>> On 18/09/19 11:57, Jianyong Wu (Arm Technology China) wrote:
>>> Paolo Bonzini wrote:
This is not Y2038-safe. Please use ktime_get_real_ts64 instead, and
split the 64-bit seconds value between val[0] and val[1].
>
> Val[] sh
[]..
+static struct clk_rcg_dfs_data gcc_dfs_clocks[] = {
+ DEFINE_RCG_DFS(gcc_qupv3_wrap0_s0_clk_src),
+ DEFINE_RCG_DFS(gcc_qupv3_wrap0_s1_clk_src),
+ DEFINE_RCG_DFS(gcc_qupv3_wrap0_s2_clk_src),
+ DEFINE_RCG_DFS(gcc_qupv3_wrap0_s3_clk_src),
+ DEFINE_RCG_DFS(gcc_qup
On Thu, 19 Sep 2019, Anup Patel wrote:
> > From: Xiang Wang
> > Date: Fri, 6 Sep 2019 11:56:09 +0800
> > Subject: [PATCH] arch/riscv: disable excess harts before picking main boot
> > hart
> >
> > Harts with id greater than or equal to CONFIG_NR_CPUS need to be
> > disabled. But the kernel can
On Thu, Sep 19, 2019 at 11:17:27AM +0200, Rasmus Villemoes wrote:
> The way state->enabled is computed is rather convoluted and hard to
> read - both branches of the if() actually do the exact same thing. So
> remove the if(), and further simplify " ? true :
> false" to "".
>
> Signed-off-by: Rasm
From: Linus Torvalds
Date: Wed, 18 Sep 2019 13:37:57 -0700
> Hmm. This adds that NET_TC_SKB_EXT config thing, and makes it "default y".
>
> Why?
>
> It's also done in a crazy way:
>
> + depends on NET_CLS_ACT
> + default y if NET_CLS_ACT
I agree.
I've asked Paul Blakey, who added
On Thu, 2019-09-05 at 16:01 +0200, Vincent Guittot wrote:
> Hi Jing-Ting,
>
> On Thu, 5 Sep 2019 at 15:26, Jing-Ting Wu wrote:
> >
> > On Fri, 2019-08-30 at 15:55 +0100, Qais Yousef wrote:
> > > On 08/29/19 11:38, Valentin Schneider wrote:
> > > > On 29/08/2019 04:15, Jing-Ting Wu wrote:
> > > >
Hi Mark,
On 29/08/2019 17:35, Srinivas Kandagatla wrote:
This patch adds bindings for WSA8810/WSA8815 Class-D Smart Speaker
Amplifier. This Amplifier also has a simple thermal sensor for
over temperature and speaker protection.
Signed-off-by: Srinivas Kandagatla
Bindings for the codec have b
On Thu, Sep 19, 2019 at 12:26:28PM +0200, Philipp Puschmann wrote:
> Using only 4 DMA periods for UART RX is very few if we have a high
> frequency of small transfers - like in our case using Bluetooth with
> many small packets via UART - causing many dma transfers but in each
> only filling a frac
On 9/16/2019 6:22 PM, Gustavo Pimentel wrote:
On Mon, Sep 16, 2019 at 13:24:1, Andrew Murray
wrote:
On Mon, Sep 16, 2019 at 04:36:33PM +0530, Pankaj Dubey wrote:
-Original Message-
From: Andrew Murray
Sent: Monday, September 16, 2019 3:46 PM
To: Pankaj Dubey
Cc: linux-...@vger.ke
On Thu, Sep 19, 2019 at 10:52:34AM +, Jerome Pouiller wrote:
> From: Jérôme Pouiller
>
> Hello all,
>
> This series add support for Silicon Labs WiFi chip WF200 and further:
>
>https://www.silabs.com/documents/public/data-sheets/wf200-datasheet.pdf
>
> This driver is an export from:
>
On Thu, Sep 19, 2019 at 11:10:14AM +0200, Miquel Raynal wrote:
> Hi Markus,
>
> Markus Elfring wrote on Wed, 18 Sep 2019
> 14:50:27 +0200:
>
> > From: Markus Elfring
> > Date: Wed, 18 Sep 2019 14:37:34 +0200
> >
> > Simplify this function implementation by using a known wrapper function.
> >
Hi all,
Today's linux-next merge of the btrfs-kdave tree got conflicts in:
fs/btrfs/block-group.c
fs/btrfs/ctree.h
fs/btrfs/extent-tree.c
fs/btrfs/send.c
fs/btrfs/space-info.c
include/uapi/linux/btrfs_tree.h
between a number of commits in Linus' tree and a number of commits in
the bt
As we are in the merge window, the net-next tree is closed, as shown
also at:
http://vger.kernel.org/~davem/net-next.html
Please resubmit this after the merge window when the net-next tree opens
back up.
Please also provide an appropriate "[PATCH 0/N]" header posting
explaining what th
On 2019/9/19 8:30, Wei Yang wrote:
> On Wed, Sep 18, 2019 at 03:08:41PM +0800, Yunfeng Ye wrote:
>>
>>
>> On 2019/9/18 14:51, Wei Yang wrote:
>>> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote:
Currently, when memblock_find_in_range_node() fail on the exact node, it
will us
Hi Greg,
Greg Kroah-Hartman wrote on Thu, 19 Sep
2019 13:29:37 +0200:
> On Thu, Sep 19, 2019 at 11:10:14AM +0200, Miquel Raynal wrote:
> > Hi Markus,
> >
> > Markus Elfring wrote on Wed, 18 Sep 2019
> > 14:50:27 +0200:
> >
> > > From: Markus Elfring
> > > Date: Wed, 18 Sep 2019 14:37:34 +0
On Thu, Sep 19, 2019 at 11:59:11AM +0200, Alexander Gordeev wrote:
> The Avalon-MM DMA Interface for PCIe is a design found in hard IPs for
> Intel Arria, Cyclone or Stratix FPGAs. It transfers data between on-chip
> memory and system memory. This RFC is an attempt to provide a generic API:
>
>
Hi Philipp,
On Thu, Sep 19, 2019 at 7:45 AM Philipp Puschmann
wrote:
>
> BD_DONE flag marks ownership of the buffer. When 1 SDMA owns the
> buffer, when 0 ARM owns it. When processing the buffers in
> sdma_update_channel_loop the ownership of the currently processed
> buffer was set to SDMA again
On 19/09/2019 12:07, Paolo Bonzini wrote:
> On 19/09/19 11:46, Jianyong Wu (Arm Technology China) wrote:
>>> On 18/09/19 11:57, Jianyong Wu (Arm Technology China) wrote:
Paolo Bonzini wrote:
> This is not Y2038-safe. Please use ktime_get_real_ts64 instead, and
> split the 64-bit secon
On 9/19/2019 1:25 PM, Greg Kroah-Hartman wrote:
- I also kept compatibility code for earlier Linux kernel version. I
may drop it in future. Maybe I will maintain compatibility with
older kernels in a external set of patches.
That has to be dropped for the in-kernel version.
There
Make code more readable by using macros defined for initializing
struct resource
Signed-off-by: Aurabindo Jayamohanan
---
drivers/staging/board/armadillo800eva.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/board/armadillo800eva.c
b/drivers/s
Hi Uwe
Am 19.09.19 um 13:22 schrieb Uwe Kleine-König:
> On Thu, Sep 19, 2019 at 12:26:28PM +0200, Philipp Puschmann wrote:
>> Using only 4 DMA periods for UART RX is very few if we have a high
>> frequency of small transfers - like in our case using Bluetooth with
>> many small packets via UART -
Hi Fabio,
Am 19.09.19 um 13:37 schrieb Fabio Estevam:
> Hi Philipp,
>
> On Thu, Sep 19, 2019 at 7:45 AM Philipp Puschmann
> wrote:
>>
>> BD_DONE flag marks ownership of the buffer. When 1 SDMA owns the
>> buffer, when 0 ARM owns it. When processing the buffers in
>> sdma_update_channel_loop the
On 2019/9/19 17:28, Mike Rapoport wrote:
> On Thu, Sep 19, 2019 at 03:14:22PM +0800, Yunfeng Ye wrote:
>>
>>
>> On 2019/9/19 12:47, Mike Rapoport wrote:
>>> Hi,
>>>
>>> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote:
Currently, when memblock_find_in_range_node() fail on the exac
Hi all,
Today's linux-next merge of the ext4 tree got a conflict in:
fs/ext4/ioctl.c
between commit:
29b3692e6dbf8226 ("ext4: wire up new fscrypt ioctls")
from Linus' tree and commits:
bb5835edcdf8bf7 ("ext4: add new ioctl EXT4_IOC_GET_ES_CACHE")
1ad3ea6e0a694b0 ("ext4: add a new ioct
The iwl_mvm_send_temp_report_ths_cmd() function is now called without
CONFIG_THERMAL, but not defined:
ERROR: "iwl_mvm_send_temp_report_ths_cmd"
[drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko] undefined!
Move that function out of the #ifdef as well and change it so
that empty data gets sent e
This does correct the sequence of switching to HS400 but it might be
safest to just add this to the latest until it gets a little testing
to make sure it doesn't expose some bug in existing controllers.
Thanks
Al
On Tue, Sep 3, 2019 at 10:52 AM Ulf Hansson wrote:
>
> On Tue, 3 Sep 2019 at 13:51,
On Thu, 2019-09-19 at 13:55 +0200, Arnd Bergmann wrote:
> The iwl_mvm_send_temp_report_ths_cmd() function is now called without
> CONFIG_THERMAL, but not defined:
>
> ERROR: "iwl_mvm_send_temp_report_ths_cmd"
> [drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko] undefined!
>
> Move that function
On Thu, Sep 19, 2019 at 01:40:03PM +0200, Philipp Puschmann wrote:
> Hi Uwe
>
> Am 19.09.19 um 13:22 schrieb Uwe Kleine-König:
> > On Thu, Sep 19, 2019 at 12:26:28PM +0200, Philipp Puschmann wrote:
> >> Using only 4 DMA periods for UART RX is very few if we have a high
> >> frequency of small tran
From: Markus Elfring
Date: Thu, 19 Sep 2019 13:30:51 +0200
Simplify this function implementation by using a known wrapper function.
* Thus reduce also a bit of exception handling code.
* Delete the local variable “res”.
This issue was detected by using the Coccinelle software.
Signed-off-by: Ma
On Wed, 18 Sep 2019, Mike Kravetz wrote:
A new clang diagnostic (-Wsizeof-array-div) warns about the calculation
to determine the number of u32's in an array of unsigned longs. Suppress
warning by adding parentheses.
While looking at the above issue, noticed that the 'address' parameter
to huge
On Thu, Sep 19, 2019 at 7:19 AM Dexuan Cui wrote:
>
> If CONFIG_PM is not set, we can comment out these functions to avoid the
> below warnings:
>
> drivers/hv/vmbus_drv.c:2208:12: warning: ‘vmbus_bus_resume’ defined but not
> used [-Wunused-function]
> drivers/hv/vmbus_drv.c:2128:12: warning: ‘v
This patchset introduces a "Secure Power Doamin Controller". In A1/C1, power
controller registers such as PWRCTRL_FOCRSTN, PWRCTRL_PWR_OFF, PWRCTRL_MEM_PD
and PWRCTRL_ISO_EN, are in the secure domain, and should be accessed from ATF
by smc.
This patchset is based on A1 DTB series at [0].
[0]
ht
The below calltrace was reported, the cause is that timer is delayed
bigger than 3 seconds
Hardware name: New H3C Technologies Co.,Ltd. UniServer R4950 G3/RS41R4950,
BIOS 2.00.06 V700R003
Workqueue: events_unbound sched_tick_remote
RIP: 0010:sched_tick_remote+0xee/0x100
...
Ca
Enable power domain controller for Meson A1 SoC.
Signed-off-by: Jianxin Pan
Signed-off-by: Zhiqiang Liang
---
arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-a1.dtsi
b/arch/arm64/boot/dts/amlogic/meson-a1.dts
Add the bindings for the Amlogic Secure power domains, controlling the
secure power domains.
The bindings targets the Amlogic A1 and C1 compatible SoCs, in which the
power domain registers are in secure world.
Signed-off-by: Jianxin Pan
Signed-off-by: Zhiqiang Liang
---
.../bindings/power/amlo
Add support for the Amlogic Secure Power controller. In A1/C1 series, power
control registers are in secure domain, and should be accessed by smc.
Signed-off-by: Jianxin Pan
Signed-off-by: Zhiqiang Liang
---
drivers/soc/amlogic/Kconfig | 13 +++
drivers/soc/amlogic/Makefile
The disconnect callback was accessing the hardware-descriptor private
data after having having freed it.
Fixes: 7490b008d123 ("ieee802154: add support for atusb transceiver")
Cc: stable # 4.2
Cc: Alexander Aring
Reported-by: syzbot+f4509a9138a1472e7...@syzkaller.appspotmail.com
Signed-off-by
snd_pcm_format_t is more formal than enum asrc_word_width, which has
two property, width and physical width, which is more accurate than
enum asrc_word_width. So it is better to use in(out)put_format
instead of in(out)put_word_width.
Signed-off-by: Shengjiu Wang
Acked-by: Nicolin Chen
---
sound
The ASRC support 24bit/16bit/8bit input width, which is
data width, not slot width.
For the S20_3LE format, the data with is 20bit, slot width
is 24bit, if we set ASRMCR1n.IWD to be 24bits, the result
is the volume is lower than expected, it likes 24bit data
right shift 4 bits
So replace S20_3LE
On 19/09/19 13:39, Marc Zyngier wrote:
>> I don't think it's ugly but more important, using tk->tkr_mono.clock is
>> incorrect. See how the x86 code hardcodes &kvm_clock, it's the same for
>> ARM.
> Not really. The guest kernel is free to use any clocksource it wishes.
Understood, in fact it's th
This patch serial is to update the supported format for fsl_asrc
and fix some format issue.
Shengjiu Wang (4):
ASoC: fsl_asrc: Use in(out)put_format instead of in(out)put_word_width
ASoC: fsl_asrc: update supported sample format
ASoC: pcm_dmaengine: Extract snd_dmaengine_pcm_refine_runtime_h
When set the runtime hardware parameters, we may need to query
the capability of DMA to complete the parameters.
This patch is to Extract this operation from
dmaengine_pcm_set_runtime_hwparams function to a separate function
snd_dmaengine_pcm_refine_runtime_hwparams, that other components
which ne
There is error "aplay: pcm_write:2023: write error: Input/output error"
on i.MX8QM/i.MX8QXP platform for S24_3LE format.
In i.MX8QM/i.MX8QXP, the DMA is EDMA, which don't support 24bit
sample, but we didn't add any constraint, that cause issues.
So we need to query the caps of dma, then update th
> Oh right... Sure, I'll ignore it/him as well.
I hope that you will still care for further possible software improvements
because of presented transformation results around collateral evolution.
Regards,
Markus
On Thu, 19 Sep 2019 at 13:22, Jing-Ting Wu wrote:
>
> On Thu, 2019-09-05 at 16:01 +0200, Vincent Guittot wrote:
> > Hi Jing-Ting,
> >
> > On Thu, 5 Sep 2019 at 15:26, Jing-Ting Wu wrote:
> > >
> > > On Fri, 2019-08-30 at 15:55 +0100, Qais Yousef wrote:
> > > > On 08/29/19 11:38, Valentin Schneide
On Thu, Sep 19, 2019 at 9:32 AM Marcel Holtmann wrote:
>
> > The btusb_rtl_cmd_timeout() function is used inside of an
> > ifdef, leading to a warning when this part is hidden
> > from the compiler:
> >
> > drivers/bluetooth/btusb.c:530:13: error: unused function
> > 'btusb_rtl_cmd_timeout' [-Wer
From: Bartosz Golaszewski
The region resource in struct stfsm is unused and can be removed.
Signed-off-by: Bartosz Golaszewski
---
drivers/mtd/devices/st_spi_fsm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices/st_spi_fsm.c
index f4d16
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+f4509a9138a1472e7...@syzkaller.appspotmail.com
Tested on:
commit: f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasa
> > By the time MT8183 shows up in more concrete devices, it will, certainly
> > in kernel-space and likely in userspace as well. At present, the DDK can
> > be modified to run on top of the in-tree Mali drivers, i.e. "Bifrost on
> > mainline linux-next (+ page table/compatible patches), with blob
Hi all,
Today's linux-next merge of the pci tree got a conflict in:
drivers/pci/controller/pci-hyperv.c
between commits:
348dd93e40c1 ("PCI: hv: Add a Hyper-V PCI interface driver for software
backchannel interface")
467a3bb97432 ("PCI: hv: Allocate a named fwnode instead of an address-b
Putting a struct stmmac_rss object on the stack is a bad idea,
as it exceeds the warning limit for a stack frame on 32-bit architectures:
drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c:1221:12: error: stack
frame size of 1208 bytes in function '__stmmac_test_l3filt'
[-Werror,-Wframe-larg
On Thu, Sep 19, 2019 at 9:58 AM Jose Abreu wrote:
>
> From: Arnd Bergmann
> Date: Sep/18/2019, 20:54:34 (UTC+00:00)
>
> > + if (!cfg || !cfg->enable) {
> > value &= ~XGMAC_RSSE;
> > writel(value, ioaddr + XGMAC_RSS_CTRL);
> > return 0;
> > }
> >
Hi Arnd,
>>> The btusb_rtl_cmd_timeout() function is used inside of an
>>> ifdef, leading to a warning when this part is hidden
>>> from the compiler:
>>>
>>> drivers/bluetooth/btusb.c:530:13: error: unused function
>>> 'btusb_rtl_cmd_timeout' [-Werror,-Wunused-function]
>>>
>>> Use an IS_ENABL
On Wed, 4 Sep 2019, Anup Patel wrote:
> We will be using ONE_REG interface accessing VCPU registers from
> user-space hence we add KVM_REG_RISCV for RISC-V VCPU registers.
>
> Signed-off-by: Anup Patel
> Acked-by: Paolo Bonzini
> Reviewed-by: Paolo Bonzini
> Reviewed-by: Alexander Graf
Thank
From: Roman Stratiienko
DE2.0 blender does not take into the account alpha channel of vi layer.
Thus makes overlaying of this layer totally opaque.
Using vi layer as bottom solves this issue.
Tested on Android.
Signed-off-by: Roman Stratiienko
---
drivers/gpu/drm/sun4i/sun8i_ui_layer.c | 33 -
On Wed, 4 Sep 2019, Anup Patel wrote:
> From: Atish Patra
>
> Export few symbols used by kvm module. Without this, kvm cannot
> be compiled as a module.
>
> Signed-off-by: Atish Patra
> Signed-off-by: Anup Patel
> Acked-by: Paolo Bonzini
> Reviewed-by: Paolo Bonzini
> Reviewed-by: Alexander
Change calculating of position page containing BBM
If none of BBM flags is set then function nand_bbm_get_next_page
reports EINVAL. It causes that BBM is not read at all during scanning
factory bad blocks. The result is that the BBT table is build without
checking factory BBM at all. For Micron
> -Original Message-
> From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com]
> Sent: 2019年9月19日 16:12
> To: zhangsha (A)
> Cc: vfal...@gmail.com; a...@greyhouse.net; da...@davemloft.net;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; yuehaibing
> ; hunongda ;
> Chenzhendong (al
On Thu, 5 Sep 2019, Bin Meng wrote:
> U-Boot expects this alias to be in place in order to fix up the mac
> address of the ethernet node.
>
> Signed-off-by: Bin Meng
Thanks, queued for v5.4-rc with Christoph's Reviewed-by.
- Paul
On Tue, Sep 17, 2019 at 03:10:21PM -0500, Josh Poimboeuf wrote:
> Then the "reverse alternatives" feature wouldn't be needed anyway.
The intent was to have the default, most-used version be there at
build-time, obviating the need to patch. Therefore on those old !ERMS
CPUs we'll end up doing rep;s
On Thu, 5 Sep 2019, Bin Meng wrote:
> The "clock-frequency" property of cpu nodes isn't required. Drop it.
>
> Signed-off-by: Bin Meng
Thanks, queued for v5.4-rc with Christoph's Reviewed-by:.
- Paul
On 2019/9/19 14:36, Greg KH wrote:
> On Thu, Sep 19, 2019 at 10:58:06AM +0800, Xiaoming Ni wrote:
>> Registering the same notifier to a hook repeatedly can cause the hook
>> list to form a ring or lose other members of the list.
>>
>> case1: An infinite loop in notifier_chain_register() can cause s
On Tue, Sep 17, 2019 at 01:45:20PM -0700, Linus Torvalds wrote:
> That sounds better, but I'm a bit nervous about the whole thing
> because who knows when the alternatives code itself internally uses
> memset() and then we have a nasty little chicken-and-egg problem.
You mean memcpy()...?
> Also,
Hi Paul,
On Wed, Sep 4, 2019 at 9:43 PM Anup Patel wrote:
>
> This patch adds riscv_isa bitmap which represents Host ISA features
> common across all Host CPUs. The riscv_isa is not same as elf_hwcap
> because elf_hwcap will only have ISA features relevant for user-space
> apps whereas riscv_isa
Hi Piotr,
Piotr Sroka wrote on Thu, 19 Sep 2019 13:41:35
+0100:
> Change calculating of position page containing BBM
>
> If none of BBM flags is set then function nand_bbm_get_next_page
> reports EINVAL. It causes that BBM is not read at all during scanning
> factory bad blocks. The result is
On Thu 19 Sep 2019 at 11:38, Neil Armstrong wrote:
> Make sure we always enable a PLL on a set_rate() when the PLL is
> flagged as critical.
>
> This fixes the case when the Amlogic G12A SYS_PLL gets disabled by the
> PSCI firmware when resuming from suspend-to-memory, in the case
> where the CPU
From: Arnd Bergmann
Date: Sep/19/2019, 13:33:43 (UTC+00:00)
> Putting a struct stmmac_rss object on the stack is a bad idea,
> as it exceeds the warning limit for a stack frame on 32-bit architectures:
>
> drivers/net/ethernet/stmicro/stmmac/stmmac_selftests.c:1221:12: error: stack
> frame size
On 04/09/2019 10.18, Jiri Slaby wrote:
On 29. 08. 19, 21:42, Martin Hundebøll wrote:
On 22/08/2019 23.56, Martin Hundebøll wrote:
When tearing down the n_gsm ldisc while one or more of its child ports
are open, a lock dep warning occurs:
[ 56.254258]
Hi,
On 31/8/19 1:14, Ravi Chandra Sadineni wrote:
> Mark chromeos_tbmc as wake capable and report wake events. This helps to
> abort suspend on seeing a tablet mode switch event when kernel is
> suspending. This also helps identifying if chroemos_tbmc is the wake
> source.
>
> Signed-off-by: Ravi
Hi,
On 4/9/19 8:26, Pi-Hsun Shih wrote:
> Since the rpmsg_endpoint is created before probe is called, it's
> possible that a host event is received during cros_ec_register, and
> there would be some pending work in the host_event_work workqueue while
> cros_ec_register is called.
>
> If cros_ec_r
The commit 5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h") introduced a
kbuild warning,
scripts/Makefile.asm-generic:25: redundant generic-y found in
arch/arm64/include/asm/Kbuild: dma-mapping.h
Hi,
On 5/9/19 23:25, Gwendal Grignou wrote:
> On Mon, Sep 2, 2019 at 9:24 AM Andy Shevchenko
> wrote:
>>
>> On Mon, Sep 02, 2019 at 06:08:48PM +0200, Enric Balletbo i Serra wrote:
>>> Allow to poll on the cros_ec device to receive the MKBP events.
>>>
>>> The /dev/cros_[ec|fp|..] file operations
Hi,
On 11/9/19 22:10, Navid Emamdoost wrote:
> In cros_usbpd_logger_probe the return value of
> create_singlethread_workqueue may be null, it should be checked.
>
> Signed-off-by: Navid Emamdoost
> ---
Applied for 5.4, the patch went to linux-next some time ago, so sorry for late
notice.
Thank
On Thu, Sep 19, 2019 at 10:24 AM Johan Hovold wrote:
>
> On Mon, Sep 16, 2019 at 06:29:12AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.gi
On 2019/9/18 下午10:32, Michael S. Tsirkin wrote:
So I have some questions:
1) Compared to method 2, what's the advantage of creating a new vhost char
device? I guess it's for keep the API compatibility?
One benefit is that we can avoid doing vhost ioctls on
VFIO device fd.
Yes, but any benefi
On 19.09.19 14:58, Miquel Raynal wrote:
> Hi Piotr,
>
> Piotr Sroka wrote on Thu, 19 Sep 2019 13:41:35
> +0100:
>
>> Change calculating of position page containing BBM
>>
>> If none of BBM flags is set then function nand_bbm_get_next_page
>> reports EINVAL. It causes that BBM is not read at all
On Thu, Sep 19, 2019 at 10:49:22AM +0100, David Howells wrote:
> David Howells wrote:
>
> > > However, I was close to unpulling it again. It has a merge commit with
> > > this merge message:
> > >
> > > Merge remote-tracking branch 'net/master' into afs-next
> > >
> > > and that simply is n
Hello,
Schrempf Frieder wrote on Thu, 19 Sep
2019 13:15:08 +:
> On 19.09.19 14:58, Miquel Raynal wrote:
> > Hi Piotr,
> >
> > Piotr Sroka wrote on Thu, 19 Sep 2019 13:41:35
> > +0100:
> >
> >> Change calculating of position page containing BBM
> >>
> >> If none of BBM flags is set then
From: Maciej Falkowski
Convert Samsung Exynos IOMMU H/W, System Memory Management Unit
to newer dt-schema format.
Signed-off-by: Maciej Falkowski
Signed-off-by: Andrzej Hajda
Signed-off-by: Marek Szyprowski
---
v4:
- Rename commit message to match common style
- Remove '"pclk", "aclk"' option
Hi,
We've come across the below lockdep report when using n_gsm multiplexing
on an imx uart.
The inverted lock scenario caused by:
1) the uart tx-ready interrupt causing the tty layer to call down
into n_gsm, and
2) n_gsm transmitting data, causing it to call up into the tty layer
We ha
On Wed, Sep 18, 2019 at 09:04:32AM +0100, Gareth Williams wrote:
> Gareth Williams (1):
> dt-bindings: snps,dw-apb-ssi: Add optional clock domain information
>
> Phil Edworthy (3):
> dt: spi: Add Renesas RZ/N1 binding documentation
Please use subject lines matching the style for the subsyste
On 9/19/19 3:48 AM, Kyle Tso wrote:
Ping! Anyone still reviewing this patch?
Which patch ? Hans' series was long since pushed.
Guenter
I have another change related to AMS.
I will group them as a set and re-send it.
Regards,
Kyle Tso
On Mon, Apr 15, 2019 at 6:03 PM Adam Thomson
wrote:
On Thu 19-09-19 21:13:32, Hillf Danton wrote:
>
> Currently memory controler is playing increasingly important role in
> how memory is used and how pages are reclaimed on memory pressure.
>
> In daily works memcg is often created for critical tasks and their pre
> configured memory usage is suppo
On Wed, 18 Sep 2019 10:47:48 +0200, Uwe =?iso-8859-1?Q?Kleine-K=F6nig?=
wrote:
> Before commit e42ee61017f5 ("of: Let of_for_each_phandle fallback to
> non-negative cell_count") the iterator functions calling
> of_for_each_phandle assumed a cell count of 0 if cells_name was NULL.
> This c
On 19.09.19 15:18, Miquel Raynal wrote:
> Hello,
>
> Schrempf Frieder wrote on Thu, 19 Sep
> 2019 13:15:08 +:
>
>> On 19.09.19 14:58, Miquel Raynal wrote:
>>> Hi Piotr,
>>>
>>> Piotr Sroka wrote on Thu, 19 Sep 2019 13:41:35
>>> +0100:
>>>
Change calculating of position page contain
On Fri, Sep 6, 2019 at 6:57 AM Roman Gushchin wrote:
> The patchset has been tested on a number of different workloads in our
> production. In all cases, it saved hefty amounts of memory:
> 1) web frontend, 650-700 Mb, ~42% of slab memory
> 2) database cache, 750-800 Mb, ~35% of slab memory
> 3) d
Currently when we're validating cpu on boot stage we assume that cpu level
won't ever be greater than two digits. In particular the check_cpu() helper
ensures to be so. Still the cpu_name() helper is a way too far from
check_cpu() routine internals so I think better to be on a safe side
and prevent
On 19/09/2019 15.27, Martin Hundebøll wrote:
But we haven't been able to reproduce locally.
Scratch that. It's reliably reproduced by sending/saturating the uart
with outgoing data.
// Martin
201 - 300 of 1297 matches
Mail list logo
