Re: [PATCH V3 2/7] PM / OPP: Introduce "domain-performance-state" binding to OPP nodes

On Fri, Feb 24, 2017 at 02:36:34PM +0530, Viresh Kumar wrote: > If the consumers don't need the capability of switching to different > domain performance states at runtime, then they can simply define their > required domain performance state in their nodes directly. > > But if the device needs

Re: [PATCH V3 2/7] PM / OPP: Introduce "domain-performance-state" binding to OPP nodes

On Fri, Feb 24, 2017 at 02:36:34PM +0530, Viresh Kumar wrote: > If the consumers don't need the capability of switching to different > domain performance states at runtime, then they can simply define their > required domain performance state in their nodes directly. > > But if the device needs

Re: [LKP] [lkp-developer] [sched/fair] 4e5160766f: +149% ftq.noise.50% regression

Vincent Guittot writes: > Hi Ying, > > On 21 February 2017 at 03:40, Huang, Ying wrote: >> Hi, Vincent, >> >> Vincent Guittot writes: >> > > [snip] > Here is the test result,

Re: [LKP] [lkp-developer] [sched/fair] 4e5160766f: +149% ftq.noise.50% regression

Vincent Guittot writes: > Hi Ying, > > On 21 February 2017 at 03:40, Huang, Ying wrote: >> Hi, Vincent, >> >> Vincent Guittot writes: >> > > [snip] > Here is the test result, =

Re: [PATCH v2 12/17] dt-bindings: arm: Document Actions Semi S900

On Fri, Feb 24, 2017 at 04:40:50AM +0100, Andreas Färber wrote: > The Actions Semi S900 is a quad-core ARM Cortex-A53 SoC. > The Bubblegum-96 is a 96Boards Consumer Edition compliant board (4/96). > > Cc: 96boa...@ucrobotics.com > Signed-off-by: Andreas Färber > --- > v1 ->

Re: [PATCH v2 12/17] dt-bindings: arm: Document Actions Semi S900

On Fri, Feb 24, 2017 at 04:40:50AM +0100, Andreas Färber wrote: > The Actions Semi S900 is a quad-core ARM Cortex-A53 SoC. > The Bubblegum-96 is a 96Boards Consumer Edition compliant board (4/96). > > Cc: 96boa...@ucrobotics.com > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Adopted

Re: [PATCH v2 2/5] dt-bindings: arm: Add Realtek RTD1295 bindings

On Thu, Feb 23, 2017 at 05:45:49PM +0100, Andreas Färber wrote: > The Zidoo X9S and a few other recent TV boxes feature the Realtek RTD1295, > a quad-core ARM Cortex-A53 SoC. > > Acked-by: Arnd Bergmann > Acked-by: Roc He > Signed-off-by: Andreas Färber

Re: [PATCH v2 2/5] dt-bindings: arm: Add Realtek RTD1295 bindings

On Thu, Feb 23, 2017 at 05:45:49PM +0100, Andreas Färber wrote: > The Zidoo X9S and a few other recent TV boxes feature the Realtek RTD1295, > a quad-core ARM Cortex-A53 SoC. > > Acked-by: Arnd Bergmann > Acked-by: Roc He > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Changed subject

Re: [PATCH v2 3.5/5] trace/kprobes: Add back warning about offset in return probes

On Mon, 27 Feb 2017 11:52:04 -0500 "Steven Rostedt (VMware)" wrote: > Let's not remove the warning about offsets and return probes when the > offset is invalid. Agreed, This looks good to me. Acked-by: Masami Hiramatsu Thanks! > > Signed-off-by:

Re: [PATCH v2 3.5/5] trace/kprobes: Add back warning about offset in return probes

On Mon, 27 Feb 2017 11:52:04 -0500 "Steven Rostedt (VMware)" wrote: > Let's not remove the warning about offsets and return probes when the > offset is invalid. Agreed, This looks good to me. Acked-by: Masami Hiramatsu Thanks! > > Signed-off-by: Steven Rostedt (VMware) > --- > diff --git

Re: [PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

On Sun, Feb 26, 2017 at 3:45 PM, Eva Rachel Retuya wrote: > This patchset modifies the adxl345 to use regmap. In doing so, we can > easily introduce SPI support and let regmap handle the rest. > > Recap of basic features: read_raw for x, y and z axes, scale. After > applying

Re: [PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

On Sun, Feb 26, 2017 at 3:45 PM, Eva Rachel Retuya wrote: > This patchset modifies the adxl345 to use regmap. In doing so, we can > easily introduce SPI support and let regmap handle the rest. > > Recap of basic features: read_raw for x, y and z axes, scale. After > applying this series, driver

Re: [PATCH] input: cpcap-pwrbutton: new driver

On Fri, Feb 24, 2017 at 09:59:09AM +0100, Sebastian Reichel wrote: > Motorola CPCAP is a PMIC found in multiple smartphones. > This driver adds support for the power/on button and has > been tested with Droid 4. > > Signed-off-by: Sebastian Reichel > --- >

Re: [PATCH] input: cpcap-pwrbutton: new driver

On Fri, Feb 24, 2017 at 09:59:09AM +0100, Sebastian Reichel wrote: > Motorola CPCAP is a PMIC found in multiple smartphones. > This driver adds support for the power/on button and has > been tested with Droid 4. > > Signed-off-by: Sebastian Reichel > --- >

[PATCH] wireless: ipw2200: remove redundant check of rc < 0

From: Colin Ian King The check for rc < 0 is always false so the check is redundant and can be removed. Detected with CoverityScan, CID#101143 ("Logically dead code") Signed-off-by: Colin Ian King ---

[PATCH] wireless: ipw2200: remove redundant check of rc < 0

From: Colin Ian King The check for rc < 0 is always false so the check is redundant and can be removed. Detected with CoverityScan, CID#101143 ("Logically dead code") Signed-off-by: Colin Ian King --- drivers/net/wireless/intel/ipw2x00/ipw2200.c | 3 --- 1 file changed, 3 deletions(-) diff

Re: [PATCH v2 11/17] dt-bindings: Add vendor prefix for uCRobotics

On Fri, Feb 24, 2017 at 04:40:49AM +0100, Andreas Färber wrote: > Cc: 96boa...@ucrobotics.com > Signed-off-by: Andreas Färber > --- > v1 -> v2: unchanged > > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file changed, 1 insertion(+) Acked-by: Rob Herring

Re: [PATCH v2 07/17] dt-bindings: serial: Document Actions Semi Owl UARTs

On Fri, Feb 24, 2017 at 04:40:45AM +0100, Andreas Färber wrote: > This UART is found on S500 and S900 SoCs. > > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Adopted "actions" vendor prefix > > .../devicetree/bindings/serial/actions,owl-uart.txt | 16 >

Re: ARM: OMAP2+: Grab reference to device nodes where needed

ping ... this problem is now seen in mainline. Guenter On Sat, Feb 11, 2017 at 02:59:08PM -0800, Guenter Roeck wrote: > After commit 'of: fix of_node leak caused in of_find_node_opts_by_path', > the following error may be reported when running omap images. > > OF: ERROR: Bad of_node_put() on

Re: [PATCH v2 11/17] dt-bindings: Add vendor prefix for uCRobotics

On Fri, Feb 24, 2017 at 04:40:49AM +0100, Andreas Färber wrote: > Cc: 96boa...@ucrobotics.com > Signed-off-by: Andreas Färber > --- > v1 -> v2: unchanged > > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file changed, 1 insertion(+) Acked-by: Rob Herring

Re: [PATCH v2 07/17] dt-bindings: serial: Document Actions Semi Owl UARTs

On Fri, Feb 24, 2017 at 04:40:45AM +0100, Andreas Färber wrote: > This UART is found on S500 and S900 SoCs. > > Signed-off-by: Andreas Färber > --- > v1 -> v2: > * Adopted "actions" vendor prefix > > .../devicetree/bindings/serial/actions,owl-uart.txt | 16 > > 1 file

Re: ARM: OMAP2+: Grab reference to device nodes where needed

ping ... this problem is now seen in mainline. Guenter On Sat, Feb 11, 2017 at 02:59:08PM -0800, Guenter Roeck wrote: > After commit 'of: fix of_node leak caused in of_find_node_opts_by_path', > the following error may be reported when running omap images. > > OF: ERROR: Bad of_node_put() on

Re: [RFC v2 03/17] dt-bindings: timer: Document Owl timer

On Mon, Feb 27, 2017 at 03:40:07PM +0100, Andreas Färber wrote: > Am 24.02.2017 um 04:40 schrieb Andreas Färber: > > The Actions Semi S500 SoC contains a timer block with two timers. > > > > Signed-off-by: Andreas Färber > > --- > > v2: new > > > >

Re: [RFC v2 03/17] dt-bindings: timer: Document Owl timer

On Mon, Feb 27, 2017 at 03:40:07PM +0100, Andreas Färber wrote: > Am 24.02.2017 um 04:40 schrieb Andreas Färber: > > The Actions Semi S500 SoC contains a timer block with two timers. > > > > Signed-off-by: Andreas Färber > > --- > > v2: new > > > >

[PATCH fixes v2] pinctrl: Really force states during suspend/resume

In case a platform only defaults a "default" set of pins, but not a "sleep" set of pins, and this particular platform suspends and resumes in a way that the pin states are not preserved by the hardware, when we resume, we would call pinctrl_single_resume() -> pinctrl_force_default() ->

[PATCH fixes v2] pinctrl: Really force states during suspend/resume

In case a platform only defaults a "default" set of pins, but not a "sleep" set of pins, and this particular platform suspends and resumes in a way that the pin states are not preserved by the hardware, when we resume, we would call pinctrl_single_resume() -> pinctrl_force_default() ->

Re: [PATCHv3 1/2] dt-bindings: Add vendor prefix for Motorola

On Thu, Feb 23, 2017 at 02:03:52AM +0100, Sebastian Reichel wrote: > Motorola was involved in semiconductor and mobile phone business. > The "motrola," prefix is already used by a couple of bindings: typo. > > * rtc/rtc-cmos.txt > * mfd/motorola-cpcap.txt > * regulator/cpcap-regulator.txt > >

Re: [PATCHv3 1/2] dt-bindings: Add vendor prefix for Motorola

On Thu, Feb 23, 2017 at 02:03:52AM +0100, Sebastian Reichel wrote: > Motorola was involved in semiconductor and mobile phone business. > The "motrola," prefix is already used by a couple of bindings: typo. > > * rtc/rtc-cmos.txt > * mfd/motorola-cpcap.txt > * regulator/cpcap-regulator.txt > >

Re: [PATCH v2 3/3] dt-bindings: mailbox: Update doc with NSP PDC/mailbox support

On Thu, Feb 23, 2017 at 09:49:52AM -0500, Steve Lin wrote: > Update the DT bindings documentation to reflect the new NSP version > of PDC driver compatibility string. > > Signed-off-by: Steve Lin > --- > Documentation/devicetree/bindings/mailbox/brcm,iproc-pdc-mbox.txt

Re: [PATCH v2 3/3] dt-bindings: mailbox: Update doc with NSP PDC/mailbox support

On Thu, Feb 23, 2017 at 09:49:52AM -0500, Steve Lin wrote: > Update the DT bindings documentation to reflect the new NSP version > of PDC driver compatibility string. > > Signed-off-by: Steve Lin > --- > Documentation/devicetree/bindings/mailbox/brcm,iproc-pdc-mbox.txt | 6 -- > 1 file

[git pull] m68knommu changes for v4.11

Hi Linus, Can you please pull the m68knommu git tree, for-next branch. Only a single change, to update the amcore board defconfig. Regards Greg The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc: Linux 4.10-rc8 (2017-02-12 13:03:20 -0800) are available in the git

[git pull] m68knommu changes for v4.11

Hi Linus, Can you please pull the m68knommu git tree, for-next branch. Only a single change, to update the amcore board defconfig. Regards Greg The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc: Linux 4.10-rc8 (2017-02-12 13:03:20 -0800) are available in the git

Re: [PATCH 2/2] ARM: dts: NSP: Add mailbox (PDC) to NSP

On Wed, Feb 22, 2017 at 03:42:26PM -0500, Steve Lin wrote: > Adds mailbox / PDC to NSP device tree. Needs new compatibility string > to differentiate from NS2 version. > > Signed-off-by: Steve Lin > --- > .../devicetree/bindings/mailbox/brcm,iproc-pdc-mbox.txt

Re: [PATCH 2/2] ARM: dts: NSP: Add mailbox (PDC) to NSP

On Wed, Feb 22, 2017 at 03:42:26PM -0500, Steve Lin wrote: > Adds mailbox / PDC to NSP device tree. Needs new compatibility string > to differentiate from NS2 version. > > Signed-off-by: Steve Lin > --- > .../devicetree/bindings/mailbox/brcm,iproc-pdc-mbox.txt | 6 -- >

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

Hi Guenter, thanks for your testing! I must admit, I'm fairly new to kernel development and a little overwhelmed by all that tools used. So I do not really know how to reproduce your test using your script. I installed qemu from the master branch and buildroot. Unfortunately, that's the point

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

Hi Guenter, thanks for your testing! I must admit, I'm fairly new to kernel development and a little overwhelmed by all that tools used. So I do not really know how to reproduce your test using your script. I installed qemu from the master branch and buildroot. Unfortunately, that's the point

Re: [PATCHv3 2/2] rtc: cpcap: new rtc driver

On Thu, Feb 23, 2017 at 02:03:53AM +0100, Sebastian Reichel wrote: > This driver supports the Motorola CPCAP PMIC found on > some of Motorola's mobile phones, such as the Droid 4. > > Tested-by: Tony Lindgren > Signed-off-by: Sebastian Reichel > --- > >

Re: [PATCHv3 2/2] rtc: cpcap: new rtc driver

On Thu, Feb 23, 2017 at 02:03:53AM +0100, Sebastian Reichel wrote: > This driver supports the Motorola CPCAP PMIC found on > some of Motorola's mobile phones, such as the Droid 4. > > Tested-by: Tony Lindgren > Signed-off-by: Sebastian Reichel > --- > > Changes since PATCHv2: > - checkpatch

Re: [PATCH RESEND] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Tue, 2017-02-28 at 00:21 +0200, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. > Signed-off-by: Ruslan Bilovol While I think

Re: [PATCH RESEND] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Tue, 2017-02-28 at 00:21 +0200, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. > Signed-off-by: Ruslan Bilovol While I think all the defconfigs that

Re: [PATCH] fpga fr br: separate freeze bridge driver code

Hi Matthew, small nit inline. On Mon, Feb 27, 2017 at 12:03 PM, wrote: > From: Matthew Gerlach > > This patch separates the core Freeze Bridge > driver code from the platform driver code. > The intent is to allow the core driver code

Re: [REGRESSION] pinctrl, of, unable to find hogs

* Gary Bisson [170227 13:08]: > Hi Tony, > > On Mon, Feb 27, 2017 at 10:45:35AM -0800, Tony Lindgren wrote: > > * Tony Lindgren [170227 09:37]: > > > * Gary Bisson [170227 08:42]: > > > > > Not sure how to fix

Re: [PATCH] fpga fr br: separate freeze bridge driver code

Hi Matthew, small nit inline. On Mon, Feb 27, 2017 at 12:03 PM, wrote: > From: Matthew Gerlach > > This patch separates the core Freeze Bridge > driver code from the platform driver code. > The intent is to allow the core driver code > to be used without requiring platform driver support. > >

Re: [REGRESSION] pinctrl, of, unable to find hogs

* Gary Bisson [170227 13:08]: > Hi Tony, > > On Mon, Feb 27, 2017 at 10:45:35AM -0800, Tony Lindgren wrote: > > * Tony Lindgren [170227 09:37]: > > > * Gary Bisson [170227 08:42]: > > > > > Not sure how to fix it though since we can't move the dt probing > > > > > before > > > > > radix tree

Re: [PATCH] f2fs: add F2FS_DIRTY_DATA to has_not_enough_free_secs and need_SSR

On 02/25, Yunlong Song wrote: > The benefit is much, let me give an example to make the point more clear, the > reserved_sections for a 64G image is > about 500M, and if the current free_sections is 600M, and the IO pattern is > like this: > > Before this patch: > time 1: node & dent * imeta

Re: [PATCH] f2fs: add F2FS_DIRTY_DATA to has_not_enough_free_secs and need_SSR

On 02/25, Yunlong Song wrote: > The benefit is much, let me give an example to make the point more clear, the > reserved_sections for a 64G image is > about 500M, and if the current free_sections is 600M, and the IO pattern is > like this: > > Before this patch: > time 1: node & dent * imeta

Re: [RFC PATCH] mm, hotplug: get rid of auto_online_blocks

On Mon, Feb 27, 2017 at 10:28:17AM +0100, Michal Hocko wrote: diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h index 134a2f69c21a..a72f7f64ee26 100644 --- a/include/linux/memory_hotplug.h +++ b/include/linux/memory_hotplug.h @@ -100,8 +100,6 @@ extern void

Re: [RFC][PATCH v2] drm: kirin: Add a mutex to avoid fb initialization race

On Sat, Feb 25, 2017 at 11:36 AM, Daniel Vetter wrote: > On Fri, Feb 24, 2017 at 05:25:16PM -0800, John Stultz wrote: >> In some cases I've been seeing a race where two framebuffers >> would be initialized, as kirin_fbdev_output_poll_changed() >> might get called quickly in

Re: [LSF/MM TOPIC] do we really need PG_error at all?

On Mon, Feb 27 2017, Andreas Dilger wrote: > > My thought is that PG_error is definitely useful for applications to get > correct errors back when doing write()/sync_file_range() so that they know > there is an error in the data that _they_ wrote, rather than receiving an > error for data that

Re: [RFC PATCH] mm, hotplug: get rid of auto_online_blocks

On Mon, Feb 27, 2017 at 10:28:17AM +0100, Michal Hocko wrote: diff --git a/include/linux/memory_hotplug.h b/include/linux/memory_hotplug.h index 134a2f69c21a..a72f7f64ee26 100644 --- a/include/linux/memory_hotplug.h +++ b/include/linux/memory_hotplug.h @@ -100,8 +100,6 @@ extern void

Re: [RFC][PATCH v2] drm: kirin: Add a mutex to avoid fb initialization race

On Sat, Feb 25, 2017 at 11:36 AM, Daniel Vetter wrote: > On Fri, Feb 24, 2017 at 05:25:16PM -0800, John Stultz wrote: >> In some cases I've been seeing a race where two framebuffers >> would be initialized, as kirin_fbdev_output_poll_changed() >> might get called quickly in succession, resulting

Re: [LSF/MM TOPIC] do we really need PG_error at all?

On Mon, Feb 27 2017, Andreas Dilger wrote: > > My thought is that PG_error is definitely useful for applications to get > correct errors back when doing write()/sync_file_range() so that they know > there is an error in the data that _they_ wrote, rather than receiving an > error for data that

[GIT PULL] workqueue changes for v4.11-rc1

Hello, Just one patch to silence clang's warnings. Thanks. The following changes since commit 6d04dfc8966019b8b0977b2cb942351f13d2b178: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-02-01 11:52:27 -0800) are available in the git repository at:

[GIT PULL] workqueue changes for v4.11-rc1

Hello, Just one patch to silence clang's warnings. Thanks. The following changes since commit 6d04dfc8966019b8b0977b2cb942351f13d2b178: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-02-01 11:52:27 -0800) are available in the git repository at:

mmotm 2017-02-27-15-18 uploaded

The mm-of-the-moment snapshot 2017-02-27-15-18 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2017-02-27-15-18 uploaded

The mm-of-the-moment snapshot 2017-02-27-15-18 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH] cpufreq: intel_pstate: Fix operation mode switching

From: Rafael J. Wysocki There is a problem with intel_pstate operation mode switching introduced by commit fb1fe1041c04 (cpufreq: intel_pstate: Operation mode control from sysfs), because the global sysfs limits are preserved across operation modes while per-policy

[PATCH] cpufreq: intel_pstate: Fix operation mode switching

From: Rafael J. Wysocki There is a problem with intel_pstate operation mode switching introduced by commit fb1fe1041c04 (cpufreq: intel_pstate: Operation mode control from sysfs), because the global sysfs limits are preserved across operation modes while per-policy limits are reinitialized from

[PATCH] scsi: lpfc: use div_u64 for 64-bit division

The new debugfs output causes a link error on 32-bit architectures: ERROR: "__aeabi_uldivmod" [drivers/scsi/lpfc/lpfc.ko] undefined! This code is not performance critical, so we can simply use div_u64(). Fixes: bd2cdd5e400f ("scsi: lpfc: NVME Initiator: Add debugfs support") Fixes: 2b65e18202fd

[PATCH] scsi: lpfc: use div_u64 for 64-bit division

The new debugfs output causes a link error on 32-bit architectures: ERROR: "__aeabi_uldivmod" [drivers/scsi/lpfc/lpfc.ko] undefined! This code is not performance critical, so we can simply use div_u64(). Fixes: bd2cdd5e400f ("scsi: lpfc: NVME Initiator: Add debugfs support") Fixes: 2b65e18202fd

Re: [PATCH 3/3] ath9k: ahb: Add OF support

On Mon, 27 Feb 2017 22:13:21 +0100 Rafał Miłecki wrote: > Why you didn't cc linux-wireless?!?! I first wanted to be sure that the devdata part was generally acceptable, this patch was just included as an example of a user. But it sound like that part will have to move to nvmem

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On Mon, 27 Feb 2017 14:45:37 -0800 David Daney wrote: > On 02/27/2017 02:36 PM, Steven Rostedt wrote: > > On Mon, 27 Feb 2017 14:21:21 -0800 > > David Daney wrote: > > > >> See attached for mips. It seems to do the right thing. > >> > >>

Re: [PATCH 3/3] ath9k: ahb: Add OF support

On Mon, 27 Feb 2017 22:13:21 +0100 Rafał Miłecki wrote: > Why you didn't cc linux-wireless?!?! I first wanted to be sure that the devdata part was generally acceptable, this patch was just included as an example of a user. But it sound like that part will have to move to nvmem first. I'll come

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On Mon, 27 Feb 2017 14:45:37 -0800 David Daney wrote: > On 02/27/2017 02:36 PM, Steven Rostedt wrote: > > On Mon, 27 Feb 2017 14:21:21 -0800 > > David Daney wrote: > > > >> See attached for mips. It seems to do the right thing. > >> > >> I leave it as an exercise to the reader to fix the

Re: [PATCH 1/2] video: fbdev: imxfb: support AUS mode

Hello Uwe, Thus wrote Uwe Kleine-König (u.kleine-koe...@pengutronix.de): > given fbdev is orphaned > (http://git.kernel.org/linus/238600783d7470bec19350b0ee79e01825d3c84f) fbdev is no longer orphaned, Bartlomiej is the new maintainer. > I think it would be nice to move the imxfb driver over to

Re: [PATCH 1/2] video: fbdev: imxfb: support AUS mode

Hello Uwe, Thus wrote Uwe Kleine-König (u.kleine-koe...@pengutronix.de): > given fbdev is orphaned > (http://git.kernel.org/linus/238600783d7470bec19350b0ee79e01825d3c84f) fbdev is no longer orphaned, Bartlomiej is the new maintainer. > I think it would be nice to move the imxfb driver over to

Re: [PATCH] pinctrl: Really force states during suspend/resume

On Thu, Feb 23, 2017 at 12:30 PM, Linus Walleij wrote: > On Wed, Feb 8, 2017 at 10:46 PM, Andy Shevchenko > wrote: > >> Btw, I have got similar issue and thinking about those states they are >> quite orthogonal to the pin states. Wouldn't be

Re: [PATCH] pinctrl: Really force states during suspend/resume

On Thu, Feb 23, 2017 at 12:30 PM, Linus Walleij wrote: > On Wed, Feb 8, 2017 at 10:46 PM, Andy Shevchenko > wrote: > >> Btw, I have got similar issue and thinking about those states they are >> quite orthogonal to the pin states. Wouldn't be better to actually >> differentiate PM related states

Re: [PATCH v1 1/2] dt-bindings: Document the Synopsys DW AXI DMA bindings

On Tue, Feb 21, 2017 at 11:38:03PM +0300, Eugeniy Paltsev wrote: > This patch adds documentation of device tree bindings for the Synopsys > DesignWare AXI DMA controller. > > Signed-off-by: Eugeniy Paltsev > --- > .../devicetree/bindings/dma/snps,axi-dw-dmac.txt

Re: [PATCH v1 1/2] dt-bindings: Document the Synopsys DW AXI DMA bindings

On Tue, Feb 21, 2017 at 11:38:03PM +0300, Eugeniy Paltsev wrote: > This patch adds documentation of device tree bindings for the Synopsys > DesignWare AXI DMA controller. > > Signed-off-by: Eugeniy Paltsev > --- > .../devicetree/bindings/dma/snps,axi-dw-dmac.txt | 34 > ++

Re: [PATCHv2 1/5] dt-bindings: mfd: Add Altera Arria10 SR Reset Controller bindings

On Wed, Feb 22, 2017 at 11:10:15AM -0600, thor.tha...@linux.intel.com wrote: > From: Thor Thayer > > This patch adds documentation for the Altera A10-SR Reset > Controller DT bindings. > > Signed-off-by: Thor Thayer > --- > v2 No

Re: [PATCHv2 1/5] dt-bindings: mfd: Add Altera Arria10 SR Reset Controller bindings

On Wed, Feb 22, 2017 at 11:10:15AM -0600, thor.tha...@linux.intel.com wrote: > From: Thor Thayer > > This patch adds documentation for the Altera A10-SR Reset > Controller DT bindings. > > Signed-off-by: Thor Thayer > --- > v2 No change > --- >

Re: [PATCH v2 1/2] dts: mfd: axp20x: Add "xpowers,master-mode" property for AXP806 PMICs

On Wed, Feb 22, 2017 at 08:41:02PM +0100, Rask Ingemann Lambertsen wrote: > commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot") > was intended to fix the case where a board uses an AXP806 in slave mode, > but the boot loader leaves it in master mode for lack of AXP806

Re: [PATCH v2 1/2] dts: mfd: axp20x: Add "xpowers,master-mode" property for AXP806 PMICs

On Wed, Feb 22, 2017 at 08:41:02PM +0100, Rask Ingemann Lambertsen wrote: > commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot") > was intended to fix the case where a board uses an AXP806 in slave mode, > but the boot loader leaves it in master mode for lack of AXP806

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 05:45 PM, David Daney wrote: On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an exercise to the reader to fix the other

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

On 02/27/2017 05:45 PM, David Daney wrote: On 02/27/2017 02:36 PM, Steven Rostedt wrote: On Mon, 27 Feb 2017 14:21:21 -0800 David Daney wrote: See attached for mips. It seems to do the right thing. I leave it as an exercise to the reader to fix the other architectures. Consult your own

Re: [PATCH] mm,x86: fix SMP x86 32bit build for native_pud_clear()

> On 02/15/2017 12:31 PM, Dave Jiang wrote: >> The fix introduced by e4decc90 to fix the UP case for 32bit x86, however >> that broke the SMP case that was working previously. Add ifdef so the dummy >> function only show up for 32bit UP case only. >> >> Fix: e4decc90 mm,x86: native_pud_clear

Re: [PATCH] mm,x86: fix SMP x86 32bit build for native_pud_clear()

> On 02/15/2017 12:31 PM, Dave Jiang wrote: >> The fix introduced by e4decc90 to fix the UP case for 32bit x86, however >> that broke the SMP case that was working previously. Add ifdef so the dummy >> function only show up for 32bit UP case only. >> >> Fix: e4decc90 mm,x86: native_pud_clear

Re: [PATCH 3/3] ath9k: ahb: Add OF support

On 27 February 2017 at 23:48, Alban wrote: > On Mon, 27 Feb 2017 22:13:21 +0100 > Rafał Miłecki wrote: > >> Why you didn't cc linux-wireless?!?! > > I first wanted to be sure that the devdata part was generally > acceptable, this patch was just included as an

Re: [PATCH 3/3] ath9k: ahb: Add OF support

On 27 February 2017 at 23:48, Alban wrote: > On Mon, 27 Feb 2017 22:13:21 +0100 > Rafał Miłecki wrote: > >> Why you didn't cc linux-wireless?!?! > > I first wanted to be sure that the devdata part was generally > acceptable, this patch was just included as an example of a user. > But it sound

[PATCH v2] mfd: Add Cherrytrail WhiskeyCove PMIC driver

Add mfd driver for Intel CHT WhiskeyCove PMIC, based on various non upstreamed CHT WhiskeyCove PMIC patches. For now this just adds a minimal version which implements just enough to get ACPI PMIC opregion support to work, so that suspend/resume will work on machines with this PMIC. Cc: Bin Gao

Re: [PATCH v5] usb: misc: add USB251xB/xBi Hi-Speed Hub Controller Driver

On Mon, Feb 27, 2017 at 3:48 AM, Jan Lübbe wrote: > On Di, 2017-02-21 at 15:57 +0100, Richard Leitner wrote: >> >>> This is a lot of properties. Are you really finding a need for all of >> >>> them? Is this to handle h/w designers too cheap to put down the EEPROM? >> >>>

[PATCH v2] mfd: Add Cherrytrail WhiskeyCove PMIC driver

Add mfd driver for Intel CHT WhiskeyCove PMIC, based on various non upstreamed CHT WhiskeyCove PMIC patches. For now this just adds a minimal version which implements just enough to get ACPI PMIC opregion support to work, so that suspend/resume will work on machines with this PMIC. Cc: Bin Gao

Re: [PATCH v5] usb: misc: add USB251xB/xBi Hi-Speed Hub Controller Driver

On Mon, Feb 27, 2017 at 3:48 AM, Jan Lübbe wrote: > On Di, 2017-02-21 at 15:57 +0100, Richard Leitner wrote: >> >>> This is a lot of properties. Are you really finding a need for all of >> >>> them? Is this to handle h/w designers too cheap to put down the EEPROM? >> >>> Maybe better to just

Re: [PATCH v2 2/3] media: dt-bindings: vpif: extend the example with an output port

On Wed, Feb 22, 2017 at 02:43:46PM +0100, Bartosz Golaszewski wrote: > This makes the example more or less correspond with the da850-evm > hardware setup. > > Signed-off-by: Bartosz Golaszewski > --- > .../devicetree/bindings/media/ti,da850-vpif.txt| 40 >

Re: [PATCH v2 2/3] media: dt-bindings: vpif: extend the example with an output port

On Wed, Feb 22, 2017 at 02:43:46PM +0100, Bartosz Golaszewski wrote: > This makes the example more or less correspond with the da850-evm > hardware setup. > > Signed-off-by: Bartosz Golaszewski > --- > .../devicetree/bindings/media/ti,da850-vpif.txt| 40 > +- > 1 file

Re: [PATCH v2 1/3] soc: qcom: Add scm call to protect modem mem in qcom scm driver.

On 01/30, Avaneesh Kumar Dwivedi wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index 893f953ea..f476803 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -292,6 +292,20 @@ int qcom_scm_pas_shutdown(u32 peripheral) > } >

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 02:06:27PM -0500, Paolo Bonzini wrote: > > > + if (!boot_cpu_has(X86_FEATURE_NONSTOP_TSC)) > > > + mark_tsc_unstable("not invariant"); > > > > Errm, no. > > > > That makes TSC unusable for systems which do not go into C/P states in > > which the TSC stops. There

Re: [PATCH v2 3/3] remoteproc: qcom: Add msm8996 specific changes in mss rproc driver.

On 01/30, Avaneesh Kumar Dwivedi wrote: > diff --git a/drivers/remoteproc/qcom_q6v5_pil.c > b/drivers/remoteproc/qcom_q6v5_pil.c > index 35eee68..9c12a36 100644 > --- a/drivers/remoteproc/qcom_q6v5_pil.c > +++ b/drivers/remoteproc/qcom_q6v5_pil.c > @@ -485,35 +497,99 @@ static int

Re: [PATCH v2 1/3] soc: qcom: Add scm call to protect modem mem in qcom scm driver.

On 01/30, Avaneesh Kumar Dwivedi wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index 893f953ea..f476803 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -292,6 +292,20 @@ int qcom_scm_pas_shutdown(u32 peripheral) > } >

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 02:06:27PM -0500, Paolo Bonzini wrote: > > > + if (!boot_cpu_has(X86_FEATURE_NONSTOP_TSC)) > > > + mark_tsc_unstable("not invariant"); > > > > Errm, no. > > > > That makes TSC unusable for systems which do not go into C/P states in > > which the TSC stops. There

Re: [PATCH v2 3/3] remoteproc: qcom: Add msm8996 specific changes in mss rproc driver.

On 01/30, Avaneesh Kumar Dwivedi wrote: > diff --git a/drivers/remoteproc/qcom_q6v5_pil.c > b/drivers/remoteproc/qcom_q6v5_pil.c > index 35eee68..9c12a36 100644 > --- a/drivers/remoteproc/qcom_q6v5_pil.c > +++ b/drivers/remoteproc/qcom_q6v5_pil.c > @@ -485,35 +497,99 @@ static int

[GIT PULL] percpu changes for v4.11-rc1

Hello, Linus. Contains just one minor cleanup patch which gets rid of an unnecessary irqsave/restore in the cpu dead callback. Thanks. The following changes since commit 44b4b461a0fb407507b46ea76a71376d74de7058: Merge tag 'armsoc-fixes' of

[GIT PULL] percpu changes for v4.11-rc1

Hello, Linus. Contains just one minor cleanup patch which gets rid of an unnecessary irqsave/restore in the cpu dead callback. Thanks. The following changes since commit 44b4b461a0fb407507b46ea76a71376d74de7058: Merge tag 'armsoc-fixes' of

Re: [PATCH RESEND] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Mon, Feb 27, 2017 at 2:21 PM, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. > > Signed-off-by: Ruslan Bilovol

Re: [PATCH RESEND] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks

On Mon, Feb 27, 2017 at 2:21 PM, Ruslan Bilovol wrote: > Config EXPERIMENTAL has been removed from kernel in 2013 > (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"), > there is no any reason to do these checks now. > > Signed-off-by: Ruslan Bilovol Acked-by: Kees Cook -Kees > --- >

Re: [PATCH v2 3/3] media: dt-bindings: vpif: new optional property

On Wed, Feb 22, 2017 at 02:43:47PM +0100, Bartosz Golaszewski wrote: > Add an optional property - enable-gpios - which can be used to specify > the GPIOs that must be requested to select the vpif functionality. > > Signed-off-by: Bartosz Golaszewski > --- >

Re: [PATCH v2 3/3] media: dt-bindings: vpif: new optional property

On Wed, Feb 22, 2017 at 02:43:47PM +0100, Bartosz Golaszewski wrote: > Add an optional property - enable-gpios - which can be used to specify > the GPIOs that must be requested to select the vpif functionality. > > Signed-off-by: Bartosz Golaszewski > --- >

[PATCH] x86/kdebugfs: Move boot params hierarchy under (debugfs)/x86/

From: Borislav Petkov ... since this is all x86-specific data and it makes sense to have it under x86/ logically instead in the toplevel debugfs dir. Signed-off-by: Borislav Petkov --- arch/x86/kernel/kdebugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] x86/kdebugfs: Move boot params hierarchy under (debugfs)/x86/

From: Borislav Petkov ... since this is all x86-specific data and it makes sense to have it under x86/ logically instead in the toplevel debugfs dir. Signed-off-by: Borislav Petkov --- arch/x86/kernel/kdebugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

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