Re: [PATCH v2] platform/x86: wmi: fix potential null pointer dereference

On Wed, Jan 30, 2019 at 5:15 PM Mattias Jacobsson <2...@mok.nu> wrote: > > In the function wmi_dev_match() the variable id is dereferenced without > first performing a NULL check. The variable can for example be NULL if > a WMI driver is registered without specifying the id_table field in > struct

Re: [patch 0/2] genirq, proc: Speedup /proc/stat interrupt statistics

On 01/30/2019 07:31 AM, Thomas Gleixner wrote: > Waiman reported that on large systems with a large amount of interrupts the > readout of /proc/stat takes a long time to sum up the interrupt > statistics. In principle this is not a problem. but for unknown reasons > some enterprise quality software

Re: [v7 3/3] dt-bindings: msm/disp: Introduce interconnect bindings for MDSS on SDM845

On Thu, 24 Jan 2019 10:39:52 +0530, Jayant Shekhar wrote: > Add interconnect properties such as interconnect provider specifier > , the edge source and destination ports which are required by the > interconnect API to configure interconnect path for MDSS. > > Changes in v2: > - None > > Cha

Re: [PATCH v2] sched/fair: Fix insertion in rq->leaf_cfs_rq_list

On Wed, 30 Jan 2019 at 14:40, Peter Zijlstra wrote: > > > static inline void list_del_leaf_cfs_rq(struct cfs_rq *cfs_rq) > @@ -352,7 +354,12 @@ static inline void list_del_leaf_cfs_rq(struct cfs_rq > *cfs_rq) > } > } > > -/* Iterate through all leaf cfs_rq's on a runqueue: */ > +static

Re: [PATCH v3 1/4] dt-bindings: Add vendor prefix for "GlobalTop Technology, Inc."

On Mon, 28 Jan 2019 17:37:58 +0100, Loys Ollivier wrote: > Add globaltop vendor definition. > > Signed-off-by: Loys Ollivier > --- > > v3: No changes > > v2: Alphabetical order > > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file changed, 1 insertion(+) > Please add Ack

Re: [PATCH next] fs/splice: iter_to_pipe -- Use PIPE_DEF_BUFFERS instead of hardcoded number

On Wed, Jan 30, 2019 at 03:42:45PM +, Al Viro wrote: > On Wed, Jan 30, 2019 at 06:39:11PM +0300, Cyrill Gorcunov wrote: > > And use ARRAY_SIZE for easier code modification if we ever need in future. > > Umm... Why PIPE_DEF_BUFFERS, though? Because it's a constant from more or > less the same

Re: [PATCH v3 3/3] platform/x86: wmi: use MODULE_DEVICE_TABLE() instead of MODULE_ALIAS()

On Wed, Jan 30, 2019 at 5:15 PM Mattias Jacobsson <2...@mok.nu> wrote: > > WMI drivers can if they have specified an array of struct wmi_device_id > use the MODULE_DEVICE_TABLE() macro to automatically generate the > appropriate MODULE_ALIAS() output. Thus avoiding to keep both the array > of struc

Re: [PATCH 4/5] virtio: Introduce virtio_max_dma_size()

Hi Tom, On Wed, Jan 30, 2019 at 03:10:29PM +, Lendacky, Thomas wrote: > On 1/29/19 2:43 AM, Joerg Roedel wrote: > > +size_t virtio_max_dma_size(struct virtio_device *vdev) > > +{ > > + size_t max_segment_size = SIZE_MAX; > > + > > + if (vring_use_dma_api(vdev)) > > + max_segment

Re: [RFC PATCH 3/5] mm/vma: add support for peer to peer to device vma

On Wed, Jan 30, 2019 at 09:00:06AM +0100, Christoph Hellwig wrote: > On Wed, Jan 30, 2019 at 04:18:48AM +, Jason Gunthorpe wrote: > > Every attempt to give BAR memory to struct page has run into major > > trouble, IMHO, so I like that this approach avoids that. > > Way less problems than not h

Re: [PATCH] PCI: Mediatek: Use resource_size function on resource object

On Wed, Jan 02, 2019 at 02:03:53PM +0800, honghui.zh...@mediatek.com wrote: > From: Honghui Zhang > > drivers/pci/pcie-mediatek.c:720:13-16: WARNING: Suspicious code. > resource_size is maybe missing with mem > > Generated by: scripts/coccinelle/api/resource_size.cocci > > Signed-off-by: Hongh

Re: [PATCH v2 04/14] dt-bindings: mailbox: qcom: Add clock-name optional property

On Mon, 28 Jan 2019 19:32:51 +0100, Jorge Ramirez-Ortiz wrote: > When the APCS clock is registered (platform dependent), it retrieves > its parent names from hardcoded values in the driver. > > The following commit allows the DT node to provide such clock names to > the platform data based clock d

Re: [PATCH v3 2/4] dt-bindings: gnss: add mediatek binding

On Mon, Jan 28, 2019 at 05:37:59PM +0100, Loys Ollivier wrote: > Add binding for Mediatek-based GNSS receivers. > > Signed-off-by: Loys Ollivier > --- > > v3: > Removed the I2C and SPI interfaces references. > Removed the "mediatek,mt3339" compatible line. > Added the optional propertied (reset,

Re: [PATCH] ARM: socfpga: fix base address of SDR controller

On 1/30/19 12:00 AM, Simon Goldschmidt wrote: > + Marek (as I really want to keep the dts in Linux and U-Boot in sync) > On Wed, Jan 30, 2019 at 1:16 AM Dinh Nguyen wrote: >> >> >> >> On 1/29/19 2:08 PM, Simon Goldschmidt wrote: >>> From: Simon Goldschmidt >>> >>> The documentation for socfpga

Re: [PATCHv3 2/6] Documentation: dt: socfpga: Add S10 System Manager binding

On Mon, 28 Jan 2019 16:14:11 -0600, thor.tha...@linux.intel.com wrote: > From: Thor Thayer > > Add the device tree bindings for the Stratix10 System Manager. > > Signed-off-by: Thor Thayer > --- > v2 New compatible string and usage for Stratix10 > v3 No change > --- > .../devicetree/bindings

Re: [PATCH V11 1/4] dt-bindings: mmc: Add supports-cqe property

On Wed, 23 Jan 2019 11:30:51 -0800, Sowjanya Komatineni wrote: > Add supports-cqe optional property for MMC hosts. > > This property is used to identify the specific host controller > supporting command queue. > > Signed-off-by: Sowjanya Komatineni > Reviewed-by: Thierry Reding > --- > [V11]:

Re: [PATCH v3] mfd: tqmx86: IO controller with i2c, wachdog and gpio

> > Hi Lee > > > > I posted a new version. > > > > Your email indicates you are using Mutt: > > > > >User-Agent: Mutt/1.9.4 (2018-02-28) > > > > Which is also what i use. I've never had issues with signatures like > > this. I also cannot find any documentation as to how you configure > > mutt r

Re: WARNING in __flush_work

On 1/30/19 6:56 AM, Tetsuo Handa wrote: > From fd653e8dd0d5368cd0cd9ccd89cf3001e4584f8a Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Wed, 30 Jan 2019 22:21:45 +0900 > Subject: [PATCH] block: pass no-op callback to INIT_WORK(). > > syzbot is hitting flush_work() warning caused by commit 4

Re: [PATCH] blk-mq: fix a hung issue when fsync

On 1/30/19 2:01 AM, Jianchao Wang wrote: > Florian reported a io hung issue when fsync(). It should be > triggered by following race condition. > > data + post flush a flush > > blk_flush_complete_seq > case REQ_FSEQ_DATA > blk_flush_queue_rq > issued to driver blk_mq_dispa

Re: ipmi_msghandler crashes in 4.19

We're rolling out 4.19.18 across the fleet. Hopefully, we'll not see it anymore, but if we do, we'll let you know. Regards, Ignat On Tue, Jan 29, 2019 at 10:29 AM Greg KH wrote: > > On Tue, Jan 15, 2019 at 10:36:42AM -0800, Ivan Babrou wrote: > > Hey, > > > > We've upgraded some machines from 4.

Re: [PATCH v2 -next] tty: ipwireless: Fix potential NULL pointer dereference

On 30. 01. 19, 11:30, YueHaibing wrote: > There is a potential NULL pointer dereference in case > alloc_ctrl_packet() fails and returns NULL. > > Fixes: 099dc4fb6265 ("ipwireless: driver for PC Card 3G/UMTS modem") > Signed-off-by: YueHaibing > --- > v2: fix return value > --- > drivers/tty/ipwi

[PATCH 0/3] SMSC USB333x ULPI USB PHY Support

This series adds support for the SMSC USB333x ULPI USB PHY. The USB333x usually does not require particular configuration as it implements generic registers described in the ULPI specification. However, specific use cases require tweaking some bits. In our case, VBUS is not connected to anything

Re: [patch 1/2] genriq: Avoid summation loops for /proc/stat

On 01/30/2019 07:31 AM, Thomas Gleixner wrote: > Waiman reported that on large systems with a large amount of interrupts the > readout of /proc/stat takes a long time to sum up the interrupt > statistics. In principle this is not a problem. but for unknown reasons > some enterprise quality software

Re: [PATCH v2] USB: Disable USB2 LPM at shutdown

> On Jan 30, 2019, at 16:21, Greg KH wrote: > > On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote: >> The QCA Rome USB Bluetooth controller has several issues once LPM gets >> enabled: >> - Fails to get enumerated in coldboot. [1] >> - Drains more power (~ 0.2W) when the system is

[PATCH V7 1/5] i2c: tegra: Sort all the include headers alphabetically

This patch sorts all the include headers alphabetically for the I2C tegra driver Signed-off-by: Sowjanya Komatineni --- [V3/V4/V5/V7] : Removed unsued headers in tegra I2C [V2] : Added this in V2 to sort the headers in tegra I2C drivers/i2c/busses/i2c-tegra.c | 19 --- 1 file

[PATCH V7 2/5] i2c: tegra: Add Bus Clear Master Support

Bus clear feature of tegra i2c controller helps to recover from bus hang when i2c master loses the bus arbitration due to the slave device holding SDA LOW continuously for some unknown reasons. Per I2C specification, the device that held the bus LOW should release it within 9 clock pulses. During

Re: [RFC PATCH 3/5] mm/vma: add support for peer to peer to device vma

On Wed, Jan 30, 2019 at 10:33:39AM +, Koenig, Christian wrote: > Am 30.01.19 um 09:02 schrieb Christoph Hellwig: > > On Tue, Jan 29, 2019 at 08:58:35PM +, Jason Gunthorpe wrote: > >> On Tue, Jan 29, 2019 at 01:39:49PM -0700, Logan Gunthorpe wrote: > >> > >>> implement the mapping. And I don

Re: [PATCH] PCI: Mediatek: Use resource_size function on resource object

On Wed, Jan 30, 2019 at 12:33:47PM +, Lorenzo Pieralisi wrote: > On Wed, Jan 02, 2019 at 02:03:53PM +0800, honghui.zh...@mediatek.com wrote: > > From: Honghui Zhang > > > > drivers/pci/pcie-mediatek.c:720:13-16: WARNING: Suspicious code. > > resource_size is maybe missing with mem > > > > G

[PATCH 3/3] MAINTAINERS: Add entry for the SMSC USB333x ULPI USB PHY

Add a new MAINTAINERS entry for this ULPI USB PHY. Signed-off-by: Paul Kocialkowski --- MAINTAINERS | 6 ++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index d2d5caf789c7..33f1538b30c0 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -14146,6 +14146,12 @@ L: linu

[PATCH 1/3] dt-bindings: phy: Add bindings for the SMSC USB333x ULPI USB PHY

Introduce the device-tree bindings for this ULPI USB PHY. Optional bindings that are not prefixed with the vendor may be relevant to other ULPI USB PHYs since they match generic ULPI registers. Signed-off-by: Paul Kocialkowski --- .../devicetree/bindings/phy/smsc-usb333x.txt | 50 ++

[PATCH 2/3] phy: Add support for the SMSC USB333x ULPI USB PHY

This is a standard ULPI USB PHY that works according to the ULPI 1.1 specification, which supports USB 2.0 OTG. This drivers mostly allows settong a few generic bits that are specific to the use case, in addition to handling the reference clock and reset GPIO. In particular, it allows configuring

Re: [PATCH v3 2/3] platform/x86: wmi: add WMI support to MODULE_DEVICE_TABLE()

On Wed, Jan 30, 2019 at 5:15 PM Mattias Jacobsson <2...@mok.nu> wrote: > > The kernel provides the macro MODULE_DEVICE_TABLE() where driver authors > can specify their device type and their array of device_ids and thereby > trigger the generation of the appropriate MODULE_ALIAS() output. This is >

[PATCH V7 4/5] i2c: tegra: Update transfer timeout

Tegra194 allows max of 64K bytes and Tegra186 and prior allows max of 4K bytes of transfer per packet. one sec timeout is not enough for transfers more than 10K bytes at STD bus rate. This patch updates I2C transfer timeout based on the transfer size and I2C bus rate to allow enough time during m

Applied "regulator: max77650: Fix include files" to the regulator tree

The patch regulator: max77650: Fix include files has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

[PATCH V7 3/5] i2c: tegra: Add DMA Support

This patch adds DMA support for Tegra I2C. Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for transfer size of the max FIFO depth and DMA mode is used for transfer size higher than max FIFO depth to save CPU overhead. PIO mode needs full intervention of CPU to fill or empty FIFO's an

[PATCH V7 5/5] i2c: tegra: Add I2C interface timing support

This patch adds I2C interface timing registers support for proper bus rate configuration along with meeting the i2c spec setup and hold times based on the tuning performed on Tegra210, Tegra186 and Tegra194 platforms. I2C_INTERFACE_TIMING_0 register contains TLOW and THIGH field and Tegra I2C cont

[PATCH v2 1/9] platform/x86: intel_cht_int33fe: Prepare for better mux naming scheme

Adding new connections with for the muxes with new identifiers. The old connection are left in for now. Signed-off-by: Heikki Krogerus --- drivers/platform/x86/intel_cht_int33fe.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/platform/x86/intel_cht_int33fe.c

[PATCH v2 2/9] usb: typec: Rationalize the API for the muxes

Since with accessory modes there is no need for additional identification when requesting a handle to the mux, we can replace the second parameter that is passed to the typec_mux_get() function with a pointer to alternate mode description structure, and simply passing NULL with accessory modes. Th

[PATCH v2 4/9] device connection: Add fwnode member to struct device_connection

This will prepare the device connection API for connections described in firmware. Signed-off-by: Heikki Krogerus --- include/linux/device.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/linux/device.h b/include/linux/device.h index 5663003a95eb..1fb077f5a936 100644 --- a/inc

[PATCH v2 0/9] device connection: Add support for device graphs

Hi, This is the second version of this series. On top the two code style improvements requested by Andy, I also renamed the connection identifiers used with the USB Type-C muxes for something that I felt are better, especially after we start using them to name reference device properties in fwnode

[PATCH v2 8/9] device connection: Prepare support for firmware described connections

When the connections are defined in firmware, struct device_connection will have the fwnode member pointing to the device node (struct fwnode_handle) of the requested device. The endpoint member for the device names will not be used at all in that case. Signed-off-by: Heikki Krogerus --- drivers

[PATCH v2 5/9] usb: typec: mux: Find the muxes by also matching against the device node

When the connections are defined in firmware, struct device_connection will have the fwnode member pointing to the device node (struct fwnode_handle) of the requested device, and the endpoint will not be used at all in that case. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/mux.c | 86 ++

[PATCH v2 6/9] usb: roles: Find the muxes by also matching against the device node

When the connections are defined in firmware, struct device_connection will have the fwnode member pointing to the device node (struct fwnode_handle) of the requested device, and the endpoint will not be used at all in that case. Signed-off-by: Heikki Krogerus --- drivers/usb/roles/class.c | 21

[PATCH v2 9/9] device connection: Find device connections also from device graphs

If connections between devices are described in OF graph or ACPI device graph, we can find them by using the fwnode_graph_*() functions. Signed-off-by: Heikki Krogerus --- drivers/base/devcon.c | 38 +++--- 1 file changed, 35 insertions(+), 3 deletions(-) diff --

Re: [PATCH] PCI: Mediatek: Use resource_size function on resource object

On Wed, Jan 02, 2019 at 02:03:53PM +0800, honghui.zh...@mediatek.com wrote: > From: Honghui Zhang > > drivers/pci/pcie-mediatek.c:720:13-16: WARNING: Suspicious code. > resource_size is maybe missing with mem > > Generated by: scripts/coccinelle/api/resource_size.cocci > > Signed-off-by: Hongh

Re: [PATCH v2 0/2] Fix crash in cper_estatus_check()

On Mon, Jan 28, 2019 at 5:06 AM Ross Lagerwall wrote: > > v2 changes: > - Address Boris's comments. > > --- > > I recently encountered a crash in cper_estatus_check() when called by > bert_init(). Patches follow to fix the problem. Note that I cannot fully > test the patches since the hardware err

[PATCH v2 7/9] usb: typec: Find the ports by also matching against the device node

When the connections are defined in firmware, struct device_connection will have the fwnode member pointing to the device node (struct fwnode_handle) of the requested device, and the endpoint will not be used at all in that case. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/class.c | 24

[PATCH v2 3/9] platform/x86: intel_cht_int33fe: Remove old style mux connections

The new mux connection naming scheme is now in use, so dropping the connections still using the old names. From now on the same connection description named "mode-switch" is used with both the port and the alternate modes, so on CHT the DP alt mode will use the same connection as the port to get a

Re: [PATCH] mic: vop: Fix broken virtqueues

On Tue, 2019-01-29 at 11:22 +0100, Vincent Whitchurch wrote: > VOP is broken in mainline since commit 1ce9e6055fa0a9043 ("virtio_ring: > introduce packed ring support"); attempting to use the virtqueues leads > to various kernel crashes. I'm testing it with my not-yet-merged > loopback patches, bu

[PATCH 0/2] drm/vkms: Bugfix for igt-tests

This patchset contains patches to fix the extra frame bug on kms_flip igt-test. First patch solves the extra vblank frame that breaks many tests on kms_flip and second patch solves the race condition caused by the solution added in the first one. Shayenne Moura (2): drm/vkms: Bugfix extra vblan

[PATCH 1/2] drm/vkms: Bugfix extra vblank frame

kms_flip tests are breaking on vkms when simulate vblank because vblank event sequence count returns one extra frame after arm vblank event to make a page flip. When vblank interrupt happens, userspace processes the vblank event and issues the next page flip command. Kernel calls queue_work to cal

Re: [RFC v7 2/5] dt-bindings: pstore-block: new support for blkoops

On Wed, Jan 23, 2019 at 08:05:13PM +0800, liaoweixiong wrote: > Create DT binding document for blkoops. > > Signed-off-by: liaoweixiong > --- > .../devicetree/bindings/pstore-block/blkoops.txt | 32 > ++ /bindings/pstore/... I wouldn't call it blkoops either. I believe ra

[PATCH 2/2] drm: vkms: Bugfix racing hrtimer vblank handle

When the vblank irq happens, kernel time subsystem executes `vkms_vblank_simulate`. In parallel or not, it prepares all stuff necessary to the next vblank with arm, and it must flush these stuff before the next vblank irq. However, vblank counter is ahead when arm is executed in parallel with handl

Re: [PATCH] x86/kvmclock: set offset for kvm unstable clock

On 28/01/19 17:22, Jon DeVree wrote: > Thanks a bunch Pavel, patch works great for me on 5.0-rc4. I also > backported it to 4.19.18 and tested it there. Should this be CC'ed to > stable@ as well? Yes, I've queued the patch and added the stable tag. Thanks, Paolo

Re: [PATCH] kvm: Use struct_size() in kmalloc()

On 29/01/19 18:20, Gustavo A. R. Silva wrote: > Hi all, > > Friendly ping: > > Who can take this? I cannot find the original message in my inbox, but I've queued it from the quote below. Thanks, Paolo > Thanks > -- > Gustavo > > On 1/4/19 10:29 AM, Gustavo A. R. Silva wrote: >> One of the mo

Re: [PATCH] svm: Fix AVIC DFR and LDR handling

On 29/01/19 09:08, Suthikulpanit, Suravee wrote: > +static void avic_inv_logical_id_entry(struct kvm_vcpu *vcpu) > +{ > + struct vcpu_svm *svm = to_svm(vcpu); > + bool flat = svm->dfr_reg == APIC_DFR_FLAT; > + u32 *entry = avic_get_logical_id_entry(vcpu, svm->ldr_reg, flat); > + > +

Re: [PATCH] rtc: rv3028: new driver

On 1/30/19 4:00 PM, Alexandre Belloni wrote: > Add a driver for the MicroCrystal RV-3028. Some additional information in the commit message won't hurt. > Signed-off-by: Alexandre Belloni > --- > Documentation/devicetree/bindings/rtc/rtc.txt | 1 + > drivers/rtc/Kconfig

Re: [PATCH] kvm: Use struct_size() in kmalloc()

On 1/30/19 10:08 AM, Paolo Bonzini wrote: > On 29/01/19 18:20, Gustavo A. R. Silva wrote: >> Hi all, >> >> Friendly ping: >> >> Who can take this? > > I cannot find the original message in my inbox, but I've queued it from > the quote below. > Thank you, Paolo. -- Gustavo

[PATCH resend 3/3] hwmon: (lm85) add support for LM96000 high frequencies

This chip expands the freqency field from 3 to 4 bits, to add more frequencies in the 22.5 to 30 kHz ranges. Signed-off-by: Jeremy Gebben --- Documentation/hwmon/lm85 | 3 +++ drivers/hwmon/lm85.c | 9 + 2 files changed, 12 insertions(+) diff --git a/Documentation/hwmon/lm85 b/Docum

[PATCH resend 2/3] hwmon: (lm85) Document the LM96000 as supported

It has been supported as a generic lm85 for quite some time. Signed-off-by: Jeremy Gebben --- Documentation/hwmon/lm85 | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/hwmon/lm85 b/Documentation/hwmon/lm85 index 7c49feaa79d2..9f3a945d1b80 100644 --- a/Docume

[PATCH resend 1/3] hwmon: (lm85) remove freq_map size hardcodes

Allow support for chips that support more than 8 frequencies. The size still must be a power of two. Signed-off-by: Jeremy Gebben --- drivers/hwmon/lm85.c | 25 +++-- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/drivers/hwmon/lm85.c b/drivers/hwmon/lm85.c

Re: [PATCH v6 5/6] dt-bindings: pinctrl: mt8183: add binding document

On Thu, Jan 24, 2019 at 04:07:19PM +0800, Erin Lo wrote: > From: Zhiyong Tao > > The commit adds mt8183 compatible node in binding document. > > Signed-off-by: Zhiyong Tao > Signed-off-by: Erin Lo > --- > .../devicetree/bindings/pinctrl/pinctrl-mt8183.txt | 115 > + > 1 f

Re: [PATCH v3 0/4] uaccess: Add unsafe accessors for arm64

Hi, Gentle ping for patches 3 and 4. Thanks, Julien On 15/01/2019 13:58, Julien Thierry wrote: > Hi, > > First version of this series[1] was briefly in linux-next but had to be > reverted due to a bug where schedule would end up being called while > user_access was active[2]. > > After clarif

Re: [RFD] A mount api that notices previous mounts

On 1/30/2019 4:47 AM, Eric W. Biederman wrote: > ebied...@xmission.com (Eric W. Biederman) writes: > >> ebied...@xmission.com (Eric W. Biederman) writes: >> >>> Casey Schaufler writes: Are you taking the LSM specific mount options into account? >>> In the design yes, and I allow setting them.

Re: [PATCH 0/3] hwmon: (lm85) add LM96000 high freqency pwm support

On Tue, Jan 29, 2019 at 4:38 PM Guenter Roeck wrote: > > On Tue, Jan 29, 2019 at 02:29:17PM -0700, Jeremy Gebben wrote: > > Hi, > > > > This patch adds support for the PWM frequencies from 22.5 to 30 kHz > > available on the LM96000. > > > > It looks like this chip has been supported for a long ti

Re: [PATCH] mtd: rawnand: denali_dt: remove single anonymous clock support

Hi Miquel, Let me review this today. Thanks, Dinh On 1/28/19 4:20 AM, Miquel Raynal wrote: > Hi Dinh, > > Masahiro Yamada wrote on Wed, 16 Jan > 2019 10:27:11 +0900: > >> (+CC Dinh Nguyen) >> >> On Tue, Jan 15, 2019 at 5:22 PM Miquel Raynal >> wrote: >>> >>> Hi Masahiro, >>> >>> Masahiro Ya

Re: [PATCH v6 6/6] arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile

On Thu, Jan 24, 2019 at 04:07:20PM +0800, Erin Lo wrote: > From: Ben Ho > > Add basic chip support for Mediatek 8183, include > pinctrl file, uart node with correct uart clocks, pwrap device > > Add clock controller nodes, include topckgen, infracfg, > apmixedsys and subsystem. > > Signed-off-b

Re: [PATCH 1/1] iommu/vt-d: Leave scalable mode default off

On Thu, Jan 24, 2019 at 10:31:32AM +0800, Lu Baolu wrote: > Commit 765b6a98c1de3 ("iommu/vt-d: Enumerate the scalable > mode capability") enables VT-d scalable mode if hardware > advertises the capability. As we will bring up different > features and use cases to upstream in different patch > serie

Re: [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels

On 01/30/2019 09:07 AM, Peter Zijlstra wrote: >> Waiman Long (4): >> locking/qspinlock: Handle > 4 slowpath nesting levels >> locking/qspinlock_stat: Track the no MCS node available case > I've taken these two, > >> locking/qspinlock_stat: Introduce a generic lockevent counting APIs >> lock

Re: [PATCH v2 2/7] scsi: libsas: only clear phy->in_shutdown after shutdown event done

On 30/01/2019 08:24, Jason Yan wrote: When the event queue is full of phy up and down events and reached the threshold, we will queue a shutdown-event, and set phy->in_shutdown so that we will not queue a shutdown-event again. But before the shutdown-event can be executed, every phy-down event wi

Re: [PATCH] iommu/amd: print reason for iommu_map_page failure in map_sg

On Mon, Jan 28, 2019 at 05:59:37PM -0700, Jerry Snitselaar wrote: > Since there are multiple possible failures in iommu_map_page > it would be useful to know which case is being hit when the > error message is printed in map_sg. While here, fix up checkpatch > complaint about using function name in

Re: [PATCH v3] async: Add cmdline option to specify drivers to be async probed

On 1/29/19 11:23 PM, Feng Tang wrote: > Asynchronous driver probing can help much on kernel fastboot, and > this option can provide a flexible way to optimize and quickly verify > async driver probe. > > Also it will help in below cases: > * Some driver actually covers several families of HWs, som

Re: [PATCH] virtio_net: Introduce extended RSC feature

On Wed, Jan 30, 2019 at 09:42:07AM +0200, Yuri Benditovich wrote: > > > On Tue, Jan 29, 2019 at 6:07 PM Michael S. Tsirkin wrote: > > On Tue, Jan 29, 2019 at 02:52:36PM +0200, Yuri Benditovich wrote: > > VIRTIO_NET_F_RSC_EXT feature bit indicates that the device > > is able to provi

Re: [PATCH v2] iommu/vt-d: Implement dma_[un]map_resource()

On Tue, Jan 22, 2019 at 02:30:45PM -0700, Logan Gunthorpe wrote: > Currently the Intel IOMMU uses the default dma_[un]map_resource() > implementations does nothing and simply returns the physical address > unmodified. > > However, this doesn't create the IOVA entries necessary for addresses > mapp

Re: [PATCH] svm: Fix improper check when deactivate AVIC

On 29/01/19 09:09, Suthikulpanit, Suravee wrote: > The function svm_refresh_apicv_exec_ctrl() always returning prematurely > as kvm_vcpu_apicv_active() always return false when calling from > the function arch/x86/kvm/x86.c:kvm_vcpu_deactivate_apicv(). > This is because the apicv_active is set to f

[PATCH v2] arm64: dts: qcom: msm8998: Add rpmcc node

Add MSM8998 Resource Power Manager Clock Controller DT node. Reviewed-by: Jeffrey Hugo Reviewed-by: Bjorn Andersson Signed-off-by: Marc Gonzalez --- Detach this patch from UFS series --- arch/arm64/boot/dts/qcom/msm8998.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/

Re: [PATCH v6 12/13] KVM: s390: add gib_alert_irq_handler()

On 29/01/2019 16:29, Michael Mueller wrote: On 29.01.19 14:26, Halil Pasic wrote: On Thu, 24 Jan 2019 13:59:38 +0100 Michael Mueller wrote: The patch implements a handler for GIB alert interruptions on the host. Its task is to alert guests that interrupts are pending for them. A GIB alert

Re: [PATCH next] fs/splice: iter_to_pipe -- Use PIPE_DEF_BUFFERS instead of hardcoded number

On Wed, Jan 30, 2019 at 06:48:51PM +0300, Cyrill Gorcunov wrote: > On Wed, Jan 30, 2019 at 03:42:45PM +, Al Viro wrote: > > On Wed, Jan 30, 2019 at 06:39:11PM +0300, Cyrill Gorcunov wrote: > > > And use ARRAY_SIZE for easier code modification if we ever need in future. > > > > Umm... Why PIPE

Re: [PATCH] mic: vop: Fix broken virtqueues

On Wed, Jan 30, 2019 at 08:29:57AM -0800, Sudeep Dutt wrote: > On Tue, 2019-01-29 at 11:22 +0100, Vincent Whitchurch wrote: > > VOP is broken in mainline since commit 1ce9e6055fa0a9043 ("virtio_ring: > > introduce packed ring support"); attempting to use the virtqueues leads > > to various kernel c

Re: [v5 1/2] dt-bindings: ahci-fsl-qoriq: add lx2160a chip name to the list

On Fri, 25 Jan 2019 08:10:12 +, Peng Ma wrote: > Add lx2160a compatible to bindings documentation. > > Signed-off-by: Peng Ma > --- > changed for V5: > - change the lxx2160a to lx2160a > > .../devicetree/bindings/ata/ahci-fsl-qoriq.txt |2 +- > 1 files changed, 1 insertions(+)

[PATCH] cpuidle: poll_state: Fix default time limit.

The default time is declared in units of microsecnds, but is used as nano seconds, resulting in significant accounting errors for idle state 0 time when all idle states deeper than 0 are disabled. Under these unusual conditions, we don't really care about the poll time limit anyhow. Signed-off-by

[PATCH v2] mic: vop: Fix broken virtqueues

VOP is broken in mainline since commit 1ce9e6055fa0a9043 ("virtio_ring: introduce packed ring support"); attempting to use the virtqueues leads to various kernel crashes. I'm testing it with my not-yet-merged loopback patches, but even the in-tree MIC hardware cannot work. The problem is not in t

Re: [PATCH] ARM: socfpga: fix base address of SDR controller

Am 30.01.2019 um 16:50 schrieb Dinh Nguyen: On 1/30/19 12:00 AM, Simon Goldschmidt wrote: + Marek (as I really want to keep the dts in Linux and U-Boot in sync) On Wed, Jan 30, 2019 at 1:16 AM Dinh Nguyen wrote: On 1/29/19 2:08 PM, Simon Goldschmidt wrote: From: Simon Goldschmidt The d

Re: [PATCH v2] sysctl: Add panic-fatal-signals

On Wed, Jan 30, 2019 at 04:02:36PM +0100, Richard Weinberger wrote: > Hmm, why can't this be a core dump helper? > Such as: > > #!/bin/sh > # Usage: > # echo "|/root/crash.sh %p %e %s" > /proc/sys/kernel/core_pattern > > PID="$1" > COMM="$2" > SIGNAL="$3" > > echo "$COMM ($PID) died by signal $S

Re: WARNING in apparmor_secid_to_secctx

On Wed, Jan 30, 2019 at 6:45 AM Dmitry Vyukov wrote: > > On Tue, Jan 29, 2019 at 12:32 PM Tetsuo Handa > wrote: > > > > On 2018/09/06 19:59, Dmitry Vyukov wrote: > > > On Wed, Sep 5, 2018 at 7:37 PM, Casey Schaufler > > > wrote: > > >> On 9/5/2018 4:08 AM, Dmitry Vyukov wrote: > > >>> Thanks! I

Re: [PATCH 2/2] iommu/amd: Remove clear_flush_young notifier

On Wed, Jan 30, 2019 at 01:57:58PM +0800, Peter Xu wrote: > AMD IOMMU driver is using the clear_flush_young() to do cache flushing > but that's actually already covered by invalidate_range(). Remove the > extra notifier and the chunks. > > Signed-off-by: Peter Xu Applied to x86/amd, thanks.

Re: [PATCH] PCI: Mediatek: Use resource_size function on resource object

On Wed, Jan 30, 2019 at 09:58:53AM -0600, Bjorn Helgaas wrote: > On Wed, Jan 30, 2019 at 12:33:47PM +, Lorenzo Pieralisi wrote: > > On Wed, Jan 02, 2019 at 02:03:53PM +0800, honghui.zh...@mediatek.com wrote: > > > From: Honghui Zhang > > > > > > drivers/pci/pcie-mediatek.c:720:13-16: WARNING:

Re: [PATCH 1/2] iommu/vt-d: Remove change_pte notifier

On Wed, Jan 30, 2019 at 01:57:57PM +0800, Peter Xu wrote: > The change_pte() interface is tailored for PFN updates, while the > other notifier invalidate_range() should be enough for Intel IOMMU > cache flushing. Actually we've done similar thing for AMD IOMMU > already in 8301da53fbc1 ("iommu/amd

[RESEND PATCH v2] arm64: dts: qcom: msm8998: Add rpmcc node

Add MSM8998 Resource Power Manager Clock Controller DT node. Reviewed-by: Jeffrey Hugo Reviewed-by: Bjorn Andersson Signed-off-by: Marc Gonzalez --- Detach this patch from UFS series Resend because SMTP server was blacklisted. --- arch/arm64/boot/dts/qcom/msm8998.dtsi | 6 ++ 1 file change

ARM64 suggestion: reduce the compat address limit (currently 0x100000000)?

Hi! At the moment, compat tasks running on ARM64 can allocate memory up to 0x1 (TASK_SIZE_32). Testing on an Android device (with an admittedly somewhat old kernel): === $ cat mmap_filler.c #include #include #include #include #include int main(void) { unsigned long size = 1

[PATCH v2 0/5] introduce unaligned access under a Kconfig option

As of today we enable unaligned access unconditionally on ARCv2. Lets move it under Kconfig option and use it actively in SW if it is enabled. While I'm at it fix and optimise ARCv2 memcpy implementaion. Changes v1->v2: * Rebase onto last ARC changes. * Don't add dummy symbol to ARC Kconfig *

Re: [PATCH v4 2/3] ASoC: add fsl_audmix DT binding documentation

On Fri, Jan 25, 2019 at 11:43:16AM -0800, Nicolin Chen wrote: > On Tue, Jan 22, 2019 at 11:14:27AM +, Viorel Suman wrote: > > Add the DT binding documentation for NXP Audio Mixer > > CPU DAI driver. > > > > Signed-off-by: Viorel Suman > > --- > > .../devicetree/bindings/sound/fsl,audmix.txt

[PATCH v2 1/5] ARCv2: lib: memcpy: fix doing prefetchw outside of buffer

ARCv2 optimized memcpy uses PREFETCHW instruction for prefetching the next cache line but doesn't ensure that the line is not past the end of the buffer. PRETECHW changes the line ownership and marks it dirty, which can cause data corruption if this area is used for DMA IO. Fix the issue by avoidi

[PATCH v2 4/5] ARCv2: LIB: MEMCPY: fixed and optimised routine

Optimise code to use efficient unaligned memory access which is available on ARCv2. This allows us to really simplify memcpy code and speed up the code one and a half times (in case of unaligned source or destination). Signed-off-by: Eugeniy Paltsev --- arch/arc/lib/Makefile | 8

[PATCH v2 5/5] ARC: boot log: print unaligned memory access details

This now prints both HW feature status (exists, enabled / disabled) and SW status (used / not used). Signed-off-by: Eugeniy Paltsev --- arch/arc/kernel/setup.c | 13 ++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/arch/arc/kernel/setup.c b/arch/arc/kernel/setup.c ind

[PATCH v2 3/5] ARCv2: use unaligned access in SW

Select HAVE_EFFICIENT_UNALIGNED_ACCESS and allow GCC to generate unaligned data if we enable enable unaligned access in HW. Signed-off-by: Eugeniy Paltsev --- arch/arc/Kconfig | 1 + arch/arc/Makefile | 6 ++ 2 files changed, 7 insertions(+) diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig

[PATCH v2 2/5] ARCv2: introduce unaligned access under a Kconfig option

As of today we enable unaligned access unconditionally on ARCv2. Lets move it under Kconfig option so we can disable it in case of using HW configuration which lacks of it. Signed-off-by: Eugeniy Paltsev --- arch/arc/Kconfig | 8 arch/arc/include/asm/irqflags-arcv2

Re: [PATCH v2] arm64: dts: Remove inconsistent use of 'arm,armv8' compatible string

On Mon, Jan 14, 2019 at 6:45 PM Rob Herring wrote: > > The 'arm,armv8' compatible string is only for software models. It adds > little value otherwise and is inconsistently used as a fallback on some > platforms. Remove it from those platforms. Applied on arm/dt, thanks! Arnd

Re: [PATCH] drm/savage: mark expected switch fall-throughs

On Tue, Jan 29, 2019 at 02:20:06PM -0600, Gustavo A. R. Silva wrote: > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > This patch fixes the following warnings: > > drivers/gpu/drm/savage/savage_state.c:301:8: warning: this stateme

[PATCH v1 0/4] MSM8998 Multimedia Clock Controller

The multimedia clock controller (mmcc) is the main clock controller for the multimedia subsystem and is required to enable things like display and camera. The mmcc consumes a few external clocks inorder to configure the root clock generators that it controls. We can use DT to grab XO (from rpmcc)

[PATCH v1 1/4] clk: qcom: smd: Add XO clock for MSM8998

The XO clock generally feeds into other clock controllers as the parent for a lot of clock generators. Fixes: 6131dc81211c (clk: qcom: smd: Add support for MSM8998 rpm clocks) Signed-off-by: Jeffrey Hugo --- drivers/clk/qcom/clk-smd-rpm.c | 4 1 file changed, 4 insertions(+) diff --git a/d

<    1   2   3   4   5   6   7   8   9   10   >