[PATCH V4 7/7] tty: serial: lpuart: add a more accurate baud rate calculation method

On new LPUART versions, the oversampling ratio for the receiver can be changed from 4x (00011) to 32x (1) which could help us get a more accurate baud rate divider. The idea is to use the best OSR (over-sampling rate) possible. Note, OSR is typically hard-set to 16 in other LPUART

[PATCH V4 7/7] tty: serial: lpuart: add a more accurate baud rate calculation method

On new LPUART versions, the oversampling ratio for the receiver can be changed from 4x (00011) to 32x (1) which could help us get a more accurate baud rate divider. The idea is to use the best OSR (over-sampling rate) possible. Note, OSR is typically hard-set to 16 in other LPUART

[PATCH V4 0/7] tty: serial: lpuart: add imx7ulp support

The lpuart in imx7ulp is basically the same as ls1021a. It's also 32 bit width register, but unlike ls1021a, it's little endian. Besides that, imx7ulp lpuart has a minor different register layout from ls1021a that it has four extra registers (verid, param, global, pincfg) located at the beginning

[PATCH V4 1/7] tty: serial: lpuart: introduce lpuart_soc_data to represent SoC property

This is used to dynamically check the SoC specific lpuart properies. Currently only the iotype is added, it functions the same as before. With this, new chips with different iotype will be more easily added. Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc:

[PATCH V4 0/7] tty: serial: lpuart: add imx7ulp support

The lpuart in imx7ulp is basically the same as ls1021a. It's also 32 bit width register, but unlike ls1021a, it's little endian. Besides that, imx7ulp lpuart has a minor different register layout from ls1021a that it has four extra registers (verid, param, global, pincfg) located at the beginning

[PATCH V4 1/7] tty: serial: lpuart: introduce lpuart_soc_data to represent SoC property

This is used to dynamically check the SoC specific lpuart properies. Currently only the iotype is added, it functions the same as before. With this, new chips with different iotype will be more easily added. Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: Stefan Agner Cc: Mingkai Hu Cc: Yangbo Lu

[PATCH V4 3/7] tty: serial: lpuart: add little endian 32 bit register support

Use standard port->iotype to distinguish endian difference. Note as we read/write register by checking iotype dynamically, we need to initialize the iotype correctly for earlycon as well to avoid a break. Cc: Greg Kroah-Hartman Cc: Jiri Slaby

[PATCH V4 3/7] tty: serial: lpuart: add little endian 32 bit register support

Use standard port->iotype to distinguish endian difference. Note as we read/write register by checking iotype dynamically, we need to initialize the iotype correctly for earlycon as well to avoid a break. Cc: Greg Kroah-Hartman Cc: Jiri Slaby (supporter:TTY LAYER) Cc: Stefan Agner Cc: Mingkai

[PATCH V4 4/7] dt-bindings: serial: fsl-lpuart: add i.MX7ULP support

The lpuart of imx7ulp is basically the same as ls1021a. It's also 32 bit width register, but unlike ls1021a, it's little endian. Besides that, imx7ulp lpuart has a minor different register layout from ls1021a. Cc: devicet...@vger.kernel.org Cc: Greg Kroah-Hartman Cc:

[PATCH V4 4/7] dt-bindings: serial: fsl-lpuart: add i.MX7ULP support

The lpuart of imx7ulp is basically the same as ls1021a. It's also 32 bit width register, but unlike ls1021a, it's little endian. Besides that, imx7ulp lpuart has a minor different register layout from ls1021a. Cc: devicet...@vger.kernel.org Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: Stefan Agner

[PATCH V4 2/7] tty: serial: lpuart: refactor lpuart32_{read|write} prototype

Due to the original lpuart32_read/write takes no port specific information arguments, it's hard to distinguish port difference within the API. Although it works before, but not suitable anymore when adding more new chips support. So let's convert it to accept a new struct uart_port argument to

[PATCH V4 2/7] tty: serial: lpuart: refactor lpuart32_{read|write} prototype

Due to the original lpuart32_read/write takes no port specific information arguments, it's hard to distinguish port difference within the API. Although it works before, but not suitable anymore when adding more new chips support. So let's convert it to accept a new struct uart_port argument to

Re: [PATCH v11 4/6] mm: function to offer a page block on the free list

On 06/13/2017 04:54 AM, Dave Hansen wrote: On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: The hypervisor is going to throw away the contents of these pages, right? It should be

Re: [PATCH v11 4/6] mm: function to offer a page block on the free list

On 06/13/2017 04:54 AM, Dave Hansen wrote: On 06/12/2017 01:34 PM, Michael S. Tsirkin wrote: On Mon, Jun 12, 2017 at 09:42:36AM -0700, Dave Hansen wrote: On 06/12/2017 09:28 AM, Michael S. Tsirkin wrote: The hypervisor is going to throw away the contents of these pages, right? It should be

Re: [PATCH] Calling check_system_tsc_reliable before unsynchronized_tsc

在 2017/6/13 0:03, Thomas Gleixner 写道: On Thu, 8 Jun 2017, Zhenzhong Duan wrote: unsynchronized_tsc() checks value of tsc_clocksource_reliable which is set by check_system_tsc_reliable(). It's better to move check_system_tsc_reliable() at front, or else this check makes no sense. Though

Re: [PATCH] Calling check_system_tsc_reliable before unsynchronized_tsc

在 2017/6/13 0:03, Thomas Gleixner 写道: On Thu, 8 Jun 2017, Zhenzhong Duan wrote: unsynchronized_tsc() checks value of tsc_clocksource_reliable which is set by check_system_tsc_reliable(). It's better to move check_system_tsc_reliable() at front, or else this check makes no sense. Though

Re: [PATCH] tty: serial: lpuart: fix semicolon.cocci warnings

Hi Fengguang, On Tue, Jun 13, 2017 at 08:28:41AM +0800, kbuild test robot wrote: > drivers/tty/serial/fsl_lpuart.c:305:2-3: Unneeded semicolon > > > Remove unneeded semicolon. > > Generated by: scripts/coccinelle/misc/semicolon.cocci > > CC: Dong Aisheng >

Re: [PATCH] tty: serial: lpuart: fix semicolon.cocci warnings

Hi Fengguang, On Tue, Jun 13, 2017 at 08:28:41AM +0800, kbuild test robot wrote: > drivers/tty/serial/fsl_lpuart.c:305:2-3: Unneeded semicolon > > > Remove unneeded semicolon. > > Generated by: scripts/coccinelle/misc/semicolon.cocci > > CC: Dong Aisheng > Signed-off-by: Fengguang Wu

[PATCH] x86/time: Make setup_default_timer_irq() static

This function isn't used outside of time.c, so let's mark it static. Signed-off-by: Dou Liyang --- arch/x86/include/asm/setup.h | 1 - arch/x86/kernel/time.c | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/include/asm/setup.h

[PATCH] x86/time: Make setup_default_timer_irq() static

This function isn't used outside of time.c, so let's mark it static. Signed-off-by: Dou Liyang --- arch/x86/include/asm/setup.h | 1 - arch/x86/kernel/time.c | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/x86/include/asm/setup.h b/arch/x86/include/asm/setup.h

Re: [PATCH V3 1/7] tty: serial: lpuart: introduce lpuart_soc_data to represent SoC property

On Mon, Jun 12, 2017 at 08:49:36PM +0300, Andy Shevchenko wrote: > On Mon, Jun 12, 2017 at 6:37 PM, Dong Aisheng wrote: > > This is used to dynamically check the SoC specific lpuart properies. > > Currently only the iotype is added, it functions the same as before. > > With

Re: [PATCH V3 1/7] tty: serial: lpuart: introduce lpuart_soc_data to represent SoC property

On Mon, Jun 12, 2017 at 08:49:36PM +0300, Andy Shevchenko wrote: > On Mon, Jun 12, 2017 at 6:37 PM, Dong Aisheng wrote: > > This is used to dynamically check the SoC specific lpuart properies. > > Currently only the iotype is added, it functions the same as before. > > With this, new chips with

RE: [PATCH net-next 1/2] r8152: split rtl8152_resume function

Oliver Neukum [mailto:oneu...@suse.com] > Sent: Monday, June 12, 2017 8:33 PM [...] > > +   usb_submit_urb(tp->intr_urb, GFP_KERNEL); > > If you ever built a device with included storage, this can deadlock, > as you may want to wake up a device for memory that is needed to wake > up a

RE: [PATCH net-next 1/2] r8152: split rtl8152_resume function

Oliver Neukum [mailto:oneu...@suse.com] > Sent: Monday, June 12, 2017 8:33 PM [...] > > +   usb_submit_urb(tp->intr_urb, GFP_KERNEL); > > If you ever built a device with included storage, this can deadlock, > as you may want to wake up a device for memory that is needed to wake > up a

Re: [PATCH V1 05/15] spmi: pmic-arb: cleanup unrequested irqs

On 06/06, kgu...@codeaurora.org wrote: > On 2017-05-31 07:27, Stephen Boyd wrote: > >On 05/30, Kiran Gunda wrote: > >>From: Abhijeet Dharmapurikar > >> > >>We see a unmapped irqs trigger right around bootup. This could > >>likely be because the bootloader exited leaving

Re: [PATCH V1 05/15] spmi: pmic-arb: cleanup unrequested irqs

On 06/06, kgu...@codeaurora.org wrote: > On 2017-05-31 07:27, Stephen Boyd wrote: > >On 05/30, Kiran Gunda wrote: > >>From: Abhijeet Dharmapurikar > >> > >>We see a unmapped irqs trigger right around bootup. This could > >>likely be because the bootloader exited leaving the interrupts > >>in an

Re: [PATCH V1 14/15] spmi: pmic-arb: do not ack and clear peripheral interrupts in cleanup_irq

On 06/06, kgu...@codeaurora.org wrote: > On 2017-06-02 12:56, kgu...@codeaurora.org wrote: > >On 2017-05-31 23:23, Stephen Boyd wrote: > >>On 05/30, Kiran Gunda wrote: > >>>From: Subbaraman Narayanamurthy > >>> > >>>Currently, cleanup_irq() is invoked when a peripheral's

Re: [PATCH V1 14/15] spmi: pmic-arb: do not ack and clear peripheral interrupts in cleanup_irq

On 06/06, kgu...@codeaurora.org wrote: > On 2017-06-02 12:56, kgu...@codeaurora.org wrote: > >On 2017-05-31 23:23, Stephen Boyd wrote: > >>On 05/30, Kiran Gunda wrote: > >>>From: Subbaraman Narayanamurthy > >>> > >>>Currently, cleanup_irq() is invoked when a peripheral's interrupt > >>>fires and

Re: [PATCH V1 01/15] spmi: pmic_arb: block access of invalid read and writes

On 06/12, kgu...@codeaurora.org wrote: > On 2017-05-31 06:03, Stephen Boyd wrote: > >On 05/30, Kiran Gunda wrote: > >>From: Abhijeet Dharmapurikar > >> > >>The system crashes due to bad access when reading from an non > >>configured > >>peripheral and when writing to

Re: [PATCH V1 01/15] spmi: pmic_arb: block access of invalid read and writes

On 06/12, kgu...@codeaurora.org wrote: > On 2017-05-31 06:03, Stephen Boyd wrote: > >On 05/30, Kiran Gunda wrote: > >>From: Abhijeet Dharmapurikar > >> > >>The system crashes due to bad access when reading from an non > >>configured > >>peripheral and when writing to peripheral which is not owned

Re: [RESEND x3][PATCH v4] arm64: dts: hi6220: Add k3-dma and i2s/hdmi audio support

Hi John > On Mon, Jun 12, 2017 at 3:10 PM, Mark Brown wrote: > > On Mon, Jun 12, 2017 at 01:52:46PM -0700, John Stultz wrote: > > > >> + sound { > >> + compatible = "simple-audio-card"; > >> + simple-audio-card,name = "hikey-hdmi"; > > > > Now the

Re: [RESEND x3][PATCH v4] arm64: dts: hi6220: Add k3-dma and i2s/hdmi audio support

Hi John > On Mon, Jun 12, 2017 at 3:10 PM, Mark Brown wrote: > > On Mon, Jun 12, 2017 at 01:52:46PM -0700, John Stultz wrote: > > > >> + sound { > >> + compatible = "simple-audio-card"; > >> + simple-audio-card,name = "hikey-hdmi"; > > > > Now the graph card has been

Re: Ftrace vs perf user page fault statistics differences

Thank you for your response. I have included responses to your questions inline. On Mon, Jun 12, 2017 at 9:20 PM, Steven Rostedt wrote: > On Mon, 12 Jun 2017 20:20:42 -0400 > Will Hawkins wrote: > >> Dear Mr. Rostedt and Kernel community, >> >> I hope

Re: Ftrace vs perf user page fault statistics differences

Thank you for your response. I have included responses to your questions inline. On Mon, Jun 12, 2017 at 9:20 PM, Steven Rostedt wrote: > On Mon, 12 Jun 2017 20:20:42 -0400 > Will Hawkins wrote: > >> Dear Mr. Rostedt and Kernel community, >> >> I hope that this is an appropriate place to ask

Re: [RFC PATCH 1/7 v1]powerpc: Free up four PTE bits to accommodate memory keys

Ram Pai writes: > On Mon, Jun 12, 2017 at 12:27:44PM +0530, Aneesh Kumar K.V wrote: >> Ram Pai writes: >> >> > Rearrange PTE bits to free up bits 3, 4, 5 and 6 for >> > memory keys. Bit 3, 4, 5, 6 and 57 shall be used for memory >> > keys.

Re: [RFC PATCH 1/7 v1]powerpc: Free up four PTE bits to accommodate memory keys

Ram Pai writes: > On Mon, Jun 12, 2017 at 12:27:44PM +0530, Aneesh Kumar K.V wrote: >> Ram Pai writes: >> >> > Rearrange PTE bits to free up bits 3, 4, 5 and 6 for >> > memory keys. Bit 3, 4, 5, 6 and 57 shall be used for memory >> > keys. >> > >> > The patch does the following

[PATCH v15 2/7] power: add power sequence library

We have an well-known problem that the device needs to do some power sequence before it can be recognized by related host, the typical example like hard-wired mmc devices and usb devices. This power sequence is hard to be described at device tree and handled by related host driver, so we have

Re: linux-next: build failure after merge of the wireless-drivers-next tree

Hi Dave, On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/quantenna/qtnfmac/core.c: In function >

[PATCH v15 4/7] usb: core: add power sequence handling for USB devices

Some hard-wired USB devices need to do power sequence to let the device work normally, the typical power sequence like: enable USB PHY clock, toggle reset pin, etc. But current Linux USB driver lacks of such code to do it, it may cause some hard-wired USB devices works abnormal or can't be

[PATCH v15 2/7] power: add power sequence library

We have an well-known problem that the device needs to do some power sequence before it can be recognized by related host, the typical example like hard-wired mmc devices and usb devices. This power sequence is hard to be described at device tree and handled by related host driver, so we have

Re: linux-next: build failure after merge of the wireless-drivers-next tree

Hi Dave, On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/quantenna/qtnfmac/core.c: In function > 'qtnf_core_net_attach': >

[PATCH v15 4/7] usb: core: add power sequence handling for USB devices

Some hard-wired USB devices need to do power sequence to let the device work normally, the typical power sequence like: enable USB PHY clock, toggle reset pin, etc. But current Linux USB driver lacks of such code to do it, it may cause some hard-wired USB devices works abnormal or can't be

[PATCH v15 5/7] ARM: dts: imx6qdl: Enable usb node children with

From: Joshua Clayton Give usb nodes #address and #size attributes, so that a child node representing a permanently connected device such as an onboard hub may be addressed with a attribute Signed-off-by: Joshua Clayton Signed-off-by: Peter

[PATCH v15 5/7] ARM: dts: imx6qdl: Enable usb node children with

From: Joshua Clayton Give usb nodes #address and #size attributes, so that a child node representing a permanently connected device such as an onboard hub may be addressed with a attribute Signed-off-by: Joshua Clayton Signed-off-by: Peter Chen --- arch/arm/boot/dts/imx6qdl.dtsi | 6 ++

[PATCH v15 7/7] ARM: dts: imx6q-evi: Fix onboard hub reset line

From: Joshua Clayton Previously the onboard hub was made to work by treating its reset gpio as a regulator enable. Get rid of that kludge now that pwseq has added reset gpio support Move pin muxing the hub reset pin into the usbh1 group Signed-off-by: Joshua Clayton

[PATCH v15 7/7] ARM: dts: imx6q-evi: Fix onboard hub reset line

From: Joshua Clayton Previously the onboard hub was made to work by treating its reset gpio as a regulator enable. Get rid of that kludge now that pwseq has added reset gpio support Move pin muxing the hub reset pin into the usbh1 group Signed-off-by: Joshua Clayton Signed-off-by: Peter Chen

[PATCH v15 6/7] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property

The current dts describes USB HUB's property at USB controller's entry, it is improper. The USB HUB should be the child node under USB controller, and power sequence properties are under it. Besides, using gpio pinctrl setting for USB2415's reset pin. Signed-off-by: Peter Chen

[PATCH v15 6/7] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property

The current dts describes USB HUB's property at USB controller's entry, it is improper. The USB HUB should be the child node under USB controller, and power sequence properties are under it. Besides, using gpio pinctrl setting for USB2415's reset pin. Signed-off-by: Peter Chen Signed-off-by:

[PATCH v15 1/7] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

Add binding doc for generic power sequence library. Signed-off-by: Peter Chen Acked-by: Philipp Zabel Acked-by: Rob Herring --- .../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++ 1 file changed, 48

RE: [PATCH v2 1/1] PCI: imx6: Add pcie compliance test option

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Tuesday, June 13, 2017 7:49 AM > To: Stefan Schoefegger > Cc: linux-...@vger.kernel.org; Richard Zhu ; Arnd > Bergmann ; open list

[PATCH v15 3/7] binding-doc: usb: usb-device: add optional properties for power sequence

Add optional properties for power sequence. Signed-off-by: Peter Chen Acked-by: Rob Herring --- Documentation/devicetree/bindings/usb/usb-device.txt | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 0/2] arm64: fix crash when reading /proc/kcore

On 2017/6/9 3:41, Ard Biesheuvel wrote: > This is a follow-up to patches from zhonjiang [0] and myself [1] that aim > to solve a problem in the kcore code, which gets confused by the presence > of block mappings in the vmalloc region. > > While fixing the crash is quite straight forward [2], we

[PATCH v15 3/7] binding-doc: usb: usb-device: add optional properties for power sequence

Add optional properties for power sequence. Signed-off-by: Peter Chen Acked-by: Rob Herring --- Documentation/devicetree/bindings/usb/usb-device.txt | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt

Re: [PATCH 0/2] arm64: fix crash when reading /proc/kcore

On 2017/6/9 3:41, Ard Biesheuvel wrote: > This is a follow-up to patches from zhonjiang [0] and myself [1] that aim > to solve a problem in the kcore code, which gets confused by the presence > of block mappings in the vmalloc region. > > While fixing the crash is quite straight forward [2], we

[PATCH v15 1/7] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library

Add binding doc for generic power sequence library. Signed-off-by: Peter Chen Acked-by: Philipp Zabel Acked-by: Rob Herring --- .../bindings/power/pwrseq/pwrseq-generic.txt | 48 ++ 1 file changed, 48 insertions(+) create mode 100644

RE: [PATCH v2 1/1] PCI: imx6: Add pcie compliance test option

> -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: Tuesday, June 13, 2017 7:49 AM > To: Stefan Schoefegger > Cc: linux-...@vger.kernel.org; Richard Zhu ; Arnd > Bergmann ; open list ; > Kishon Vijay Abraham I ; Jingoo Han > ; Bjorn Helgaas ; > moderated

[PATCH v15 0/7] power: add power sequence library

This is a follow-up for my last power sequence framework patch set [1]. According to Rob Herring and Ulf Hansson's comments[2]. The kinds of power sequence instances will be added at postcore_initcall, the match criteria is compatible string first, if the compatible string is not matched between

[PATCH v15 0/7] power: add power sequence library

This is a follow-up for my last power sequence framework patch set [1]. According to Rob Herring and Ulf Hansson's comments[2]. The kinds of power sequence instances will be added at postcore_initcall, the match criteria is compatible string first, if the compatible string is not matched between

[PATCH 1/4] i2c: pca-platform: add devicetree awareness

Allow devices that use this driver to be registered via a devicetree. Signed-off-by: Chris Packham --- .../devicetree/bindings/i2c/i2c-pca-platform.txt| 18 ++ drivers/i2c/busses/i2c-pca-platform.c | 21 +

[PATCH 1/4] i2c: pca-platform: add devicetree awareness

Allow devices that use this driver to be registered via a devicetree. Signed-off-by: Chris Packham --- .../devicetree/bindings/i2c/i2c-pca-platform.txt| 18 ++ drivers/i2c/busses/i2c-pca-platform.c | 21 + 2 files changed, 39 insertions(+)

[PATCH 2/4] i2c: pca-platform: use gpio_is_valid

Use gpio_is_valid() instead of gpio > -1. Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-pca-platform.c

[PATCH 3/4] i2c: pca-platform: use device managed allocations

Switch to using the devm_ APIs and remove the now unnecessary error handling and most of the device removal code. Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 61 +++ 1 file changed, 11 insertions(+),

[PATCH 0/4] i2c: pca-platform: updates

We're using a PCA9564 on an embedded platform to provide an i2c controller. This adds devicetree support and I've included some cleanups for the driver while I was at it. Chris Packham (4): i2c: pca-platform: add devicetree awareness i2c: pca-platform: use gpio_is_valid i2c: pca-platform:

[PATCH 4/4] i2c: pca-platform: use dev_warn/dev_info instead of printk

Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-pca-platform.c b/drivers/i2c/busses/i2c-pca-platform.c index ee217ef5d879..f3285c4c159c

[PATCH 2/4] i2c: pca-platform: use gpio_is_valid

Use gpio_is_valid() instead of gpio > -1. Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-pca-platform.c b/drivers/i2c/busses/i2c-pca-platform.c index

[PATCH 3/4] i2c: pca-platform: use device managed allocations

Switch to using the devm_ APIs and remove the now unnecessary error handling and most of the device removal code. Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 61 +++ 1 file changed, 11 insertions(+), 50 deletions(-) diff --git

[PATCH 0/4] i2c: pca-platform: updates

We're using a PCA9564 on an embedded platform to provide an i2c controller. This adds devicetree support and I've included some cleanups for the driver while I was at it. Chris Packham (4): i2c: pca-platform: add devicetree awareness i2c: pca-platform: use gpio_is_valid i2c: pca-platform:

[PATCH 4/4] i2c: pca-platform: use dev_warn/dev_info instead of printk

Signed-off-by: Chris Packham --- drivers/i2c/busses/i2c-pca-platform.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/i2c/busses/i2c-pca-platform.c b/drivers/i2c/busses/i2c-pca-platform.c index ee217ef5d879..f3285c4c159c 100644 ---

Receive Your Bonus @Walmart Supercenter 2151 Royal Ave Monona, WI 53713.

Monona Walmart Supercenter 2151 Royal Ave Monona, WI 53713 (508) 465-2862 Dear Customer, Be informed that your bonus of $450,000 is set to send to you through Walmart to Walmart. All you need to do is to send us the below requested details to enable us proceed with your transfer today before

Receive Your Bonus @Walmart Supercenter 2151 Royal Ave Monona, WI 53713.

Monona Walmart Supercenter 2151 Royal Ave Monona, WI 53713 (508) 465-2862 Dear Customer, Be informed that your bonus of $450,000 is set to send to you through Walmart to Walmart. All you need to do is to send us the below requested details to enable us proceed with your transfer today before

Re: [git pull] first batch of ufs fixes

On Mon, Jun 12, 2017 at 05:54:06PM -0700, Richard Narron wrote: > Earlier today I could not reproduce the OpenBSD 6.1 ufs1 fsck error after > Linux 4.12-rc5 copy of my >2GB file using "cp". > > But later today I get the error when I copy using your "dd" method... > > In any case I always get a

Re: [git pull] first batch of ufs fixes

On Mon, Jun 12, 2017 at 05:54:06PM -0700, Richard Narron wrote: > Earlier today I could not reproduce the OpenBSD 6.1 ufs1 fsck error after > Linux 4.12-rc5 copy of my >2GB file using "cp". > > But later today I get the error when I copy using your "dd" method... > > In any case I always get a

Re: WMI and Kernel:User interface

On Tue, Jun 13, 2017 at 12:17:28AM +0200, Pali Rohár wrote: > On Monday 12 June 2017 19:02:49 Darren Hart wrote: > > On Sat, Jun 10, 2017 at 12:36:40PM +0200, Pali Rohár wrote: > > > On Saturday 10 June 2017 02:46:41 Darren Hart wrote: > > > > On Fri, Jun 09, 2017 at 08:41:51AM +0200, Greg

Re: WMI and Kernel:User interface

On Tue, Jun 13, 2017 at 12:17:28AM +0200, Pali Rohár wrote: > On Monday 12 June 2017 19:02:49 Darren Hart wrote: > > On Sat, Jun 10, 2017 at 12:36:40PM +0200, Pali Rohár wrote: > > > On Saturday 10 June 2017 02:46:41 Darren Hart wrote: > > > > On Fri, Jun 09, 2017 at 08:41:51AM +0200, Greg

[PATCH v2] mfd: Add driver for RAVE Supervisory Processor

Add a driver for RAVE Supervisory Processor, an MCU implementing varoius bits of housekeeping functionality (watchdoging, backlight control, LED control, etc) on RAVE family of products by Zodiac Inflight Innovations. This driver implementes core MFD/serdev device as well as communication

[PATCH v2] mfd: Add driver for RAVE Supervisory Processor

Add a driver for RAVE Supervisory Processor, an MCU implementing varoius bits of housekeeping functionality (watchdoging, backlight control, LED control, etc) on RAVE family of products by Zodiac Inflight Innovations. This driver implementes core MFD/serdev device as well as communication

Re: [PATCH 0/3] scsi: qedf: Fix a return value + some cleanups

Christophe, > This patch serie first fixes a case where an error code was missing. > The 2 other patches are just cleanups in the same area. Applied to 4.13/scsi-queue with fixed typo. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 0/3] scsi: qedf: Fix a return value + some cleanups

Christophe, > This patch serie first fixes a case where an error code was missing. > The 2 other patches are just cleanups in the same area. Applied to 4.13/scsi-queue with fixed typo. -- Martin K. Petersen Oracle Linux Engineering

Re: Ftrace vs perf user page fault statistics differences

On Mon, 12 Jun 2017 20:20:42 -0400 Will Hawkins wrote: > Dear Mr. Rostedt and Kernel community, > > I hope that this is an appropriate place to ask this question, Please > forgive me for wasting your time if it is not. I've searched for > answers to this question on LKML and

Re: Ftrace vs perf user page fault statistics differences

On Mon, 12 Jun 2017 20:20:42 -0400 Will Hawkins wrote: > Dear Mr. Rostedt and Kernel community, > > I hope that this is an appropriate place to ask this question, Please > forgive me for wasting your time if it is not. I've searched for > answers to this question on LKML and the "net" before

Re: [PATCH 0/2] esas2r: Replace semaphores with mutexes

Binoy, > These are a set of patches which removes semaphores from esas2r. > These are part of a bigger effort to eliminate unwanted semaphores > from the linux kernel. Applied to 4.13/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 0/2] esas2r: Replace semaphores with mutexes

Binoy, > These are a set of patches which removes semaphores from esas2r. > These are part of a bigger effort to eliminate unwanted semaphores > from the linux kernel. Applied to 4.13/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 03/11] Creation of "usb_device_auth" LSM hook

Hi Salvatore, [auto build test WARNING on security/next] [also build test WARNING on v4.12-rc5] [cannot apply to next-20170609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 03/11] Creation of "usb_device_auth" LSM hook

Hi Salvatore, [auto build test WARNING on security/next] [also build test WARNING on v4.12-rc5] [cannot apply to next-20170609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH V3 2/3] watchdog: uniphier: add UniPhier watchdog driver

Add a watchdog driver for Socionext UniPhier series SoC. Note that the timeout value for this device must be a power of 2 because of the specification. Signed-off-by: Keiji Hayashibara --- Documentation/watchdog/watchdog-parameters.txt | 6 +

[PATCH V3 2/3] watchdog: uniphier: add UniPhier watchdog driver

Add a watchdog driver for Socionext UniPhier series SoC. Note that the timeout value for this device must be a power of 2 because of the specification. Signed-off-by: Keiji Hayashibara --- Documentation/watchdog/watchdog-parameters.txt | 6 + drivers/watchdog/Kconfig |

[PATCH V3 1/3] dt-bindings: watchdog: add description for UniPhier WDT controller

Add uniphier-wdt dt-bindings documentation. Signed-off-by: Keiji Hayashibara --- .../devicetree/bindings/watchdog/uniphier-wdt.txt| 20 1 file changed, 20 insertions(+) create mode 100644

[PATCH V3 3/3] arm64: dts: uniphier: add watchdog node for LD11 and LD20

Add nodes of watchdog timer for UniPhier LD11 and LD20 SoC. The watchdog timer is included in sysctrl. Signed-off-by: Keiji Hayashibara --- arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 4 arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 4 2

[PATCH V3 1/3] dt-bindings: watchdog: add description for UniPhier WDT controller

Add uniphier-wdt dt-bindings documentation. Signed-off-by: Keiji Hayashibara --- .../devicetree/bindings/watchdog/uniphier-wdt.txt| 20 1 file changed, 20 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/uniphier-wdt.txt diff --git

[PATCH V3 3/3] arm64: dts: uniphier: add watchdog node for LD11 and LD20

Add nodes of watchdog timer for UniPhier LD11 and LD20 SoC. The watchdog timer is included in sysctrl. Signed-off-by: Keiji Hayashibara --- arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 4 arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 4 2 files changed, 8 insertions(+)

[RESEND PATCH 2/2] arm:omap2+: drop dependence on DEBUG_OMAP2PLUS_UART for DEBUG_UNCOMPRESS

With a patch 9a5151e1d1ba4df41bc4b8e8c0f17163247645ac, "arm:omap2+: put omap_uart_phys/virt/lsr in .text section when ZIMAGE is true", the dependence on DEBUG_OMAP2PLUS_UART for DEBUG_UNCOMPRESS can be dropped, because all code of omap2+'s DEBUG_LL_INCLUDE file is in .text section when it's

[PATCH V3 0/3] add UniPhier watchdog support

This series adds support for watchdog timer implemented on UniPhier LD11 and LD20 SoCs. This driver supports watchdog and system reset for SoCs. patch V2 http://www.spinics.net/lists/linux-watchdog/msg11852.html patch V1 http://www.spinics.net/lists/linux-watchdog/msg11782.html Changes between

[RESEND PATCH 2/2] arm:omap2+: drop dependence on DEBUG_OMAP2PLUS_UART for DEBUG_UNCOMPRESS

With a patch 9a5151e1d1ba4df41bc4b8e8c0f17163247645ac, "arm:omap2+: put omap_uart_phys/virt/lsr in .text section when ZIMAGE is true", the dependence on DEBUG_OMAP2PLUS_UART for DEBUG_UNCOMPRESS can be dropped, because all code of omap2+'s DEBUG_LL_INCLUDE file is in .text section when it's

[PATCH V3 0/3] add UniPhier watchdog support

This series adds support for watchdog timer implemented on UniPhier LD11 and LD20 SoCs. This driver supports watchdog and system reset for SoCs. patch V2 http://www.spinics.net/lists/linux-watchdog/msg11852.html patch V1 http://www.spinics.net/lists/linux-watchdog/msg11782.html Changes between

[RESEND PATCH 1/2] arm:omap2+: put omap_uart_phys/virt/lsr in .text section when ZIMAGE is true

omap_uart_phys, omap_uart_virt and omap_uart_lsr reside in .data section and it's right implementation. But because of this, we cannot enable CONFIG_DEBUG_UNCOMPRESS. LL_DEBUG and DEBUG_UNCOMPRESS are very useful tools for debugging early boot stage when something goes wrong if you don't have any

[RESEND PATCH 1/2] arm:omap2+: put omap_uart_phys/virt/lsr in .text section when ZIMAGE is true

omap_uart_phys, omap_uart_virt and omap_uart_lsr reside in .data section and it's right implementation. But because of this, we cannot enable CONFIG_DEBUG_UNCOMPRESS. LL_DEBUG and DEBUG_UNCOMPRESS are very useful tools for debugging early boot stage when something goes wrong if you don't have any

Re: [PATCH][scsi-next] scsi: qla2xxx: remove redundant null check on tgt

Colin, > An earlier commit ed7fb808477b846bb2 ("scsi: qla2xxx: Remove redundant > wait when target is stopped.") removed a null check on ha->tgt.tgt_ops > and replaced it with a new check that null checked tgt, thus making > the subsequent null check on tgt totally redundant. Remove it. Applied

Re: [PATCH][scsi-next] scsi: qla2xxx: remove redundant null check on tgt

Colin, > An earlier commit ed7fb808477b846bb2 ("scsi: qla2xxx: Remove redundant > wait when target is stopped.") removed a null check on ha->tgt.tgt_ops > and replaced it with a new check that null checked tgt, thus making > the subsequent null check on tgt totally redundant. Remove it. Applied

Re: [PATCH V4 0/2] scsi: ufshcd-pci: Add Intel CNL support

Adrian, > Here is V4 of patches to add support for Intel UFS host controllers. Applied to 4.13/scsi-queue. Thank you! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH V4 0/2] scsi: ufshcd-pci: Add Intel CNL support

Adrian, > Here is V4 of patches to add support for Intel UFS host controllers. Applied to 4.13/scsi-queue. Thank you! -- Martin K. Petersen Oracle Linux Engineering

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