[PATCH V1 03/26] spi: tegra114: fix for unpacked mode transfers

Fixes: computation of actual bytes to fill/receive in/from FIFO in unpacked mode when transfer length is not a multiple of requested bits per word. unpacked mode transfers fails when the transfer includes partial bytes in the last word. Total words to be written/read to/from FIFO is computed

[PATCH V1 11/26] spi: tegra114: reset controller on probe

Fixes: SPI driver can be built as module so perform SPI controller reset on probe to make sure it is in valid state before initiating transfer. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 32 ++-- 1 file changed, 18 insertions(+), 14

[PATCH V1 06/26] spi: tegra114: terminate dma and reset on transfer timeout

Fixes: terminate DMA and perform controller reset on transfer timeout to clear the FIFO's and errors. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index

[PATCH V1 10/26] spi: tegra114: avoid reset call in atomic context

Fixes: move SPI controller reset out of spin lock. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index 268a790a663e..5523936b21f5 100644 ---

[PATCH V1 05/26] spi: tegra114: use unpacked mode for below 4 byte transfers

Fixes: use unpacked mode when transfer length is less than 4 bytes. Packed mode expects minimum transfer length of 4 bytes. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V1 09/26] spi: tegra114: dump SPI registers during timeout

This patch dumps SPI registers on DMA or transfer timeout for debug purpose. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index

[PATCH V1 12/26] spi: tegra114: add SPI_LSB_FIRST support

Tegra SPI controller supports lsb first mode. Default is MSB bit first and on selection of SPI_LSB_FIRST through SPI mode transmission happens with LSB bit first. This patch adds SPI_LSB_FIRST flag to mode_bits and also configures it on request. Signed-off-by: Sowjanya Komatineni ---

[PATCH V1 17/26] spi: tegra114: add support for interrupt mask

This patch creates tegra_spi_soc_data structure to maintain and implement SPI HW feature differences between different Tegra chips and also creates a separate compatible string for T124/T210/T186. Tegra210 and later has a separate interrupt mask register SPI_INTR_MASK for enabling or disabling

[PATCH V1 14/26] spi: tegra114: add 3 wire transfer mode support

This patch adds 3 wire transfer support to SPI mode list and also implements it. 3 wire or Bi-directional mode uses only one serial data pin for the transfer. SPI in master mode uses MOSI data line only and MISO data line is not used by the SPI. Signed-off-by: Sowjanya Komatineni ---

[PATCH V1 19/26] DT bindings: spi: add spi client device properties

This patch adds below cs timing properties to allow SPI master configuring setup, hold and time interval between two SPI transactions to meet specific SPI client device requirements. CS setup time CS hold time CS inactive delay DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com;

[PATCH V1 20/26] spi: tegra114: add support for tuning HW CS timing

Some slaves may need certain CS setup time, hold time, CS inactive delay between the packets. Tegra SPI controller supports configuring these CS timing parameters and are applicable when using HW CS. This patch adds support for configuring these HW CS timing parameters through device tree

[PATCH V1 21/26] DT bindings: spi: add tx/rx clock delay SPI client properties

This patch adds Tegra SPI master tx and rx clock delay properties. TX/RX clock delays may vary depending on the platform design trace lengths for each client on the Tegra SPI bus. These properties helps to tune the clock delays. Signed-off-by: Sowjanya Komatineni ---

[PATCH V1 23/26] spi: tegra114: add support for gpio based cs

This patch adds supports for chip select control using GPIO if valid CS gpio exists rather than controlling from the SPI controller. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 57 ++ 1 file changed, 57 insertions(+) diff

[PATCH V1 26/26] spi: tegra114: add support for LSBYTE_FIRST

Some SPI devices expects SPI transfers to be in Least significant byte first order and some devices expect Most significant byte first order. This patch adds SPI_LSBYTE_FIRST to supported mode list and implements configuration accordingly. Signed-off-by: Sowjanya Komatineni ---

[PATCH V1 24/26] spi: tegra114: de-assert CS before SPI mode is reset to its default

With SW CS, during transfer completion CS is de-asserted by writing the default command1 register value to SPI_COMMAND1 register. With this both mode and CS state are set at the same time and if current transfer mode is different to default SPI mode and if mode change happens prior to CS

[PATCH V1 25/26] spi: expand mode and mode_bits support

mode and mode_bits is declared as u16 and all bits are used. This patch changes mode and mode_bits to be u32 to allow for more mode configurations. Some SPI Master controllers support configuring Least significant byte first or Most significant byte first order for transfers. Also some SPI slave

[PATCH V1 13/26] spi: tegra114: add dual mode support

This patch adds support for dual mode SPI transfer. Dual mode uses both MOSI and MISO lines in parallel where the data is interleaved on MOSI and MISO lines increasing the throughput. Packet from Tx FIFO is transmitted on both MOSI and MISO lines and packet to Rx FIFO is received from both MOSI

[PATCH V1 18/26] spi: tegra114: add support for hw based cs

This patch adds support for HW based CS control. Tegra SPI controller supports both HW and SW based CS control transfers. Tegra SPI driver default uses SW CS control for transfers and HW CS control can be enabled through SPI client device node DT property nvidia,enable-hw-based-cs and is used

[PATCH V1 15/26] spi: tegra114: set supported bits_per_word

Tegra SPI supports 4 through 32 bits per word. This patch sets bits_per_word_mask accordingly to support transfer with these bits per word. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V1 22/26] spi: tegra114: add support for tuning clock delay

Tegra SPI controller has TX_CLK_TAP_DELAY and RX_CLK_TAP_DELAY in COMMAND2 register to tune delay of the clock going out to external device during transmit and also for the clock coming in from external device during receive. TX/RX clock tap delays may vary based on the trace lengths of the

[PATCH V1 16/26] spi: tegra114: set bus number based on id

This patch sets the SPI device id from the device tree as the bus number. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/spi/spi-tegra114.c b/drivers/spi/spi-tegra114.c index 94acef0f5ea5..9b9d4b9e1f3e 100644 ---

[PATCH V1 08/26] spi: tegra114: configure dma burst size to fifo trig level

Fixes: Configure DMA burst size to be same as SPI TX/RX trigger levels to avoid mismatch. SPI FIFO trigger levels are calculated based on the transfer length. So this patch moves DMA slave configuration to happen before start of DMAs. Signed-off-by: Sowjanya Komatineni ---

[PATCH V1 07/26] spi: tegra114: flush fifos

Fixes: Flush TX and RX FIFOs before start of new transfer and on FIFO overflow or underrun errors. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 39 ++- 1 file changed, 30 insertions(+), 9 deletions(-) diff --git

[PATCH V1 01/26] spi: tegra114: fix PIO transfer

Fixes: Use PIO bit in SPI_COMMAND1 register for PIO mode. Current driver uses DMA_EN instead of PIO bit. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/spi/spi-tegra114.c

[PATCH V1 02/26] spi: tegra114: clear packed bit for unpacked mode

Fixes: Clear packed bit when not using packed mode. Packed bit is not cleared when not using packed mode. This results in transfer timeouts for the unpacked mode transfers followed by the packed mode transfers. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 2 ++ 1 file

[PATCH V1 04/26] spi: tegra114: use packed mode for 32 bits per word

Fixes: Use packed mode for 32 bits per word transfers to increase performance as each packet is a full 32-bit word. Signed-off-by: Sowjanya Komatineni --- drivers/spi/spi-tegra114.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/spi-tegra114.c

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

On Tue, Mar 26, 2019 at 10:29:41PM -0700, Andy Lutomirski wrote: > > > > On Mar 26, 2019, at 10:06 PM, Greg KH wrote: > > > >> On Tue, Mar 26, 2019 at 09:29:14PM -0700, Andy Lutomirski wrote: > >>> On Tue, Mar 26, 2019 at 5:31 PM Greg KH > >>> wrote: > >>> > On Tue, Mar 26, 2019 at

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

> On Mar 26, 2019, at 10:06 PM, Greg KH wrote: > >> On Tue, Mar 26, 2019 at 09:29:14PM -0700, Andy Lutomirski wrote: >>> On Tue, Mar 26, 2019 at 5:31 PM Greg KH wrote: >>> On Tue, Mar 26, 2019 at 12:20:24PM -0700, Andy Lutomirski wrote: On Tue, Mar 26, 2019 at 11:28 AM Matthew

Re: [PATCH 03/17] fpga: dfl: fme: support 512bit data width PR

On Mon, Mar 25, 2019 at 05:58:36PM -0500, Scott Wood wrote: > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote: > > On Mon, 2019-03-25 at 11:07 +0800, Wu Hao wrote: > > > In early partial reconfiguration private feature, it only > > > supports 32bit data width when writing data to hardware for

[PATCH] trace/page_ref: print out the page migratetype name

Print out the page migratetype name which is more readable. Signed-off-by: Huang Shijie --- include/trace/events/page_ref.h | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/include/trace/events/page_ref.h b/include/trace/events/page_ref.h index

Zdravstvujte Vas interesuyut klientskie bazy dannyh?

Zdravstvujte Vas interesuyut klientskie bazy dannyh?

[PATCH v7 7/7] cros_ec: differentiate SCP from EC by feature bit.

From: Pi-Hsun Shih Since a SCP and EC would both exist on a system, and use the cros_ec_dev driver, we need to differentiate between them for the userspace, or they would both be registered at /dev/cros_ec, causing a conflict. Signed-off-by: Pi-Hsun Shih --- Changes from v6: - No change.

[PATCH v7 5/7] dt-bindings: Add binding for cros-ec-rpmsg.

From: Pi-Hsun Shih Add a DT binding documentation for ChromeOS EC driver over rpmsg. Signed-off-by: Pi-Hsun Shih --- Changes from v6: - No change. Changes from v5: - New patch. --- Documentation/devicetree/bindings/mfd/cros-ec.txt | 5 - 1 file changed, 4 insertions(+), 1 deletion(-)

[PATCH v7 6/7] platform/chrome: cros_ec: add EC host command support using rpmsg.

From: Pi-Hsun Shih Add EC host command support through rpmsg. Signed-off-by: Pi-Hsun Shih --- Changes from v6: - Make data for response aligned to 4 bytes. Changes from v5: - Change commit title. - Add documents for some structs, and fix all warning from scripts/kernel-doc. -

[PATCH v7 4/7] rpmsg: add rpmsg support for mt8183 SCP.

From: Pi-Hsun Shih Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly. Signed-off-by: Pi-Hsun Shih --- Changes from v6: - Decouple mtk_rpmsg from mtk_scp by putting all necessary informations (name service IPI id, register/unregister/send functions) into a struct,

[PATCH v7 1/7] dt-bindings: Add a binding for Mediatek SCP

From: Erin Lo Add a DT binding documentation of SCP for the MT8183 SoC from Mediatek. Signed-off-by: Erin Lo Signed-off-by: Pi-Hsun Shih Reviewed-by: Rob Herring --- Changes from v6: - No change. Changes from v5: - Remove dependency on CONFIG_RPMSG_MTK_SCP. Changes from v4: - Add detail

[PATCH v7 3/7] remoteproc: mt8183: add reserved memory manager API

From: Erin Lo Add memory table mapping API for other driver to lookup reserved physical and virtual memory Signed-off-by: Erin Lo Signed-off-by: Pi-Hsun Shih --- Changes from v6: - No change. Changes from v5: - No change. Changes from v4: - New patch. --- drivers/remoteproc/mtk_scp.c

[PATCH v7 2/7] remoteproc/mediatek: add SCP support for mt8183

From: Erin Lo Provide a basic driver to control Cortex M4 co-processor Signed-off-by: Erin Lo Signed-off-by: Nicolas Boichat Signed-off-by: Pi-Hsun Shih --- Changes from v6: - No change. Changes from v5: - Changed some space to tab. Changes from v4: - Rename most function from mtk_scp_*

Re: [PATCH 5.0 00/52] 5.0.5-stable review

On Wed, Mar 27, 2019 at 09:36:06AM +0530, Naresh Kamboju wrote: > On Tue, 26 Mar 2019 at 12:09, Greg Kroah-Hartman > wrote: > > > > This is the start of the stable review cycle for the 5.0.5 release. > > There are 52 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

On Tue, Mar 26, 2019 at 09:29:14PM -0700, Andy Lutomirski wrote: > On Tue, Mar 26, 2019 at 5:31 PM Greg KH wrote: > > > > On Tue, Mar 26, 2019 at 12:20:24PM -0700, Andy Lutomirski wrote: > > > On Tue, Mar 26, 2019 at 11:28 AM Matthew Garrett > > > wrote: > > > > > > > > From: Matthew Garrett >

RE: [PATCH] input: keyboard: snvs: make sure irq is handled correctly

Hi, Dmitry Best Regards! Anson Huang > -Original Message- > From: dmitry.torok...@gmail.com [mailto:dmitry.torok...@gmail.com] > Sent: 2019年3月27日 12:29 > To: Anson Huang > Cc: Fabio Estevam ; linux-in...@vger.kernel.org; > linux-kernel@vger.kernel.org; dl-linux-imx > Subject: Re:

[PATCH] clocksource/drivers/timer-ti-dm: Remove omap_dm_timer_set_load_start

Commit 008258d995a6 ("clocksource/drivers/timer-ti-dm: Make omap_dm_timer_set_load_start() static") made omap_dm_time_set_load_start static because its prototype was not defined in a header. Unfortunately, this causes a build warning on multi_v7_defconfig because this function is not used anywhere

Re: [PATCH v19,RESEND 16/27] x86/sgx: Add the Linux SGX Enclave Driver

On Tue, Mar 26, 2019 at 12:01:31PM +, Huang, Kai wrote: > On Wed, 2019-03-20 at 18:21 +0200, Jarkko Sakkinen wrote: > > Intel Software Guard eXtensions (SGX) is a set of CPU instructions that > > can be used by applications to set aside private regions of code and > > data. The code outside

[PATCH v13 11/11] thermal: intel: intel_soc_dts_iosf: Utilize for_each_set_clump8 macro

Utilize for_each_set_clump8 macro, and the bitmap_set_value8 and bitmap_get_value8 functions, where appropriate. In addition, remove the now unnecessary temp_mask and temp_shift members of the intel_soc_dts_sensor_entry structure. Suggested-by: Andy Shevchenko Tested-by: Andy Shevchenko

[PATCH v13 10/11] gpio: 74x164: Utilize the for_each_set_clump8 macro

Replace verbose implementation in set_multiple callback with for_each_set_clump8 macro to simplify code and improve clarity. Suggested-by: Andy Shevchenko Cc: Geert Uytterhoeven Cc: Phil Reid Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-74x164.c | 19 +-- 1

[PATCH v13 09/11] gpio: uniphier: Utilize for_each_set_clump8 macro

Replace verbose implementation in set_multiple callback with for_each_set_clump8 macro to simplify code and improve clarity. An improvement in this case is that banks that are not masked will now be skipped. Cc: Masahiro Yamada Signed-off-by: William Breathitt Gray ---

[PATCH v13 08/11] gpio: pcie-idio-24: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-pcie-idio-24.c | 109 --- 1 file

[PATCH v13 07/11] gpio: pci-idio-16: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-pci-idio-16.c | 75 - 1 file

[PATCH v13 06/11] gpio: ws16c48: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-ws16c48.c | 73 ++--- 1 file

[PATCH v13 05/11] gpio: gpio-mm: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-gpio-mm.c | 73 +++-- 1 file

[PATCH v13 04/11] gpio: 104-idi-48: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-idi-48.c | 36 +++--- 1 file

[PATCH v13 03/11] gpio: 104-dio-48e: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-dio-48e.c | 73 ++--- 1 file

[PATCH v13 02/11] lib/test_bitmap.c: Add for_each_set_clump8 test cases

The introduction of the for_each_set_clump8 macro warrants test cases to verify the implementation. This patch adds test case checks for whether an out-of-bounds clump index is returned, a zero clump is returned, or the returned clump value differs from the expected clump value. Cc: Rasmus

Re: Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED'

On Tue, Mar 26, 2019 at 09:59:40AM -0500, Denis Kenzior wrote: > Hi James, > > On 03/26/2019 09:25 AM, James Bottomley wrote: > > Looking at the contents of linux/keys/trusted.h, it looks like the > > wrong decision to move it. The contents are way too improperly named > > and duplicative to be

[PATCH v13 01/11] bitops: Introduce the for_each_set_clump8 macro

This macro iterates for each 8-bit group of bits (clump) with set bits, within a bitmap memory region. For each iteration, "start" is set to the bit offset of the found clump, while the respective clump value is stored to the location pointed by "clump". Additionally, the bitmap_get_value8 and

[PATCH v13 00/11] Introduce the for_each_set_clump8 macro

Changes in v13: - Reimplement find_next_clump8 to leverage find_next_bit - Restrict bitmap_get_value8/bitmap_set_value8 start argument to values that are multiples of 8; this prevents cases where a clump lands between word boundaries - Trim const qualifiers from bitmap_get_value8,

Re: Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED'

On Tue, Mar 26, 2019 at 07:25:17AM -0700, James Bottomley wrote: > On Tue, 2019-03-26 at 08:10 -0400, Mimi Zohar wrote: > > Hi Jarrko, > > > > On Tue, 2019-03-26 at 13:37 +0200, Jarkko Sakkinen wrote: > > > Mimi, > > > > > > Can you fix this and I can ack and send PR through my tree? > > > >

Re: [PATCH 03/17] fpga: dfl: fme: support 512bit data width PR

On Tue, Mar 26, 2019 at 04:22:34PM -0500, Scott Wood wrote: > On Tue, 2019-03-26 at 14:33 -0500, Alan Tull wrote: > > On Mon, Mar 25, 2019 at 5:58 PM Scott Wood wrote: > > > > Hi Scott, > > > > > On Mon, 2019-03-25 at 17:53 -0500, Scott Wood wrote: > > > > On Mon, 2019-03-25 at 11:07 +0800, Wu

Re: [PATCH] Input: elan_i2c - Add i2c_reset in sysfs for ELAN touchpad recovery

Hi KT, On Sat, Feb 02, 2019 at 03:54:56PM +0800, KT Liao wrote: > Roger from SUSE reported the touchpad on Lenovo yoga2 crush sometimes. > He found that rmmod/modprobe elan_i2c will recover the issue. > He add the workaround on SUSE and solve the problem. > Recently, the workaround fails in

Re: [RFC PATCH] x86/entry/64: randomize kernel stack offset upon syscall

On Tue, Mar 26, 2019 at 3:35 AM Reshetova, Elena wrote: > > > On Mon, Mar 18, 2019 at 1:16 PM Andy Lutomirski wrote: > > > On Mon, Mar 18, 2019 at 2:41 AM Elena Reshetova > > > wrote: > > > > Performance: > > > > > > > > 1) lmbench: ./lat_syscall -N 100 null > > > > base:

Re: linux-next: build failure after merge of the sound-asoc tree

Mark Brown writes: > On Tue, Mar 26, 2019 at 01:33:49PM +1100, Stephen Rothwell wrote: > >> After merging the sound-asoc tree, today's linux-next build (powerpc >> allyesconfig) failed like this: > >> sound/soc/codecs/tlv320aic32x4-clk.c: In function 'clk_aic32x4_pll_prepare': >>

Re: [PATCH] Input: elan_i2c - Add many hardware ID for lenovo laptop

On Wed, Mar 13, 2019 at 08:17:43PM +0800, KT Liao wrote: > There are many Lenovo laptop which need elan_i2c support. > Elan collects the list ands add to add to elan_acpi_id[] > > Signed-off-by: KT Liao Applied, thank you. -- Dmitry

Re: [PATCH RESEND v3] tpm: fix an invalid condition in tpm_common_poll

On Tue, Mar 26, 2019 at 08:58:28AM -0700, Tadeusz Struk wrote: > Hi Jarkko, > On 3/25/19 7:09 AM, Jarkko Sakkinen wrote: > > It is still missing the comment I asked to add. Otherwise, it is good. > > > > Sorry, I didn't see your email with the suggestion earlier. > To be honest I'm not sure if

Re: [PATCH] input: keyboard: snvs: make sure irq is handled correctly

Hi Anson, On Wed, Mar 27, 2019 at 02:47:06AM +, Anson Huang wrote: > SNVS IRQ is requested before necessary driver data initialized, > if there is a pending IRQ during driver probe phase, kernel > NULL pointer panic will occur in IRQ handler. To avoid such > scenario, need to move the IRQ

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

On Tue, Mar 26, 2019 at 5:31 PM Greg KH wrote: > > On Tue, Mar 26, 2019 at 12:20:24PM -0700, Andy Lutomirski wrote: > > On Tue, Mar 26, 2019 at 11:28 AM Matthew Garrett > > wrote: > > > > > > From: Matthew Garrett > > > > > > debugfs has not been meaningfully audited in terms of ensuring that >

Re: [PATCH 5.0 00/52] 5.0.5-stable review

On Tue, 26 Mar 2019 at 12:09, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.0.5 release. > There are 52 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. > >

Re: [PATCH 4.19 00/45] 4.19.32-stable review

On Tue, 26 Mar 2019 at 12:06, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.32 release. > There are 45 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. > >

Re: possible deadlock in acct_pin_kill

syzbot has bisected this bug to: commit e950564b97fd0f541b02eb207685d0746f5ecf29 Author: Miklos Szeredi Date: Tue Jul 24 13:01:55 2018 + vfs: don't evict uninitialized inode bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1212314320 start commit: da5322e6 Merge

linux-next: Tree for Mar 27

Hi all, Changes since 20190326: The bpf-next tree gained a conflict against the net tree. The sound-asoc tree lost its build failure but gained another for which I reverted 3 commits. The drm-intel tree gained a build failure for which I reverted some comits. Non-merge commits (relative

[PATCHv1 5/7] vfio/mdev: Follow correct remove sequence

mdev_remove_sysfs_files() should follow exact mirror sequence of a create, similar to what is followed in error unwinding path of mdev_create_sysfs_files(). Fixes: 6a62c1dfb5c7 ("vfio/mdev: Re-order sysfs attribute creation") Reviewed-by: Maxim Levitsky Signed-off-by: Parav Pandit ---

[PATCHv1 7/7] vfio/mdev: Fix race conditions with mdev device life cycle APIs

Below race condition and call trace exist with current device life cycle sequence. 1. In following sequence, child devices created while removing mdev parent device can be left out, or it may lead to race of removing half initialized child mdev devices. issue-1: cpu-0

[PATCHv1 6/7] vfio/mdev: Fix aborting mdev child device removal if one fails

device_for_each_child() stops executing callback function for remaining child devices, if callback hits an error. Each child mdev device is independent of each other. While unregistering parent device, mdev core must remove all child mdev devices. Therefore, mdev_device_remove_cb() always returns

[PATCHv1 1/7] vfio/mdev: Avoid release parent reference during error path

During mdev parent registration in mdev_register_device(), if parent device is duplicate, it releases the reference of existing parent device. This is incorrect. Existing parent device should not be touched. Fixes: 7b96953bc640 ("vfio: Mediated device Core driver") Reviewed By: Kirti Wankhede

[PATCHv1 4/7] vfio/mdev: Avoid masking error code to EBUSY

Instead of masking return error to -EBUSY, return actual error returned by the driver. Reviewed-by: Maxim Levitsky Signed-off-by: Parav Pandit --- drivers/vfio/mdev/mdev_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/vfio/mdev/mdev_core.c

[PATCHv1 2/7] vfio/mdev: Removed unused kref

Remove unused kref from the mdev_device structure. Fixes: 7b96953bc640 ("vfio: Mediated device Core driver") Reviewed By: Kirti Wankhede Reviewed-by: Maxim Levitsky Signed-off-by: Parav Pandit --- drivers/vfio/mdev/mdev_core.c| 1 - drivers/vfio/mdev/mdev_private.h | 1 - 2 files changed,

[PATCHv1 3/7] vfio/mdev: Drop redundant extern for exported symbols

There is no need use 'extern' for exported functions. Reviewed-by: Maxim Levitsky Signed-off-by: Parav Pandit --- include/linux/mdev.h | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/include/linux/mdev.h b/include/linux/mdev.h index d7aee90..4924d80

[PATCHv1 0/7] vfio/mdev: Improve vfio/mdev core module

As we would like to use mdev subsystem for wider use case as discussed in [1], [2] apart from an offline discussion. This use case is also discussed with wider forum in [4] in track 'Lightweight NIC HW functions for container offload use cases'. This series is prep-work and improves vfio/mdev

Re: [PATCH 06/10] mm: vmscan: demote anon DRAM pages to PMEM node

On 3/26/19 5:35 PM, Keith Busch wrote: On Mon, Mar 25, 2019 at 12:49:21PM -0700, Yang Shi wrote: On 3/24/19 3:20 PM, Keith Busch wrote: How do these pages eventually get to swap when migration fails? Looks like that's skipped. Yes, they will be just put back to LRU. Actually, I don't

RE: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

Hi Alex, > -Original Message- > From: Alex Williamson > Sent: Tuesday, March 26, 2019 10:27 AM > To: Kirti Wankhede > Cc: Parav Pandit ; k...@vger.kernel.org; linux- > ker...@vger.kernel.org; Neo Jia > Subject: Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence > > On Tue,

linux-next: build failure after merge of the drm-intel tree

Hi all, After merging the drm-intel tree, today's linux-next build (i386 defconfig) failed like this: In file included from drivers/gpu/drm/i915/intel_guc.h:28:0, from drivers/gpu/drm/i915/intel_uc.h:27, from drivers/gpu/drm/i915/intel_uc.c:25:

Re: [RFC PATCH 0/10] Another Approach to Use PMEM as NUMA Node

On 3/26/19 11:37 AM, Michal Hocko wrote: On Tue 26-03-19 11:33:17, Yang Shi wrote: On 3/26/19 6:58 AM, Michal Hocko wrote: On Sat 23-03-19 12:44:25, Yang Shi wrote: With Dave Hansen's patches merged into Linus's tree

Re: [PATCH] ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock for SDMA

On Mon, Mar 25, 2019 at 3:49 AM Fabio Estevam wrote: > > Hi Andrey, > > On Mon, Mar 25, 2019 at 2:01 AM Andrey Smirnov > wrote: > > > diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi > > index 9f9aa6e7ed0e..354feba077b2 100644 > > --- a/arch/arm/boot/dts/imx6qdl.dtsi

[PATCH] input: keyboard: snvs: make sure irq is handled correctly

SNVS IRQ is requested before necessary driver data initialized, if there is a pending IRQ during driver probe phase, kernel NULL pointer panic will occur in IRQ handler. To avoid such scenario, need to move the IRQ request to after driver data initialization done. This patch is inspired by NXP's

Re: [PATCH v3 3/4] driver core: add dev_print_hex_dump() logging function.

On Tue, Mar 26, 2019 at 06:48:06PM -0700, Ronald Tschalär wrote: > This is the dev_xxx() analog to print_hex_dump(), using dev_printk() > instead of straight printk() to match other dev_xxx() logging functions. > --- > drivers/base/core.c| 43 ++ >

[PATCH v5 1/1] mm: introduce put_user_page*(), placeholder versions

From: John Hubbard Introduces put_user_page(), which simply calls put_page(). This provides a way to update all get_user_pages*() callers, so that they call put_user_page(), instead of put_page(). Also introduces put_user_pages(), and a few dirty/locked variations, as a replacement for

[PATCH v5 0/1] mm: introduce put_user_page*(), placeholder versions

From: John Hubbard Hi Andrew and all, Can we please apply this for Linux 5.2? I'm adding a Reviewed-by from Christopher Lameter (thanks!), and an updated comment about a race condition (from Kirill's review feedback), and can now make the following statement more confidently: We seem to have

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

On Tue, Mar 26, 2019 at 07:06:36PM -0700, Matthew Garrett wrote: > On Tue, Mar 26, 2019 at 5:31 PM Greg KH wrote: > > On Tue, Mar 26, 2019 at 11:27:41AM -0700, Matthew Garrett wrote: > > > From: Matthew Garrett > > > > > > debugfs has not been meaningfully audited in terms of ensuring that > > >

Re: [PATCH v2 00/11] LSM documentation update

On Tue, 26 Feb 2019, Denis Efremov wrote: > Recent "New LSM Hooks" discussion has led me to the > thought that it might be a good idea to slightly > update the current documentation. The patchset adds > nothing new to the documentation, only fixes the old > description of hooks to reflect their

Re: [PATCH] HID: intel-ish-hid: ISH firmware loader client driver

On Tue, 2019-03-26 at 18:39 -0600, Nick Crews wrote: > Hi Rushikesh, I know I've been reviewing this on Chromium, but I have > some more larges-scale design thoughts. Hi Nick. Does this fundamentally change, the way it is done here or can wait for subsequent revisions later? Thanks, Srinivas >

RE: [PATCHv4 00/28] PCI: refactor Mobiveil driver and add PCIe Gen4 driver for NXP Layerscape SoCs

Hi Lorenzo, Thanks for your comments! > -Original Message- > From: Lorenzo Pieralisi > Sent: 2019年3月27日 1:38 > To: Z.q. Hou > Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; > bhelg...@google.com;

Re: [PATCH V31 25/25] debugfs: Disable open() when kernel is locked down

On Tue, Mar 26, 2019 at 5:31 PM Greg KH wrote: > On Tue, Mar 26, 2019 at 11:27:41AM -0700, Matthew Garrett wrote: > > From: Matthew Garrett > > > > debugfs has not been meaningfully audited in terms of ensuring that > > userland cannot trample over the kernel. At Greg's request, disable > >

RE: [PATCHv4 16/28] PCI: mobiveil: refactor Mobiveil PCIe Host Bridge IP driver

Hi Lorenzo, Thanks for your comments! > -Original Message- > From: Lorenzo Pieralisi > Sent: 2019年3月27日 1:34 > To: Z.q. Hou > Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; > bhelg...@google.com;

Re: [PATCH v2 0/4] Add new features for the Spreadtrum serial controller

On Wed, 27 Mar 2019 at 08:59, Greg KH wrote: > > On Tue, Mar 26, 2019 at 06:41:31PM +0800, Baolin Wang wrote: > > Hi Greg, > > > > On Mon, 4 Mar 2019 at 16:59, Baolin Wang wrote: > > > > > > This patch set fixes the baud rate calculation formula issue, as well as > > > adding power management

[PATCH v5 2/2] staging: mt7621-mmc: Initialize completions a single time during probe

The module was initializing completions whenever it was going to wait on them, and not when the completion was allocated. This is incorrect according to the completion docs: Calling init_completion() on the same completion object twice is most likely a bug [...] Re-initialization is

RE: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

Hello，Paul I use a new NUC (made in 2017) to test, meet the same hang. System run very slowly. But I use my PC (made before 2015), test V3.18.136+ patch for 12 hours, still well. Maybe V3.18.y don't support some new devices. -Original Message- From: Paul E. McKenney

[PATCH v5 1/2] staging: mt7621-mmc: Remove obsolete Kconfig flags

These values are not referred to anywhere else in the kernel. Card detect is controlled by the device tree property "mediatek,cd-poll", and there is no driver support for eMMC whatsoever. Signed-off-by: George Hilliard --- v2: Rewrite of v1 v3: [Not present] v4: Resubmit of v2 v5: No change from

[PATCH v5 0/2] staging: mt7621-mmc: correctness fixes

Now formatted according to checkpatch.pl, not my own semi-coherent sense of what the kernel style should be. No functionality changes. George

Re: [PATCH v2] x86/boot: Use EFI setup data if provided

Hi Junichi, On 03/26/19 at 02:57pm, Borislav Petkov wrote: > On Mon, Mar 25, 2019 at 11:10:01PM +, Junichi Nomura wrote: > > efi_get_rsdp_addr() and kexec_get_rsdp_addr() could be implemented > > like this (sorry about the pseudo code): > > This doesn't look like what I suggested: > > > So

[PATCH v3 4/4] Input: add Apple SPI keyboard and trackpad driver.

The keyboard and trackpad on recent MacBook's (since 8,1) and MacBookPro's (13,* and 14,*) are attached to an SPI controller instead of USB, as previously. The higher level protocol is not publicly documented and hence has been reverse engineered. As a consequence there are still a number of

[PATCH v3 1/4] drm/bridge: sil_sii8620: depend on INPUT instead of selecting it.

commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge: sil_sii8620: do not have a dependency of RC_CORE) added a dependency on INPUT. However, this causes problems with other drivers, in particular an input driver that depends on MFD_INTEL_LPSS_PCI (to be added in a future commit):

  1   2   3   4   5   6   7   8   9   10   >