RE: [PATCH v8 1/2] media: dt-bindings: media: xilinx: Add Xilinx MIPI CSI-2 Rx Subsystem

Hi Sakari, > -Original Message- > From: Sakari Ailus [mailto:sakari.ai...@linux.intel.com] > Sent: Thursday, June 06, 2019 5:43 PM > To: Vishal Sagar > Cc: Vishal Sagar ; Hyun Kwon ; > laurent.pinch...@ideasonboard.com; mche...@kernel.org; > robh...@kernel.org; mark.rutl...@arm.com;

[PATCH 1/2] habanalabs: add rate-limit to an error message

This patch changes the print of an error message about mis-configuration of the debug infrastructure to be rate-limited, to prevent flooding of kernel log, as these configuration requests can come at a high rate. Signed-off-by: Oded Gabbay --- drivers/misc/habanalabs/habanalabs_ioctl.c | 2 +-

[PATCH 2/2] docs/habanalabs: update text for some entries in sysfs

This patch updates the description of some entries in sysfs for the habanalabs driver. Signed-off-by: Oded Gabbay --- .../ABI/testing/sysfs-driver-habanalabs | 42 +++ 1 file changed, 24 insertions(+), 18 deletions(-) diff --git

Re: [PATCH] ASoC: msm8916-wcd-digital: Add sidetone support

Thanks for the review, On 06/06/2019 12:54, Mark Brown wrote: On Thu, Jun 06, 2019 at 12:40:02PM +0100, Srinivas Kandagatla wrote: + default: + pr_err("%s: event = %d not expected\n", __func__, event); + } dev_err() please (and a break; as well, it isn't strictly

Re: [PATCH v7 5/6] usb:cdns3 Add Cadence USB3 DRD Driver

Pawel, On 05/06/2019 13:03, Pawel Laszczak wrote: > This patch introduce new Cadence USBSS DRD driver to Linux kernel. > > The Cadence USBSS DRD Driver is a highly configurable IP Core which > can be instantiated as Dual-Role Device (DRD), Peripheral Only and > Host Only (XHCI)configurations. >

Re: [PATCH v8 1/2] media: dt-bindings: media: xilinx: Add Xilinx MIPI CSI-2 Rx Subsystem

Hi Vishal, On Thu, Jun 06, 2019 at 11:54:19AM +, Vishal Sagar wrote: > Hi Sakari, > > > -Original Message- > > From: Sakari Ailus [mailto:sakari.ai...@linux.intel.com] > > Sent: Wednesday, June 05, 2019 12:54 AM > > To: Vishal Sagar > > Cc: Hyun Kwon ;

Re: [PATCH v7 1/6] dt-bindings: add binding for USBSS-DRD controller.

Pawel, On 05/06/2019 13:03, Pawel Laszczak wrote: > This patch aim at documenting USB related dt-bindings for the > Cadence USBSS-DRD controller. > > Signed-off-by: Pawel Laszczak > Reviewed-by: Rob Herring > > --- > .../devicetree/bindings/usb/cdns-usb3.txt | 30 +++ > 1

Re: [PATCH V2] i2c: busses: tegra: Add suspend-resume support

06.06.2019 8:54, Bitan Biswas пишет: > Post suspend I2C registers have power on reset values. Before any > transfer initialize I2C registers to prevent I2C transfer timeout > and implement suspend and resume callbacks needed. Fix below errors > post suspend: > > 1) Tegra I2C transfer timeout

[PATCH v5 2/4] mm/vmalloc.c: preload a CPU with one object for split purpose

Refactor the NE_FIT_TYPE split case when it comes to an allocation of one extra object. We need it in order to build a remaining space. The preload is done per CPU in non-atomic context with GFP_KERNEL flags. More permissive parameters can be beneficial for systems which are suffer from high

[PATCH v5 4/4] mm/vmalloc.c: switch to WARN_ON() and move it under unlink_va()

Trigger a warning if an object that is about to be freed is detached. We used to have a BUG_ON(), but even though it is considered as faulty behaviour that is not a good reason to break a system. Signed-off-by: Uladzislau Rezki (Sony) --- mm/vmalloc.c | 25 ++--- 1 file

Re: [PATCH 01/16] firmware: ti_sci: Add resource management APIs for ringacc, psi-l and udma

Hi Lokesh, On 06/06/2019 9.00, Lokesh Vutla wrote: > Hi Peter, > > On 06/05/19 6:04 PM, Peter Ujfalusi wrote: >> Signed-off-by: Peter Ujfalusi > > Patch has the following checkpatch warnings and checks which can be fixed: > > WARNING: Missing commit description - Add an appropriate one How

[PATCH v5 3/4] mm/vmalloc.c: get rid of one single unlink_va() when merge

It does not make sense to try to "unlink" the node that is definitely not linked with a list nor tree. On the first merge step VA just points to the previously disconnected busy area. On the second step, check if the node has been merged and do "unlink" if so, because now it points to an object

[PATCH v5 1/4] mm/vmalloc.c: remove "node" argument

Remove unused argument from the __alloc_vmap_area() function. Signed-off-by: Uladzislau Rezki (Sony) Reviewed-by: Andrew Morton Reviewed-by: Roman Gushchin --- mm/vmalloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index

[PATCH v5 0/4] Some cleanups for the KVA/vmalloc

v4->v5: - base on next-20190606 - embed preloading directly into alloc_vmap_area(). [2] patch - update the commit message of [2]. - if RB_EMPTY_NODE(), generate warning and return; [4] patch v3->v4: - Replace BUG_ON by WARN_ON() in [4]; - Update the commit m

Re: [PATCH v6 1/2] Bluetooth: hci_qca: Load customized NVM based on the device property

On 2019-06-06 15:10, Rocky Liao wrote: QCA BTSOC NVM is a customized firmware file and different vendors may want to have different BTSOC configuration (e.g. Configure SCO over PCM or I2S, Setting Tx power, etc.) via this file. This patch will allow vendors to download different NVM firmware

Re: [PATCH v2] arm64: dts: qcom: Add Dragonboard 845c

On 06/06/2019 05:38, Bjorn Andersson wrote: This adds an initial dts for the Dragonboard 845. Supported functionality includes Debug UART, UFS, USB-C (peripheral), USB-A (host), microSD-card and Bluetooth. Initializing the SMMU is clearing the mapping used for the splash screen framebuffer,

Re: [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10)

* Mathieu Desnoyers: > Should we plan ahead for such scheme to override which library "owns" rseq > registration from a LD_PRELOAD library ? If so, then we would want glibc to > set __rseq_handled _after_ LD_PRELOAD ctors are executed. I don't think so. The LD_PRELOAD phase is not clearly

Re: [PATCH] scsi: libsas, lldds: Use dev_is_expander()

On Thu, Jun 6, 2019 at 3:35 AM Jason Yan wrote: > > > > On 2019/6/6 0:12, John Garry wrote: > > Many times in libsas, and in LLDDs which use libsas, the check for an > > expander device is re-implemented or open coded. > > > > Use dev_is_expander() instead. We rename this from > >

Re: [PATCH V4] drivers: i2c: tegra: fix checkpatch defects

On Thu, Jun 06, 2019 at 12:35:23AM -0700, Bitan Biswas wrote: > Fix checkpatch.pl warning(s)/error(s)/check(s) in i2c-tegra.c > > Remove redundant BUG_ON calls or replace with WARN_ON_ONCE > as needed. Replace BUG() with error handling code. > Define I2C_ERR_UNEXPECTED_STATUS for error handling.

RE: [PATCH v8 1/2] media: dt-bindings: media: xilinx: Add Xilinx MIPI CSI-2 Rx Subsystem

Hi Sakari, > -Original Message- > From: Sakari Ailus [mailto:sakari.ai...@linux.intel.com] > Sent: Wednesday, June 05, 2019 12:54 AM > To: Vishal Sagar > Cc: Hyun Kwon ; laurent.pinch...@ideasonboard.com; > mche...@kernel.org; robh...@kernel.org; mark.rutl...@arm.com; Michal > Simek ;

Re: [PATCH] ASoC: msm8916-wcd-digital: Add sidetone support

On Thu, Jun 06, 2019 at 12:40:02PM +0100, Srinivas Kandagatla wrote: > + default: > + pr_err("%s: event = %d not expected\n", __func__, event); > + } dev_err() please (and a break; as well, it isn't strictly needed but stops people having to check that it isn't needed). > +

Re: [PATCH] [RFC] dmaengine: add fifo_size member

On 06/06/2019 13.49, Jon Hunter wrote: > > On 06/06/2019 11:22, Peter Ujfalusi wrote: > > ... > > It does sounds like that FIFO_SIZE == src/dst_maxburst in your case as > well. Not exactly equal. ADMA burst_size can range from 1(WORD) to 16(WORDS) FIFO_SIZE can be

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

On 06/06/19 03:18, Like Xu wrote: > Add support to expose Intel V2 Extended Topology Enumeration Leaf for > some new systems with multiple software-visible die within each package. > > Because unimplemented and unexposed leaves should be explicitly reported > as zero, there is no need to limit

RE: [PATCH v8 1/2] media: dt-bindings: media: xilinx: Add Xilinx MIPI CSI-2 Rx Subsystem

Hi Sakari, Thanks for reviewing this. > -Original Message- > From: linux-media-ow...@vger.kernel.org [mailto:linux-media- > ow...@vger.kernel.org] On Behalf Of Sakari Ailus > Sent: Tuesday, June 04, 2019 8:56 PM > To: Vishal Sagar > Cc: Hyun Kwon ; laurent.pinch...@ideasonboard.com; >

Re: [PATCH V1] i2c: busses: tegra: Add suspend-resume support

06.06.2019 8:43, Bitan Biswas пишет: > > > On 5/31/19 5:43 AM, Dmitry Osipenko wrote: >> 31.05.2019 11:50, Bitan Biswas пишет: >>> >>> >>> On 5/30/19 4:27 AM, Dmitry Osipenko wrote: 30.05.2019 8:55, Bitan Biswas пишет: > Post suspend I2C registers have power on reset values. Before any

Re: [PATCH RFC 0/2] x86/boot: Introduce the setup_header2

On Wed, Jun 05, 2019 at 10:01:17AM -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Jun 05, 2019 at 03:50:31PM +0200, Daniel Kiper wrote: > > On Fri, May 24, 2019 at 11:55:02AM +0200, Daniel Kiper wrote: > > > Hi, > > > > > > This change is needed to properly start the Linux kernel in Intel TXT > >

Re: [PATCH 4.19 262/276] media: saa7146: avoid high stack usage with clang

On 6/6/19 1:44 PM, Pavel Machek wrote: > Hi! > >> Two saa7146/hexium files contain a construct that causes a warning >> when built with clang: >> >> drivers/media/pci/saa7146/hexium_orion.c:210:12: error: stack frame size of >> 2272 bytes in function 'hexium_probe' >>

Re: [PATCH v8 08/13] drivers: memory: add DMC driver for Exynos5422

On Thu, 6 Jun 2019 at 12:38, Lukasz Luba wrote: > Hi Krzysztof, > >> +/** > >> + * exynos5_dmc_init_clks() - Initialize clocks needed for DMC operation. > >> + * @dmc: DMC structure containing needed fields > >> + * > >> + * Get the needed clocks defined in DT device, enable and set the

Re: [PATCH 4.19 262/276] media: saa7146: avoid high stack usage with clang

Hi! > Two saa7146/hexium files contain a construct that causes a warning > when built with clang: > > drivers/media/pci/saa7146/hexium_orion.c:210:12: error: stack frame size of > 2272 bytes in function 'hexium_probe' > [-Werror,-Wframe-larger-than=] > static int hexium_probe(struct

Re: [BISECTED REGRESSION] b43legacy broken on G4 PowerBook

On Thu, Jun 06, 2019 at 08:57:49PM +1000, Benjamin Herrenschmidt wrote: > > Wow... that's an odd amount. One thing we could possibly do is add code > > to limit the amount of RAM when we detect that device > > Sent too quickly... I mean that *or* force swiotlb at 30-bits on those > systems

Re: [PATCH 2/2] edac: add support for Amazon's Annapurna Labs EDAC

Disagree. The various drivers don't depend on each other. I think we should keep the drivers separated as they are distinct and independent IP blocks. But they don't exist in isolation, they both depend on the integration-choices/firmware that makes up your platform. Other platforms may

[PATCH] ASoC: msm8916-wcd-digital: Add sidetone support

This patch adds sidetone support via one of the 3 RX Mix paths using IIR1 and IIR2. IIR1 can be feed by any Decimators or RX paths, and IIRx can also be looped back to RX mixers to provide sidetone functionality. Two IIR filters are used for Side tone equalization and each filter is 5 stage.

Re: [PATCH V4] drivers: i2c: tegra: fix checkpatch defects

06.06.2019 10:35, Bitan Biswas пишет: > Fix checkpatch.pl warning(s)/error(s)/check(s) in i2c-tegra.c > > Remove redundant BUG_ON calls or replace with WARN_ON_ONCE > as needed. Replace BUG() with error handling code. > Define I2C_ERR_UNEXPECTED_STATUS for error handling. > > Signed-off-by:

Re: [PATCH 7/7] staging: kpc2000: fix incorrect code comment in core.c

On Tue, Jun 04, 2019 at 12:29:16AM +0200, Simon Sandström wrote: > Step 11 was removed from kp2000_pcie_probe in a previous commit but the > comment was not changed to reflect this, so do it now. > > Signed-off-by: Simon Sandström > --- > drivers/staging/kpc2000/kpc2000/core.c | 2 +- > 1 file

[PATCH -mm V2 1/1] signal: simplify set_user_sigmask/restore_user_sigmask

task->saved_sigmask and ->restore_sigmask are only used in the ret-from- syscall paths. This means that set_user_sigmask() can save ->blocked in ->saved_sigmask and do set_restore_sigmask() to indicate that ->blocked was modified. This way the callers do not need 2 sigset_t's passed to

Re: [PATCH V2 4/4] arm64/mm: Drop local variable vm_fault_t from __do_page_fault()

On Thu, Jun 06, 2019 at 12:27:40PM +0100, Catalin Marinas wrote: > On Thu, Jun 06, 2019 at 10:24:01AM +0530, Anshuman Khandual wrote: > > On 06/04/2019 08:26 PM, Catalin Marinas wrote: > > > On Mon, Jun 03, 2019 at 12:11:25PM +0530, Anshuman Khandual wrote: > > >> diff --git

RE: [PATCH -mm 0/1] signal: simplify set_user_sigmask/restore_user_sigmask

From: Oleg Nesterov > Sent: 06 June 2019 12:05 > On 06/06, David Laight wrote: > > > > If a signal handler is called, I presume that the trampoline > > calls back into the kernel to get further handlers called > > and to finally restore the original signal mask? > > See sigmask_to_save(), this is

Re: [PATCH V2 4/4] arm64/mm: Drop local variable vm_fault_t from __do_page_fault()

On Thu, Jun 06, 2019 at 10:24:01AM +0530, Anshuman Khandual wrote: > On 06/04/2019 08:26 PM, Catalin Marinas wrote: > > On Mon, Jun 03, 2019 at 12:11:25PM +0530, Anshuman Khandual wrote: > >> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c > >> index 4bb65f3..41fa905 100644 > >> ---

Re: [PATCH v6 5/5] leds: lm36274: Introduce the TI LM36274 LED driver

Pavel On 6/6/19 5:07 AM, Pavel Machek wrote: On Wed 2019-06-05 07:56:34, Dan Murphy wrote: Introduce the LM36274 LED driver. This driver uses the ti-lmu MFD driver to probe this LED driver. The driver configures only the LED registers and enables the outputs according to the config file.

Re: [alsa-devel] [RESEND PATCH v3 00/30] Update cros_ec_commands.h

Hi Lee, Missatge de Lee Jones del dia dt., 4 de juny 2019 a les 8:00: > > On Mon, 03 Jun 2019, Gwendal Grignou wrote: > > > The interface between CrosEC embedded controller and the host, > > described by cros_ec_commands.h, as diverged from what the embedded > > controller really support. > > >

[PATCH] soundwire: intel: set dai min and max channels correctly

Looks like there is a copy paste error. This patch fixes it! Signed-off-by: Srinivas Kandagatla --- drivers/soundwire/intel.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/soundwire/intel.c b/drivers/soundwire/intel.c index 92be6ad84e8d..317873bc0555 100644 ---

Re: [PATCH V2 3/4] arm64/mm: Consolidate page fault information capture

On Thu, Jun 06, 2019 at 10:38:11AM +0100, Mark Rutland wrote: > On Tue, Jun 04, 2019 at 03:42:09PM +0100, Catalin Marinas wrote: > > On Mon, Jun 03, 2019 at 12:11:24PM +0530, Anshuman Khandual wrote: > > > diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c > > > index da02678..4bb65f3

Re: KASAN: use-after-free Read in device_del

On Thu, Jun 6, 2019 at 10:54 AM Oliver Neukum wrote: > > Am Montag, den 03.06.2019, 04:41 -0700 schrieb syzbot: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:69bbe8c7 usb-fuzzer: main usb gadget fuzzer driver > > git tree:

Re: [PATCH 2/2] edac: add support for Amazon's Annapurna Labs EDAC

On Thu, Jun 06, 2019 at 11:33:30AM +0100, James Morse wrote: > All these are integration choices between the two IP blocks, done as separate > drivers we > don't have anywhere to store that information. Even if you don't care about > this, making > them separate drivers should only be done to

[PATCH v2] soundwire: stream: fix bad unlock balance

multi bank switching code takes lock on condition but releases without any check resulting in below warning. This patch fixes this. = WARNING: bad unlock balance detected! 5.1.0-16506-gc1c383a6f0a2-dirty #1523 Tainted: GW

Re: [5.2.0-rcx] Bluetooth: hci0: unexpected event for opcode

Hi Joerg, >>> In 5.2.0-rcx I see a new error message on startup probably after >>> loading the Bluetooth firmware: >>> [1.609460] Bluetooth: hci0: unexpected event for opcode 0xfc2f >>> dmesg | grep Bluetooth >>> [0.130969] Bluetooth: Core ver 2.22 >>> [0.130973] Bluetooth: HCI

Re: [PATCH] arm64: dts: sdm845: Add iommus property to qup1

Hi Stephen, On Thu, Jun 6, 2019 at 2:27 AM Stephen Boyd wrote: > > Quoting Vivek Gautam (2019-06-04 21:55:26) > > On Wed, Jun 5, 2019 at 4:16 AM Stephen Boyd wrote: > > > > > > Quoting Bjorn Andersson (2019-06-04 15:37:00) > > > > On Tue 04 Jun 15:29 PDT 2019, Stephen Boyd wrote: > > > > > > >

Re: [PATCH v4] platform/chrome: mfd/cros_ec_debugfs: Add debugfs entry to retrieve EC uptime.

Hi Tim, Sorry for making you wait so much, now that the patches about cros_ec_commands include file has been accepted and the struct is up-to-date I can manage this. I've some few comments though, one of them is a change I requested but that now we should revert (sorry about that) Please rebase

Re: [PATCH] mm: memcontrol: dump memory.stat during cgroup OOM

On Wed 05-06-19 12:11:33, Johannes Weiner wrote: > On Wed, Jun 05, 2019 at 02:08:37PM +0200, Michal Hocko wrote: [...] > > I am not entirely happy with that many lines in the oom report though. I > > do see that you are trying to reduce code duplication which is fine but > > would it be possible

Re: [PATCH v2 1/2] dt-bindings: iio: adc: add adi,ad7780.yaml binding

On Wed, 2019-06-05 at 17:35 -0300, Renato Lui Geh wrote: > [External] > > > On 05/26, Jonathan Cameron wrote: > > On Fri, 24 May 2019 22:26:30 -0300 > > Renato Lui Geh wrote: > > > > > This patch adds a YAML binding for the Analog Devices AD7780/1 and > > > AD7170/1 analog-to-digital

Re: [PATCH -mm 0/1] signal: simplify set_user_sigmask/restore_user_sigmask

On 06/06, David Laight wrote: > > If a signal handler is called, I presume that the trampoline > calls back into the kernel to get further handlers called > and to finally restore the original signal mask? See sigmask_to_save(), this is what the kernel records in uc.uc_sigmask before the signal

Re: [PATCH RFC 07/10] fs/ext4: Fail truncate if pages are GUP pinned

On Wed 05-06-19 18:45:40, ira.we...@intel.com wrote: > From: Ira Weiny > > If pages are actively gup pinned fail the truncate operation. > > Signed-off-by: Ira Weiny > --- > fs/ext4/inode.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c > index

Re: [PATCH v3 06/15] drm/bridge: tc358767: Simplify AUX data read

On 05.06.2019 09:04, Andrey Smirnov wrote: > Simplify AUX data read by removing index arithmetic and shifting with > a helper functions that does three things: > > 1. Fetch data from up to 4 32-bit registers from the chip > 2. Optionally fix data endianness (not needed on LE hosts) >

Re: KMSAN: uninit-value in rt2500usb_bbp_read

On Thu, Jun 6, 2019 at 11:42 AM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:f75e4cfe kmsan: use kmsan_handle_urb() in urb.c > git tree: kmsan > console output: https://syzkaller.appspot.com/x/log.txt?x=12f8b01ea0 > kernel config:

Re: [BISECTED REGRESSION] b43legacy broken on G4 PowerBook

On Thu, 2019-06-06 at 20:56 +1000, Benjamin Herrenschmidt wrote: > On Thu, 2019-06-06 at 12:31 +0300, Aaro Koskinen wrote: > > Hi, > > > > On Thu, Jun 06, 2019 at 10:54:51AM +1000, Benjamin Herrenschmidt > > wrote: > > > On Thu, 2019-06-06 at 01:50 +0300, Aaro Koskinen wrote: > > > > Hi, > > > >

Re: [BISECTED REGRESSION] b43legacy broken on G4 PowerBook

On Thu, 2019-06-06 at 12:31 +0300, Aaro Koskinen wrote: > Hi, > > On Thu, Jun 06, 2019 at 10:54:51AM +1000, Benjamin Herrenschmidt > wrote: > > On Thu, 2019-06-06 at 01:50 +0300, Aaro Koskinen wrote: > > > Hi, > > > > > > When upgrading from v5.0 -> v5.1 on G4 PowerBook, I noticed WLAN > > >

[PATCH v2 4/3] KVM: LAPIC: add advance timer support to pi_inject_timer

From: Wanpeng Li Wait before calling posted-interrupt deliver function directly to add advance timer support to pi_inject_timer. Cc: Paolo Bonzini Cc: Radim Krčmář Signed-off-by: Wanpeng Li --- arch/x86/kvm/lapic.c | 6 -- arch/x86/kvm/lapic.h | 2 +- arch/x86/kvm/svm.c | 2 +-

Re: [PATCH] clk: rockchip: Remove 48 MHz PLL rate from rk3288

Am Mittwoch, 5. Juni 2019, 00:31:59 CEST schrieb Douglas Anderson: > The 48 MHz PLL rate is not present in the downstream chromeos-3.14 > tree. Looking at history, it was originally removed in > ("CHROMIUM: clk: rockchip: expand more > clocks support") with no

Re: [PATCH] Staging: emxx_udc: fix warning "sum of probable bitmasks, consider |"

On Wed, Jun 05, 2019 at 12:04:43PM +0530, Hariprasad Kelam wrote: > On Mon, Jun 03, 2019 at 09:04:57PM +0200, Greg Kroah-Hartman wrote: > > On Tue, Jun 04, 2019 at 12:24:12AM +0530, Hariprasad Kelam wrote: > > > Knowing the fact that operator '|' is faster than '+'. > > > Its better we replace +

Re: [PATCH] arm64: dts: sdm845: Add CPU topology

On Thu, Jun 06, 2019 at 10:44:58AM +0200, Vincent Guittot wrote: > On Thu, 6 Jun 2019 at 10:34, Dietmar Eggemann > wrote: > > > > On 6/6/19 10:20 AM, Vincent Guittot wrote: > > > On Thu, 6 Jun 2019 at 09:49, Quentin Perret > > > wrote: > > >> > > >> Hi Vincent, > > >> > > >> On Thursday 06 Jun

Re: [PATCH] [RFC] dmaengine: add fifo_size member

On 06/06/2019 11:22, Peter Ujfalusi wrote: ... It does sounds like that FIFO_SIZE == src/dst_maxburst in your case as well. >>> Not exactly equal. >>> ADMA burst_size can range from 1(WORD) to 16(WORDS) >>> FIFO_SIZE can be adjusted from 16(WORDS) to 1024(WORDS) [can vary in >>>

Re: [PATCH 2/2] ARM: dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on veyron

Am Mittwoch, 5. Juni 2019, 23:52:00 CEST schrieb Heiko Stübner: > Am Mittwoch, 5. Juni 2019, 23:24:27 CEST schrieb Matthias Kaehlcke: > > On Wed, Jun 05, 2019 at 11:11:12PM +0200, Heiko Stübner wrote: > > > Am Mittwoch, 5. Juni 2019, 22:43:20 CEST schrieb Matthias Kaehlcke: > > > > This enables

Re: [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices

Am Mittwoch, 5. Juni 2019, 22:43:19 CEST schrieb Matthias Kaehlcke: > With a single device DT overrides can become messy, especially when > keys are added or removed. Multiple devices also allow to > enable/disable wakeup per key/group. > > Signed-off-by: Matthias Kaehlcke applied for 5.3 with

Re: [PATCH][next] bpf: remove redundant assignment to err

On Mon, Jun 03, 2019 at 07:07:20PM +0100, Colin Ian King wrote: > On 03/06/2019 18:49, Jakub Kicinski wrote: > > On Mon, 3 Jun 2019 18:39:16 +0100, Colin Ian King wrote: > >> On 03/06/2019 18:21, Jakub Kicinski wrote: > >>> On Mon, 3 Jun 2019 18:02:47 +0100, Colin King wrote: > From: Colin

Re: [PATCH RFC 00/10] RDMA/FS DAX truncate proposal

On Wed 05-06-19 18:45:33, ira.we...@intel.com wrote: > From: Ira Weiny > > ... V1,000,000 ;-) > > Pre-requisites: > John Hubbard's put_user_pages() patch series.[1] > Jan Kara's ext4_break_layouts() fixes[2] > > Based on the feedback from LSFmm and the LWN article which resulted.

Hi dear,

Hi dear, I am still waiting for your Email response, you did receive my first email to you Respectfully Yours, Capt Katie Higgins

Re: [PATCH v8 08/13] drivers: memory: add DMC driver for Exynos5422

Hi Krzysztof, On 6/6/19 12:03 PM, Krzysztof Kozlowski wrote: > On Wed, 5 Jun 2019 at 18:54, Lukasz Luba wrote: >> >> This patch adds driver for Exynos5422 Dynamic Memory Controller. >> The driver provides support for dynamic frequency and voltage scaling for >> DMC and DRAM. It supports changing

Re: [5.2.0-rcx] Bluetooth: hci0: unexpected event for opcode

Am Do., 6. Juni 2019 um 08:18 Uhr schrieb Marcel Holtmann : > > Hi Joerg, > > > In 5.2.0-rcx I see a new error message on startup probably after > > loading the Bluetooth firmware: > > [1.609460] Bluetooth: hci0: unexpected event for opcode 0xfc2f > > > >> dmesg | grep Bluetooth > > [

Re: [PATCH 2/2] edac: add support for Amazon's Annapurna Labs EDAC

Hi Hawa, On 06/06/2019 08:53, Hawa, Hanna wrote: > On 5/31/2019 8:14 AM, Borislav Petkov wrote: >> On Fri, May 31, 2019 at 01:15:33AM +, Herrenschmidt, Benjamin wrote: >>> This isn't terribly helpful, there's nothing telling anybody which of >>> those files corresponds to an ARM SoC :-) >> >>

[PATCH v2 net-next] net: stmmac: move reset gpio parse & request to stmmac_mdio_register

Move the reset gpio dt parse and request to stmmac_mdio_register(), thus makes the mdio code straightforward. This patch also replace stack var mdio_bus_data with data to simplify the code. Signed-off-by: Jisheng Zhang --- Since v1: - rebase on the latest net-next tree

Re: [PATCH 1/1] ARM: dts: imx6ull-colibri: enable UHS-I for USDHC1

On Thu, 2019-06-06 at 12:06 +0300, Igor Opaniuk wrote: > From: Igor Opaniuk > > Allows to use the SD interface at a higher speed mode if the card > supports it. For this the signaling voltage is switched from 3.3V to > 1.8V under the usdhc1's drivers control. > > Signed-off-by: Igor Opaniuk

Re: [PATCH 3/5] ARM: dts: rockchip: Switch to builtin HDMI DDC bus on rk3288-veyron

Am Freitag, 3. Mai 2019, 00:53:34 CEST schrieb Douglas Anderson: > Downstream Chrome OS kernels use the builtin DDC bus from dw_hdmi on > veyron. This is the only way to get them to negotiate HDCP. > > Although HDCP isn't currently all supported upstream, it still seems > like it makes sense to

Re: [PATCH] lockref: Limit number of cmpxchg loop retries

On Thu, Jun 06, 2019 at 10:41:54AM +0100, Will Deacon wrote: > On Thu, Jun 06, 2019 at 08:03:27AM +, Jan Glauber wrote: > > On Wed, Jun 05, 2019 at 01:16:46PM -0700, Linus Torvalds wrote: > > > On Wed, Jun 5, 2019 at 6:49 AM Jan Glauber wrote: > > > > > > > > Add an upper bound to the loop to

Re: Race between MMIO writes and level IRQs

On Thu, Jun 06, 2019 at 11:53:05AM +0200, Marc Gonzalez wrote: > Hello everyone, > > There's something about interrupts I have never quite understood, > which I'd like to clear up once and for all. What I'm about to write > will probably sound trivial to anyone's who's already figured it out, >

[PATCH v3] serial: stm32: fix a recursive locking in stm32_config_rs485

Remove spin_lock_irqsave in stm32_config_rs485, it cause recursive locking. Already locked in uart_set_rs485_config. fixes: 1bcda09d291081 ("serial: stm32: add support for RS485 hardware control mode") Signed-off-by: Borut Seljak --- drivers/tty/serial/stm32-usart.c | 3 --- 1 file changed, 3

Re: [PATCH v4] platform/chrome: wilco_ec: Add event handling

On 24/5/19 1:06, Nick Crews wrote: > The Wilco Embedded Controller can create custom events that > are not handled as standard ACPI objects. These events can > contain information about changes in EC controlled features, > such as errors and events in the dock or display. For example, > an

Re: [PATCH v5] platform/chrome: wilco_ec: Add telemetry char device interface

On 21/5/19 21:20, Nick Crews wrote: > The Wilco Embedded Controller is able to send telemetry data > which is useful for enterprise applications. A daemon running on > the OS sends a command to the EC via a write() to a char device, > and can read the response with a read(). The write() request

Re: [PATCH -mm 0/1] signal: simplify set_user_sigmask/restore_user_sigmask

On 06/05, Linus Torvalds wrote: > > On Wed, Jun 5, 2019 at 8:58 AM Oleg Nesterov wrote: > > > > To simplify the review, please see the code with this patch applied. > > I am using epoll_pwait() as an example because it looks very simple. > > I like it. > > However. > > I think I'd like it even

Re: [PATCH v2 -next] platform/chrome: cros_ec: Make some symbols static

On 30/5/19 19:53, Benson Leung wrote: > Hello YueHaibing, > > On Thu, May 30, 2019 at 04:49:32PM +0800, YueHaibing wrote: >> Fix sparse warning: >> >> drivers/platform/chrome/cros_ec_debugfs.c:256:30: warning: symbol >> 'cros_ec_console_log_fops' was not declared. Should it be static? >>

Re: [PATCH] [RFC] dmaengine: add fifo_size member

Hi Jon, Sameer, On 06/06/2019 10.14, Jon Hunter wrote: > > On 06/06/2019 07:41, Sameer Pujar wrote: >> >> On 6/6/2019 11:30 AM, Peter Ujfalusi wrote: >>> Hi Sameer, >>> >>> On 06/06/2019 6.49, Sameer Pujar wrote: Sorry for late reply. [Resending the reply since delivery failed for few

Re: [PATCH v2] platform/chrome: wilco_ec: Add version sysfs entries

Hi, On 5/6/19 17:12, Nick Crews wrote: > Thanks Raul and Enric, this looks good to me. > > On Mon, Jun 3, 2019 at 2:40 PM Enric Balletbo i Serra > wrote: >> >> Nick, >> >> On 3/6/19 20:16, Raul E Rangel wrote: >>> Add the ability to extract version information from the EC. >>> >>> Example

RE: [RFC PATCH v2 1/3] vfio: Use capability chains to handle device specific irq

> -Original Message- > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On > Behalf Of kra...@redhat.com > Sent: Wednesday, June 5, 2019 6:10 PM > To: Zhang, Tina > Cc: Tian, Kevin ; k...@vger.kernel.org; linux- > ker...@vger.kernel.org; Zhenyu Wang ; Yuan, >

Re: [PATCH v8 07/13] dt-bindings: memory-controllers: add Exynos5422 DMC device description

Hi Krzysztof, On 6/6/19 10:29 AM, Krzysztof Kozlowski wrote: > On Wed, 5 Jun 2019 at 18:54, Lukasz Luba wrote: >> >> The patch adds description for DT binding for a new Exynos5422 Dynamic >> Memory Controller device. >> >> Signed-off-by: Lukasz Luba >> --- >>

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

in addition you should take care about this problem which is raised up if SAE is used. since AES-CMAC required tid to be non zero WARNING: CPU: 2 PID: 15324 at /home/seg/DEV/mt7621/src/router/private/compat-wireless-2017-09-03/net/mac80211/key.c:1096 mt76_wcid_key_setup+0x58/0x9c [mt76]

Re: [PATCH v3 1/2] mt76: mt7615: enable support for mesh

i tested your patch against a qca 9984 chipset using SAE and without encryption. both did not work. the devices are connecting, but no data connection is possible Sebastian Am 03.06.2019 um 08:08 schrieb Ryder Lee: Enable NL80211_IFTYPE_MESH_POINT and update its path. Signed-off-by: Ryder

[PATCH] vxlan: Use FDB_HASH_SIZE hash_locks to reduce contention

The monolithic hash_lock could cause huge contention when inserting/deletiing vxlan_fdbs into the fdb_head. Use FDB_HASH_SIZE hash_locks to protect insertions/deletions of vxlan_fdbs into the fdb_head hash table. Suggested-by: David S. Miller Signed-off-by: Litao jiao --- drivers/net/vxlan.c

Re: [PATCH v6 5/5] leds: lm36274: Introduce the TI LM36274 LED driver

On Wed 2019-06-05 07:56:34, Dan Murphy wrote: > Introduce the LM36274 LED driver. This driver uses the ti-lmu > MFD driver to probe this LED driver. The driver configures only the > LED registers and enables the outputs according to the config file. > > The driver utilizes the TI LMU (Lighting

Re: [PATCH v6 5/5] leds: lm36274: Introduce the TI LM36274 LED driver

Hi! > Introduce the LM36274 LED driver. This driver uses the ti-lmu > MFD driver to probe this LED driver. The driver configures only the > LED registers and enables the outputs according to the config file. > > The driver utilizes the TI LMU (Lighting Management Unit) LED common > framework

Re: Race between MMIO writes and level IRQs

On Thu, Jun 06, 2019 at 11:53:05AM +0200, Marc Gonzalez wrote: > Hello everyone, > > There's something about interrupts I have never quite understood, > which I'd like to clear up once and for all. What I'm about to write > will probably sound trivial to anyone's who's already figured it out, >

Re: [PATCH v8 08/13] drivers: memory: add DMC driver for Exynos5422

On Wed, 5 Jun 2019 at 18:54, Lukasz Luba wrote: > > This patch adds driver for Exynos5422 Dynamic Memory Controller. > The driver provides support for dynamic frequency and voltage scaling for > DMC and DRAM. It supports changing timings of DRAM running with different > frequency. There is also

Re: [PATCH 2/2] edac: add support for Amazon's Annapurna Labs EDAC

On Thu, Jun 06, 2019 at 10:53:42AM +0300, Hawa, Hanna wrote: > Disagree. The various drivers don't depend on each other. > I think we should keep the drivers separated as they are distinct and > independent IP blocks. This topic comes up each time someone submits a new ARM EDAC driver: EDAC can't

Re: [PATCH v6 4/5] dt-bindings: leds: Add LED bindings for the LM36274

Hi! > .../devicetree/bindings/leds/leds-lm36274.txt | 82 +++ > 1 file changed, 82 insertions(+) > create mode 100644 Documentation/devicetree/bindings/leds/leds-lm36274.txt > > diff --git a/Documentation/devicetree/bindings/leds/leds-lm36274.txt >

Re: [PATCH 07/13] drivers: Add generic match helper by ACPI_COMPANION device

On Thu, Jun 6, 2019 at 11:28 AM Suzuki K Poulose wrote: > > > > On 06/06/2019 10:17, Rafael J. Wysocki wrote: > > On Wed, Jun 5, 2019 at 5:14 PM Suzuki K Poulose > > wrote: > >> > >> Add a generic helper to match a device by the acpi device. > > > > "by its ACPI companion device object",

[RFC RESEND PATCH v2 4/4] arm64: dts: ti: am654-base-board: Add gpio_keys node

There are 2 push buttons: SW5 and SW6 that are basically connected to WKUP_GPIO0_24 and WKUP_GPIO0_27 respectively. Add the respective nodes and the pinctrl data to set the mode to GPIO and Input. Signed-off-by: Keerthy --- .../arm64/boot/dts/ti/k3-am654-base-board.dts | 27 +++

[RFC RESEND PATCH v2 3/4] arm64: dts: ti: am6-main: Add gpio nodes

Add gpio0/1 nodes under main domain. They have 96 and 90 gpios respectively and all are capable of generating banked interrupts. Signed-off-by: Keerthy --- arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 32 1 file changed, 32 insertions(+) diff --git

[RFC RESEND PATCH v2 1/4] dt-bindings: gpio: davinci: Add k3 am654 compatible

The patch adds k3 am654 compatible, specific properties and an example. Signed-off-by: Keerthy --- .../devicetree/bindings/gpio/gpio-davinci.txt | 18 ++ 1 file changed, 18 insertions(+) diff --git a/Documentation/devicetree/bindings/gpio/gpio-davinci.txt

[RFC RESEND PATCH v2 0/4] arm64: dts: ti: am6: Add gpio nodes

K3 AM6 platform has 2 instances of gpio banks on main domain and 1 instance on wakeup domin. All are capable of generating banked interrupts. This series also adds 2 goio_keys nodes connected to SW6 SW5 switches and tested for gpio_keys interrupts. The series depends on:

[RFC RESEND PATCH v2 2/4] arm64: dts: ti: am6-wakeup: Add gpio node

Add gpio0 node under wakeup domain. This has 56 gpios and all are capable of generating banked interrupts. Signed-off-by: Keerthy --- arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++ 1 file changed, 15 insertions(+) diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi

Re: [PATCH v6 3/5] regulator: lm363x: Add support for LM36274

On Wed 2019-06-05 07:56:32, Dan Murphy wrote: > Adding regulator support for the LM36274 backlight driver. > This device can leverage this existing code as the functionality > and registers are common enough between the LM36274 and the LM363x > series of devices. > > Signed-off-by: Dan Murphy >

Re: single copy atomicity for double load/stores on 32-bit systems

Hi Paul, On Thu, Jun 6, 2019 at 11:43 AM Paul E. McKenney wrote: > On Tue, Jun 04, 2019 at 09:41:04AM +0200, Geert Uytterhoeven wrote: > > On Mon, Jun 3, 2019 at 10:14 PM Paul E. McKenney > > wrote: > > > On Mon, Jun 03, 2019 at 06:08:35PM +, Vineet Gupta wrote: > > > > On 5/31/19 1:21 AM,

<    2   3   4   5   6   7   8   9   10   >