Re: [PATCH] phy: Add reset callback for not generic phy

On 10/25/2016 7:15 AM, Randy Li wrote: > I forget to add a dummy function in case the CONFIG_GENERIC_PHY > is disabled. > > Signed-off-by: Randy Li Fixes: cac18ecb6f44 ("phy: Add reset callback") Tested-by: John Youn Hi Kishon, Can you take this for

Re: [PATCH] phy: Add reset callback for not generic phy

On 10/25/2016 7:15 AM, Randy Li wrote: > I forget to add a dummy function in case the CONFIG_GENERIC_PHY > is disabled. > > Signed-off-by: Randy Li Fixes: cac18ecb6f44 ("phy: Add reset callback") Tested-by: John Youn Hi Kishon, Can you take this for 4.9-rc? Thanks, John > --- >

Re: [PATCH 2/3] usb: dwc3: host: Do not use dma_set_coherent_mask

On Tuesday, October 25, 2016 4:26:27 PM CEST Sriram Dash wrote: > Do not require dma_set_coherent_mask for hcd > > Signed-off-by: Arnd Bergmann Aside from the comments I had for patch 3, you are doing two different things here: > diff --git a/drivers/usb/dwc3/dwc3-st.c

Re: [PATCH 2/3] usb: dwc3: host: Do not use dma_set_coherent_mask

On Tuesday, October 25, 2016 4:26:27 PM CEST Sriram Dash wrote: > Do not require dma_set_coherent_mask for hcd > > Signed-off-by: Arnd Bergmann Aside from the comments I had for patch 3, you are doing two different things here: > diff --git a/drivers/usb/dwc3/dwc3-st.c

Re: console issue since 3.6, console=ttyS1 hangs

On Mon, Oct 24, 2016 at 04:49:25PM -0500, Nathan Zimmer wrote: > [0.974874] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) > [0.975038] pnp 00:04: parse resource options > [0.975048] pnp 00:04: dependent set 0 (acceptable) io min 0x2f8 max > 0x2f8 align 1 size 8

Re: console issue since 3.6, console=ttyS1 hangs

On Mon, Oct 24, 2016 at 04:49:25PM -0500, Nathan Zimmer wrote: > [0.974874] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active) > [0.975038] pnp 00:04: parse resource options > [0.975048] pnp 00:04: dependent set 0 (acceptable) io min 0x2f8 max > 0x2f8 align 1 size 8

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 10/22, Xiaolong Zhang wrote: > On 四, 10月 20, 2016 at 04:01:03下午 -0700, Stephen Boyd wrote: > > On 10/11, Orson Zhai wrote: > > > From: Xiaolong Zhang > > > > > > When common kernel setups fixed clock, of_clk_provider will be > > > registerred. > > > But there

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 10/22, Xiaolong Zhang wrote: > On 四, 10月 20, 2016 at 04:01:03下午 -0700, Stephen Boyd wrote: > > On 10/11, Orson Zhai wrote: > > > From: Xiaolong Zhang > > > > > > When common kernel setups fixed clock, of_clk_provider will be > > > registerred. > > > But there is no clkdev being registerred

[PATCH v2] Input: synaptics-rmi4 - stop scanning PDT after two empty pages

We have encountered some RMI4 firmwares where there are blank pages in between PDT pages which contain functions. This change makes them correctly enumerate all functions on the device. Tested on S7817 (has empty page 2). Signed-off-by: Nick Dyer ---

[PATCH v2] Input: synaptics-rmi4 - stop scanning PDT after two empty pages

We have encountered some RMI4 firmwares where there are blank pages in between PDT pages which contain functions. This change makes them correctly enumerate all functions on the device. Tested on S7817 (has empty page 2). Signed-off-by: Nick Dyer --- drivers/input/rmi4/rmi_driver.c | 16

Re: [PATCH 3/3] clk: keystone: Fix missing iounmap calls in an error handling path

On 10/25, walter harms wrote: > Am 24.10.2016 22:43, schrieb Christophe JAILLET: > > @@ -220,6 +218,12 @@ static void __init _of_pll_clk_init(struct device_node > > *node, bool pllctrl) > > > > out: > > pr_err("%s: error initializing pll %s\n", __func__, node->name); > > + if

Re: [PATCH 3/3] clk: keystone: Fix missing iounmap calls in an error handling path

On 10/25, walter harms wrote: > Am 24.10.2016 22:43, schrieb Christophe JAILLET: > > @@ -220,6 +218,12 @@ static void __init _of_pll_clk_init(struct device_node > > *node, bool pllctrl) > > > > out: > > pr_err("%s: error initializing pll %s\n", __func__, node->name); > > + if

Re: [PATCH] tpm: sanitize constant expressions

On Sat, Oct 22, 2016 at 12:39:27AM +0300, Jarkko Sakkinen wrote: > Use cpu_to_b32 at the time it is needed in enum tpm_capabilities and > enum tpm_sub_capabilities in order to be consistent with the other > enums in drivats/char/tpm/tpm.h. > > Signed-off-by: Jarkko Sakkinen

Re: [PATCH] tpm: sanitize constant expressions

On Sat, Oct 22, 2016 at 12:39:27AM +0300, Jarkko Sakkinen wrote: > Use cpu_to_b32 at the time it is needed in enum tpm_capabilities and > enum tpm_sub_capabilities in order to be consistent with the other > enums in drivats/char/tpm/tpm.h. > > Signed-off-by: Jarkko Sakkinen I'll apply this to

Re: [tpmdd-devel] [PATCH] tpm, tpm_crb: remove redundant CRB_FL_CRB_START flag

On Fri, Oct 21, 2016 at 06:11:41PM +0300, Jarkko Sakkinen wrote: > On Thu, Oct 20, 2016 at 02:24:21PM -0600, Jason Gunthorpe wrote: > > On Thu, Oct 20, 2016 at 05:00:11PM +0300, Jarkko Sakkinen wrote: > > > > > > > I have a 4th Gen Core NUC where I experienced this issue. It reported > > > > >

Re: [tpmdd-devel] [PATCH] tpm, tpm_crb: remove redundant CRB_FL_CRB_START flag

On Fri, Oct 21, 2016 at 06:11:41PM +0300, Jarkko Sakkinen wrote: > On Thu, Oct 20, 2016 at 02:24:21PM -0600, Jason Gunthorpe wrote: > > On Thu, Oct 20, 2016 at 05:00:11PM +0300, Jarkko Sakkinen wrote: > > > > > > > I have a 4th Gen Core NUC where I experienced this issue. It reported > > > > >

Re: [PATCH 3/3] usb: dwc3: host: Do not use dma_coerce_mask_and_coherent

On Tuesday, October 25, 2016 4:26:28 PM CEST Sriram Dash wrote: > Do not use dma_coerce_mask_and_coherent for hcd. > > Signed-off-by: Arnd Bergmann The patch is good, but please follow the usual rules for submitting someone else's patch: - As the first line, have "From: Arnd

Re: [PATCH 3/3] usb: dwc3: host: Do not use dma_coerce_mask_and_coherent

On Tuesday, October 25, 2016 4:26:28 PM CEST Sriram Dash wrote: > Do not use dma_coerce_mask_and_coherent for hcd. > > Signed-off-by: Arnd Bergmann The patch is good, but please follow the usual rules for submitting someone else's patch: - As the first line, have "From: Arnd Bergmann ". "git

Re: [PATCH V2 4/8] PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage()

On 10/25, Viresh Kumar wrote: > On 24-10-16, 16:14, Stephen Boyd wrote: > > On 10/20, Viresh Kumar wrote: > > > Pass the entire supply structure instead of all of its fields. > > > > > > Signed-off-by: Viresh Kumar > > > --- > > > > This patch should be combined with

Re: [PATCH V2 4/8] PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage()

On 10/25, Viresh Kumar wrote: > On 24-10-16, 16:14, Stephen Boyd wrote: > > On 10/20, Viresh Kumar wrote: > > > Pass the entire supply structure instead of all of its fields. > > > > > > Signed-off-by: Viresh Kumar > > > --- > > > > This patch should be combined with the previous one. > > I

Re: [RFC v2] ARM: memory: da8xx-ddrctl: new driver

Kevin Hilman writes: > Bartosz Golaszewski writes: > >> Create a new driver for the da8xx DDR2/mDDR controller and implement >> support for writing to the Peripheral Bus Burst Priority Register. >> >> Signed-off-by: Bartosz Golaszewski

Re: [RFC v2] ARM: memory: da8xx-ddrctl: new driver

Kevin Hilman writes: > Bartosz Golaszewski writes: > >> Create a new driver for the da8xx DDR2/mDDR controller and implement >> support for writing to the Peripheral Bus Burst Priority Register. >> >> Signed-off-by: Bartosz Golaszewski >> --- >> .../memory-controllers/ti-da8xx-ddrctl.txt

Re: [PATCH 1/3] drivers: iommu: arm-smmu: constify iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const. >

Re: [PATCH 1/3] drivers: iommu: arm-smmu: constify iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const. >

Re: [PATCH 2/3] drivers: iommu: arm-smmu-v3: constify iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const. >

[PATCH v2] cw1200: fix bogus maybe-uninitialized warning

On x86, the cw1200 driver produces a rather silly warning about the possible use of the 'ret' variable without an initialization presumably after being confused by the architecture specific definition of WARN_ON: drivers/net/wireless/st/cw1200/wsm.c: In function ‘wsm_handle_rx’:

Re: [PATCH 2/3] drivers: iommu: arm-smmu-v3: constify iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const. >

[PATCH v2] cw1200: fix bogus maybe-uninitialized warning

On x86, the cw1200 driver produces a rather silly warning about the possible use of the 'ret' variable without an initialization presumably after being confused by the architecture specific definition of WARN_ON: drivers/net/wireless/st/cw1200/wsm.c: In function ‘wsm_handle_rx’:

Re: [PATCH] cw1200: fix bogus maybe-uninitialized warning

On Tuesday, October 25, 2016 1:24:55 PM CEST David Laight wrote: > > diff --git a/drivers/net/wireless/st/cw1200/wsm.c > > b/drivers/net/wireless/st/cw1200/wsm.c > > index 680d60eabc75..094e6637ade2 100644 > > --- a/drivers/net/wireless/st/cw1200/wsm.c > > +++

Re: [PATCH] cw1200: fix bogus maybe-uninitialized warning

On Tuesday, October 25, 2016 1:24:55 PM CEST David Laight wrote: > > diff --git a/drivers/net/wireless/st/cw1200/wsm.c > > b/drivers/net/wireless/st/cw1200/wsm.c > > index 680d60eabc75..094e6637ade2 100644 > > --- a/drivers/net/wireless/st/cw1200/wsm.c > > +++

Re: [PATCH 3/3] drivers: iommu: io-pgtable-arm: use const and __initconst for iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const.

Re: [PATCH 3/3] drivers: iommu: io-pgtable-arm: use const and __initconst for iommu_gather_ops structures

On Tue, 25 Oct 2016, Bhumika Goyal wrote: > Check for iommu_gather_ops structures that are only stored in the tlb > field of an io_pgtable_cfg structure. The tlb field is of type > const struct iommu_gather_ops *, so iommu_gather_ops structures > having this property can be declared as const.

Re: [PATCH v2 2/8] IB/core: Replace semaphore sm_sem with completion

On Tuesday, October 25, 2016 9:48:22 AM CEST Jason Gunthorpe wrote: > > Using a completion to model exclusive ownership seems convoluted to > me - is that a thing now? What about an atomic? I also totally missed how this is used. I initially mentioned to Binoy that almost all semaphores can

Re: [PATCH v2 2/8] IB/core: Replace semaphore sm_sem with completion

On Tuesday, October 25, 2016 9:48:22 AM CEST Jason Gunthorpe wrote: > > Using a completion to model exclusive ownership seems convoluted to > me - is that a thing now? What about an atomic? I also totally missed how this is used. I initially mentioned to Binoy that almost all semaphores can

Re: [PATCH] virtio-net: Update the mtu code to match virtio spec

Aaron Conole writes: >> From: Aaron Conole >> >> The virtio committee recently ratified a change, VIRTIO-152, which >> defines the mtu field to be 'max' MTU, not simply desired MTU. >> >> This commit brings the virtio-net device in compliance with

Re: [PATCH] virtio-net: Update the mtu code to match virtio spec

Aaron Conole writes: >> From: Aaron Conole >> >> The virtio committee recently ratified a change, VIRTIO-152, which >> defines the mtu field to be 'max' MTU, not simply desired MTU. >> >> This commit brings the virtio-net device in compliance with VIRTIO-152. >> >> Additionally, drop the

[PATCH v2 net-next] virtio-net: Update the mtu code to match virtio spec

The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by

[PATCH v2 net-next] virtio-net: Update the mtu code to match virtio spec

The virtio committee recently ratified a change, VIRTIO-152, which defines the mtu field to be 'max' MTU, not simply desired MTU. This commit brings the virtio-net device in compliance with VIRTIO-152. Additionally, drop the max_mtu branch - it cannot be taken since the u16 returned by

Re: Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Peter, On 25.10.2016 21:39, Peter Rosin wrote: > Hi! > > Early on in my boot procedure I create an overlay and shuffle > things around a bit so that the original rootfs stays readonly > at the bottom of an overlayed readwrite fs. This way I can just > toss out the overlayed fs and have a clean

Re: Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Peter, On 25.10.2016 21:39, Peter Rosin wrote: > Hi! > > Early on in my boot procedure I create an overlay and shuffle > things around a bit so that the original rootfs stays readonly > at the bottom of an overlayed readwrite fs. This way I can just > toss out the overlayed fs and have a clean

[PATCH v3 1/1] ahci: imx: Add imx53 SATA temperature sensor support

From: Csaba Kertesz Add a hwmon entry to get the temperature from the die of imx53 SATA. The original patch was made by Richard Zhu for kernel 2.6.x: ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch Signed-off-by: Fabien Lahoudere

[PATCH v3 1/1] ahci: imx: Add imx53 SATA temperature sensor support

From: Csaba Kertesz Add a hwmon entry to get the temperature from the die of imx53 SATA. The original patch was made by Richard Zhu for kernel 2.6.x: ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch Signed-off-by: Fabien Lahoudere --- drivers/ata/ahci_imx.c | 195

RE: [PATCH] drm/amd/powerplay: mark symbols static where possible

> -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Tuesday, October 25, 2016 4:15 AM > To: Baoyou Xie > Cc: Deucher, Alexander; Dave Airlie; Zhu, Rex; Zhou, Jammy; Huang, > JinHuiEric; StDenis, Tom; Edward O'Callaghan; Prosyak, Vitaly; Yang, Eric; > Yang, Young;

RE: [PATCH] drm/amd/powerplay: mark symbols static where possible

> -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: Tuesday, October 25, 2016 4:15 AM > To: Baoyou Xie > Cc: Deucher, Alexander; Dave Airlie; Zhu, Rex; Zhou, Jammy; Huang, > JinHuiEric; StDenis, Tom; Edward O'Callaghan; Prosyak, Vitaly; Yang, Eric; > Yang, Young;

Re: [PATCH] virtio-net: Update the mtu code to match virtio spec

> From: Aaron Conole > > The virtio committee recently ratified a change, VIRTIO-152, which > defines the mtu field to be 'max' MTU, not simply desired MTU. > > This commit brings the virtio-net device in compliance with VIRTIO-152. > > Additionally, drop the max_mtu branch -

Re: [PATCH] virtio-net: Update the mtu code to match virtio spec

> From: Aaron Conole > > The virtio committee recently ratified a change, VIRTIO-152, which > defines the mtu field to be 'max' MTU, not simply desired MTU. > > This commit brings the virtio-net device in compliance with VIRTIO-152. > > Additionally, drop the max_mtu branch - it cannot be taken

Re: [PATCH] iio: maxim_thermocouple: return -EINVAL on invalid read size

On 25/10/16 20:11, Lars-Peter Clausen wrote: > On 10/25/2016 09:04 PM, Colin King wrote: >> From: Colin Ian King >> >> In the case that the read size is not 2 or 4 bytes >> then maxim_thermocouple_read is not initializing ret and >> hence may return early with a bogus

Re: [PATCH] iio: maxim_thermocouple: return -EINVAL on invalid read size

On 25/10/16 20:11, Lars-Peter Clausen wrote: > On 10/25/2016 09:04 PM, Colin King wrote: >> From: Colin Ian King >> >> In the case that the read size is not 2 or 4 bytes >> then maxim_thermocouple_read is not initializing ret and >> hence may return early with a bogus error return or >> just

Re: [RFC 5/8] mm: Add new flag VM_CDM for coherent device memory

On 10/25/2016 12:20 PM, Aneesh Kumar K.V wrote: > Dave Hansen writes: >> On 10/23/2016 09:31 PM, Anshuman Khandual wrote: >>> VMAs containing coherent device memory should be marked with VM_CDM. These >>> VMAs need to be identified in various core kernel paths and this new

Re: [RFC 5/8] mm: Add new flag VM_CDM for coherent device memory

On 10/25/2016 12:20 PM, Aneesh Kumar K.V wrote: > Dave Hansen writes: >> On 10/23/2016 09:31 PM, Anshuman Khandual wrote: >>> VMAs containing coherent device memory should be marked with VM_CDM. These >>> VMAs need to be identified in various core kernel paths and this new flag >>> will help in

Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories

Hi Cyrille, On Tue, Oct 25, 2016 at 2:38 PM, Jagan Teki wrote: > On Mon, Oct 24, 2016 at 7:37 PM, Cyrille Pitchen > wrote: >> Le 24/10/2016 à 14:09, Cyrille Pitchen a écrit : >>> Hi Jagan, >>> >>> Le 24/10/2016 à 09:41, Jagan Teki a écrit : On

Re: [PATCH v2 0/9] mtd: spi-nor: parse SFDP tables to setup (Q)SPI memories

Hi Cyrille, On Tue, Oct 25, 2016 at 2:38 PM, Jagan Teki wrote: > On Mon, Oct 24, 2016 at 7:37 PM, Cyrille Pitchen > wrote: >> Le 24/10/2016 à 14:09, Cyrille Pitchen a écrit : >>> Hi Jagan, >>> >>> Le 24/10/2016 à 09:41, Jagan Teki a écrit : On Sun, Oct 23, 2016 at 2:03 AM, Marek Vasut

[PATCHv2 7/7] mm: kill arch_mremap

This reverts commit 4abad2ca4a4d ("mm: new arch_remap() hook") and commit 2ae416b142b6 ("mm: new mm hook framework"). It also keeps the same functionality of mremapping vDSO blob with introducing vm_special_mapping mremap op for powerpc. Cc: Laurent Dufour Cc:

[PATCHv2 7/7] mm: kill arch_mremap

This reverts commit 4abad2ca4a4d ("mm: new arch_remap() hook") and commit 2ae416b142b6 ("mm: new mm hook framework"). It also keeps the same functionality of mremapping vDSO blob with introducing vm_special_mapping mremap op for powerpc. Cc: Laurent Dufour Cc: Benjamin Herrenschmidt Cc: Paul

[RFC 2/2] mmc: sdhci: Use sdhci-caps-mask and sdhci-caps to change the caps read during __sdhci_read_caps

The sdhci capabilities registers can be incorrect. The sdhci-caps-mask and sdhci-caps dt properties specify which bits of the registers are incorrect and what their values should be. This patch makes the sdhci driver use those properties to correct the caps during __sdhci_read_caps. During

[RFC 0/2] mmc: sdhci: Fix sdhci caps register bits with corrections provided by dt

For various reasons the sdhci caps register can be incorrect. This patch set introduces a general way to correct the bits when they are read to accurately reflect the capabilties of the controller/board combo. The first patch creates sdhci-caps and sdhci-caps-mask dt properties that combined

[RFC 1/2] mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask

On some systems the sdhci capabilty registers are incorrect for one reason or another. The sdhci-caps-mask property specifies which bits in the registers are incorrect and should be turned off before using sdhci-caps to turn on bits. The sdhci-caps property specifies which bits should be turned

[RFC 2/2] mmc: sdhci: Use sdhci-caps-mask and sdhci-caps to change the caps read during __sdhci_read_caps

The sdhci capabilities registers can be incorrect. The sdhci-caps-mask and sdhci-caps dt properties specify which bits of the registers are incorrect and what their values should be. This patch makes the sdhci driver use those properties to correct the caps during __sdhci_read_caps. During

[RFC 0/2] mmc: sdhci: Fix sdhci caps register bits with corrections provided by dt

For various reasons the sdhci caps register can be incorrect. This patch set introduces a general way to correct the bits when they are read to accurately reflect the capabilties of the controller/board combo. The first patch creates sdhci-caps and sdhci-caps-mask dt properties that combined

[RFC 1/2] mmc: sdhci: dt: Add device tree properties sdhci-caps and sdhci-caps-mask

On some systems the sdhci capabilty registers are incorrect for one reason or another. The sdhci-caps-mask property specifies which bits in the registers are incorrect and should be turned off before using sdhci-caps to turn on bits. The sdhci-caps property specifies which bits should be turned

[DOC] Missing completions-design.txt?

Hi, It looks like Nicholas submitted this doc a while back as patch 2/2: "[PATCH 2/2] doc: detailed documentation for completion" http://lkml.iu.edu/hypermail/linux/kernel/1412.2/03676.html where patch 1/2 got merged as this: 202799be447b doc: brief user documentation for completion

[DOC] Missing completions-design.txt?

Hi, It looks like Nicholas submitted this doc a while back as patch 2/2: "[PATCH 2/2] doc: detailed documentation for completion" http://lkml.iu.edu/hypermail/linux/kernel/1412.2/03676.html where patch 1/2 got merged as this: 202799be447b doc: brief user documentation for completion

Re: [PATCH] PCI: pci-stub: accept exceptions to the ID- and class-based matching

On 10/25/16 21:24, Laszlo Ersek wrote: > On 10/25/16 20:42, Alex Williamson wrote: >> FWIW, I think the reason >> this hasn't been done to date is that PCI bus addresses (except for >> root bus devices) are not stable. Depending on the system, the address >> of a given device may change, not

Re: [PATCH] PCI: pci-stub: accept exceptions to the ID- and class-based matching

On 10/25/16 21:24, Laszlo Ersek wrote: > On 10/25/16 20:42, Alex Williamson wrote: >> FWIW, I think the reason >> this hasn't been done to date is that PCI bus addresses (except for >> root bus devices) are not stable. Depending on the system, the address >> of a given device may change, not

Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Hi! Early on in my boot procedure I create an overlay and shuffle things around a bit so that the original rootfs stays readonly at the bottom of an overlayed readwrite fs. This way I can just toss out the overlayed fs and have a clean and reliable way to do a "factory-reset". Both the read-only

Regression caused by commit c83ed4c9dbb3 "ubifs: Abort readdir on error"

Hi! Early on in my boot procedure I create an overlay and shuffle things around a bit so that the original rootfs stays readonly at the bottom of an overlayed readwrite fs. This way I can just toss out the overlayed fs and have a clean and reliable way to do a "factory-reset". Both the read-only

Re: [RFC] shutdown machine when li-ion battery goes below 3V

> + res = bq27xxx_battery_voltage(di, ); > + if (res) > + return res; > + > + mV = val.intval / 1000; Reading that code I stumbled over the comment in bq27xxx_battery_voltage saying that it returns millivolts. The code here, the code in bq27xxx_battery_voltage and

Re: [RFC] shutdown machine when li-ion battery goes below 3V

> + res = bq27xxx_battery_voltage(di, ); > + if (res) > + return res; > + > + mV = val.intval / 1000; Reading that code I stumbled over the comment in bq27xxx_battery_voltage saying that it returns millivolts. The code here, the code in bq27xxx_battery_voltage and

[PATCH 1/7] powerpc/vdso: unify return paths in setup_additional_pages

Impact: cleanup Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Michael Ellerman Cc: Andy Lutomirski Cc: Oleg Nesterov Cc: linuxppc-...@lists.ozlabs.org Cc: linux...@kvack.org

Re: [PATCH v3 2/9] mtd: spi-nor: add an alternative method to support memory >16MiB

On 10/25/2016 11:18 AM, Cyrille Pitchen wrote: > Le 25/10/2016 à 00:10, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> This patch provides an alternative mean to support memory above 16MiB >>> (128Mib) by replacing 3byte address op codes by their associated 4byte >>>

Re: [PATCH v3 1/9] mtd: spi-nor: improve macronix_quad_enable()

On 10/25/2016 10:52 AM, Cyrille Pitchen wrote: > Hi Marek, > > Le 25/10/2016 à 00:00, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> The patch checks whether the Quad Enable bit is already set in the Status >>> Register. If so, the function exits immediately with a

[PATCH 1/7] powerpc/vdso: unify return paths in setup_additional_pages

Impact: cleanup Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Michael Ellerman Cc: Andy Lutomirski Cc: Oleg Nesterov Cc: linuxppc-...@lists.ozlabs.org Cc: linux...@kvack.org Signed-off-by: Dmitry Safonov --- arch/powerpc/kernel/vdso.c | 19 +++ 1 file changed, 7

Re: [PATCH v3 2/9] mtd: spi-nor: add an alternative method to support memory >16MiB

On 10/25/2016 11:18 AM, Cyrille Pitchen wrote: > Le 25/10/2016 à 00:10, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> This patch provides an alternative mean to support memory above 16MiB >>> (128Mib) by replacing 3byte address op codes by their associated 4byte >>>

Re: [PATCH v3 1/9] mtd: spi-nor: improve macronix_quad_enable()

On 10/25/2016 10:52 AM, Cyrille Pitchen wrote: > Hi Marek, > > Le 25/10/2016 à 00:00, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> The patch checks whether the Quad Enable bit is already set in the Status >>> Register. If so, the function exits immediately with a

[PATCH v5 7/8] drivers:input:ads7846(+tsc2046): fix spi module table

Fix module table so that the driver is loaded if compiled as module and requested by DT. Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/ads7846.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git

[PATCH v5 6/8] drivers:input:ads7846(+tsc2046): add new common binding names, pre-calibration and flipping

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

[PATCH v5 7/8] drivers:input:ads7846(+tsc2046): fix spi module table

Fix module table so that the driver is loaded if compiled as module and requested by DT. Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/ads7846.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/drivers/input/touchscreen/ads7846.c

[PATCH v5 6/8] drivers:input:ads7846(+tsc2046): add new common binding names, pre-calibration and flipping

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

[PATCH v5 4/8] drivers:input:tsc2007: add iio interface to read external ADC input and temperature

The tsc2007 chip not only has a resistive touch screen controller but also an external AUX adc imput which can be used for an ambient light sensor, battery voltage monitoring or any general purpose. Additionally it can measure the chip temperature. This extension provides an iio interface for

[PATCH v5 3/8] drivers:input:tsc2007: check for presence and power down tsc2007 during probe

1. check if chip is really present and don't succeed if it isn't. 2. if it succeeds, power down the chip until accessed Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/tsc2007.c | 8 1 file changed, 8 insertions(+) diff --git

[PATCH 6/7] powerpc/vdso: switch from legacy_special_mapping_vmops

This will allow to introduce mremap hook (the next patch). Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Michael Ellerman Cc: Andy Lutomirski Cc: Oleg Nesterov Cc:

[PATCH v5 3/8] drivers:input:tsc2007: check for presence and power down tsc2007 during probe

1. check if chip is really present and don't succeed if it isn't. 2. if it succeeds, power down the chip until accessed Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/tsc2007.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/input/touchscreen/tsc2007.c

[PATCH 6/7] powerpc/vdso: switch from legacy_special_mapping_vmops

This will allow to introduce mremap hook (the next patch). Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Michael Ellerman Cc: Andy Lutomirski Cc: Oleg Nesterov Cc: linuxppc-...@lists.ozlabs.org Cc: linux...@kvack.org Signed-off-by: Dmitry Safonov --- arch/powerpc/kernel/vdso.c

[PATCH v5 4/8] drivers:input:tsc2007: add iio interface to read external ADC input and temperature

The tsc2007 chip not only has a resistive touch screen controller but also an external AUX adc imput which can be used for an ambient light sensor, battery voltage monitoring or any general purpose. Additionally it can measure the chip temperature. This extension provides an iio interface for

Re: [PATCH v3 8/9] mtd: spi-nor: add support to Macronix mx66l1g45g

On 10/25/2016 11:39 AM, Cyrille Pitchen wrote: > Hi Marek, Hi, > Le 25/10/2016 à 00:16, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> This patch adds an entry in the spi_nor_ids[] table to add support >>> to the Macronix mx66l1g45g. >>> >>> Signed-off-by: Cyrille

Re: [PATCH v3 8/9] mtd: spi-nor: add support to Macronix mx66l1g45g

On 10/25/2016 11:39 AM, Cyrille Pitchen wrote: > Hi Marek, Hi, > Le 25/10/2016 à 00:16, Marek Vasut a écrit : >> On 10/24/2016 06:34 PM, Cyrille Pitchen wrote: >>> This patch adds an entry in the spi_nor_ids[] table to add support >>> to the Macronix mx66l1g45g. >>> >>> Signed-off-by: Cyrille

Re: [PATCH 4/4] ARM: dts: da850: Add the usb otg device node

On 10/25/2016 09:39 AM, Alexandre Bailon wrote: This adds the device tree node for the usb otg controller present in the da850 family of SoC's. This also enables the otg usb controller for the lcdk board. Signed-off-by: Alexandre Bailon ---

Re: [PATCH 4/4] ARM: dts: da850: Add the usb otg device node

On 10/25/2016 09:39 AM, Alexandre Bailon wrote: This adds the device tree node for the usb otg controller present in the da850 family of SoC's. This also enables the otg usb controller for the lcdk board. Signed-off-by: Alexandre Bailon --- arch/arm/boot/dts/da850-lcdk.dts | 8

[PATCH v5 2/8] drivers:input:tsc2007: send pendown and penup only once like ads7846(+tsc2046) driver does

this should reduce unnecessary input events. Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/tsc2007.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/input/touchscreen/tsc2007.c

[PATCH v5 2/8] drivers:input:tsc2007: send pendown and penup only once like ads7846(+tsc2046) driver does

this should reduce unnecessary input events. Signed-off-by: H. Nikolaus Schaller --- drivers/input/touchscreen/tsc2007.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/input/touchscreen/tsc2007.c b/drivers/input/touchscreen/tsc2007.c index

[PATCH v5 0/8] drivers: touchscreen: tsc2007 and ads7846/tsc2046 improvements (use common touchscreen bindings, pre-calibration, spi fix and provide iio raw values)

Changes V5: * ads7846: remove an empty line (suggested by Andrew F. Davis ) * ads7846: remove MODULE_ALIAS for SPI (suggested by Andrew F. Davis ) * tsc2007: fix a bug from swapping patch 3/n and patch 4/n (found by kbuid test robot) * refactored tsc2007 into

[PATCH v5 8/8] DT:omap3+ads7846: use new common touchscreen bindings

The standard touch screen bindings [1] replace the private ti,swap-xy with touchscreen-swaped-x-y. And for the Openpandora we use touchscreen-size etc. to match the LCD screen size. [1]: Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt Tested with OpenPandora. Signed-off-by:

[PATCH v5 5/8] DT:omap3+tsc2007: use new common touchscreen bindings

While we fix the GTA04 we add proper pinmux for the penirq gpio. Tested on: GTA04A4 and Pyra-Handheld Signed-off-by: H. Nikolaus Schaller --- arch/arm/boot/dts/omap3-gta04.dtsi | 25 +++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git

[PATCH v5 0/8] drivers: touchscreen: tsc2007 and ads7846/tsc2046 improvements (use common touchscreen bindings, pre-calibration, spi fix and provide iio raw values)

Changes V5: * ads7846: remove an empty line (suggested by Andrew F. Davis ) * ads7846: remove MODULE_ALIAS for SPI (suggested by Andrew F. Davis ) * tsc2007: fix a bug from swapping patch 3/n and patch 4/n (found by kbuid test robot) * refactored tsc2007 into tsc2007_core and tsc2007_iio (asked

[PATCH v5 8/8] DT:omap3+ads7846: use new common touchscreen bindings

The standard touch screen bindings [1] replace the private ti,swap-xy with touchscreen-swaped-x-y. And for the Openpandora we use touchscreen-size etc. to match the LCD screen size. [1]: Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt Tested with OpenPandora. Signed-off-by:

[PATCH v5 5/8] DT:omap3+tsc2007: use new common touchscreen bindings

While we fix the GTA04 we add proper pinmux for the penirq gpio. Tested on: GTA04A4 and Pyra-Handheld Signed-off-by: H. Nikolaus Schaller --- arch/arm/boot/dts/omap3-gta04.dtsi | 25 +++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git

[PATCH v5 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

[PATCH v5 1/8] drivers:input:tsc2007: add new common binding names, pre-calibration, flipping and rotation

commit b98abe52fa8e ("Input: add common DT binding for touchscreens") introduced common DT bindings for touchscreens [1] and a helper function to parse the DT. commit ed7c9870c9bc ("Input: of_touchscreen - add support for inverted / swapped axes") added another helper for parsing axis inversion

Re: [PATCH] PCI: pci-stub: accept exceptions to the ID- and class-based matching

On 10/25/16 20:42, Alex Williamson wrote: > On Tue, 25 Oct 2016 20:24:19 +0200 > Laszlo Ersek wrote: > >> Some systems have multiple instances of the exact same kind of PCI device >> installed. When VFIO users intend to assign these devices to VMs, they >> occasionally don't

Applied "ASoC: tlv320aic31xx: add explicit support for tlv320dac31xx" to the asoc tree

The patch ASoC: tlv320aic31xx: add explicit support for tlv320dac31xx has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

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