Re: [PATCH] extcon: adc-jack: add suspend/resume support

Hi Venkat, Applied it. Thanks, Chanwoo Choi 2016-06-30 17:54 GMT+09:00 Venkat Reddy Talla : > adding suspend and resume funtionality for extcon-adc-jack > driver to configure system wake up for extcon events, > also adding support to enable/disable system wakeup >

Re: [PATCH] extcon: adc-jack: add suspend/resume support

Hi Venkat, Applied it. Thanks, Chanwoo Choi 2016-06-30 17:54 GMT+09:00 Venkat Reddy Talla : > adding suspend and resume funtionality for extcon-adc-jack > driver to configure system wake up for extcon events, > also adding support to enable/disable system wakeup > through flag wakeup_source

[PATCH] device-tree: nexus7: Set phy mode to otg instead of host

In order to have the usb phy work in gadget mode, override the default host mode with otg mode. This allows gadget mode to work w/o any hacks to the dtsi file. Cc: Rob Herring Cc: Andy Gross Cc: Bjorn Andersson Cc: Stephen

[PATCH] device-tree: nexus7: Set phy mode to otg instead of host

In order to have the usb phy work in gadget mode, override the default host mode with otg mode. This allows gadget mode to work w/o any hacks to the dtsi file. Cc: Rob Herring Cc: Andy Gross Cc: Bjorn Andersson Cc: Stephen Boyd Cc: linux-arm-...@vger.kernel.org Cc: devicet...@vger.kernel.org

Re: [PATCH 03/12] PM,devfreq: Employ atomic_fetch_inc()

Hi Davidlohr, Acked-by: Chanwoo Choi Thanks, Chanwoo Choi 2016-06-21 5:05 GMT+09:00 Davidlohr Bueso : > Now that we have fetch_inc() we can stop using inc_return() - 1. > > These are very similar to the existing OP-RETURN primitives we already >

Re: [PATCH 03/12] PM,devfreq: Employ atomic_fetch_inc()

Hi Davidlohr, Acked-by: Chanwoo Choi Thanks, Chanwoo Choi 2016-06-21 5:05 GMT+09:00 Davidlohr Bueso : > Now that we have fetch_inc() we can stop using inc_return() - 1. > > These are very similar to the existing OP-RETURN primitives we already > have, except they return the value of the

Re: [PATCH 7/7] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

Hi Peter, 2016-07-01 18:42 GMT+09:00 Peter Chen : > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: Chanwoo Choi > Cc: MyungJoo Ham > Cc: Kyungmin Park

Re: [PATCH 7/7] devfreq: exynos-bus: add missing of_node_put after calling of_parse_phandle

Hi Peter, 2016-07-01 18:42 GMT+09:00 Peter Chen : > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: Chanwoo Choi > Cc: MyungJoo Ham > Cc: Kyungmin Park > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Signed-off-by: Peter Chen

Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI

Hi, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/rc-ir-spi-add-support-for-IR

Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI

Hi, [auto build test WARNING on linuxtv-media/master] [also build test WARNING on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/rc-ir-spi-add-support-for-IR

Re: [PATCH 1/7] extcon: add missing of_node_put after calling of_parse_phandle

Hi Peter, Applied it. Regards, Chanwoo Choi 2016-07-01 18:41 GMT+09:00 Peter Chen : > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: MyungJoo Ham > Cc: Chanwoo Choi

Re: [PATCH 1/7] extcon: add missing of_node_put after calling of_parse_phandle

Hi Peter, Applied it. Regards, Chanwoo Choi 2016-07-01 18:41 GMT+09:00 Peter Chen : > of_node_put needs to be called when the device node which is got > from of_parse_phandle has finished using. > > Cc: MyungJoo Ham > Cc: Chanwoo Choi > Signed-off-by: Peter Chen > --- >

[PATCH] firmware: qcom: scm: Change initcall to subsys

The patch changes the initcall for SCM to use subsys_initcall instead of arch_initcall. This corrects the order so that we don't probe defer when trying to get clks which causes issues later when the spm driver makes calls to qcom_set_warm_boot_addr(). The order became an issue due to the

[PATCH] firmware: qcom: scm: Change initcall to subsys

The patch changes the initcall for SCM to use subsys_initcall instead of arch_initcall. This corrects the order so that we don't probe defer when trying to get clks which causes issues later when the spm driver makes calls to qcom_set_warm_boot_addr(). The order became an issue due to the

[PATCH] perf/x86: fix 32-bit perf user callgraph collection

A basic perf callgraph record operation causes an immediate panic on a 32-bit kernel compiled with CONFIG_CC_STACKPROTECTOR: $ perf record -g ls Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: c0404fbd CPU: 0 PID: 998 Comm: ls Not tainted 4.7.0-rc5+ #1

[PATCH] perf/x86: fix 32-bit perf user callgraph collection

A basic perf callgraph record operation causes an immediate panic on a 32-bit kernel compiled with CONFIG_CC_STACKPROTECTOR: $ perf record -g ls Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: c0404fbd CPU: 0 PID: 998 Comm: ls Not tainted 4.7.0-rc5+ #1

Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI

Hi, [auto build test ERROR on linuxtv-media/master] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/rc-ir-spi-add-support-for-IR-LEDs

Re: [PATCH] [media] rc: ir-spi: add support for IR LEDs connected with SPI

Hi, [auto build test ERROR on linuxtv-media/master] [also build test ERROR on v4.7-rc5 next-20160701] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Andi-Shyti/rc-ir-spi-add-support-for-IR-LEDs

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

Dear Caesar & Doug, On 07/02/2016 09:34 AM, Caesar Wang wrote: > > On 2016年07月02日 00:56, Doug Anderson wrote: >> Caesar >> >> On Thu, Jun 30, 2016 at 9:32 PM, Caesar Wang wrote: >>> From: Elaine Zhang >>> >>> In order to meet low power

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

Dear Caesar & Doug, On 07/02/2016 09:34 AM, Caesar Wang wrote: > > On 2016年07月02日 00:56, Doug Anderson wrote: >> Caesar >> >> On Thu, Jun 30, 2016 at 9:32 PM, Caesar Wang wrote: >>> From: Elaine Zhang >>> >>> In order to meet low power requirements, a power management unit >>> (PMU) is >>>

kernel/trace/trace.h:516:28: error: 'struct task_struct' has no member named 'trace_recursion'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: dbdc3bb74faeec5fd92e28c15c945045d5aab426 commit: 7ef224d1d0e3a1ade02d02c01ce1dcffb736d2c3 tracing: Add 'hist' event trigger command date: 2 months ago config: x86_64-randconfig-s0-07021107 (attached as

kernel/trace/trace.h:516:28: error: 'struct task_struct' has no member named 'trace_recursion'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: dbdc3bb74faeec5fd92e28c15c945045d5aab426 commit: 7ef224d1d0e3a1ade02d02c01ce1dcffb736d2c3 tracing: Add 'hist' event trigger command date: 2 months ago config: x86_64-randconfig-s0-07021107 (attached as

[PATCH] block: do not merge requests without consulting with io scheduler

Before merging a bio into an existing request, io scheduler is called to get its approval first. However, the requests that come from a plug flush may get merged by block layer without consulting with io scheduler. In case of CFQ, this can cause fairness problems. For instance, if a request gets

[PATCH] block: do not merge requests without consulting with io scheduler

Before merging a bio into an existing request, io scheduler is called to get its approval first. However, the requests that come from a plug flush may get merged by block layer without consulting with io scheduler. In case of CFQ, this can cause fairness problems. For instance, if a request gets

[PATCHv2 1/1] thermal: sysfs: lock tz while on access to mode properties

Serialized calls to tz.ops in user facing sysfs handler mode_show() and mode_store(). Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal

[PATCHv2 1/1] thermal: sysfs: lock tz while on access to mode properties

Serialized calls to tz.ops in user facing sysfs handler mode_show() and mode_store(). Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal

Re: [PATCH v6 3/5] thermal: streamline get_trend callbacks

On Wed, Jun 22, 2016 at 04:42:03PM +0800, Caesar Wang wrote: > From: Sascha Hauer > > The .get_trend callback in struct thermal_zone_device_ops has > the prototype: > int (*get_trend) (struct thermal_zone_device *, int, > enum

Re: [PATCH v6 3/5] thermal: streamline get_trend callbacks

On Wed, Jun 22, 2016 at 04:42:03PM +0800, Caesar Wang wrote: > From: Sascha Hauer > > The .get_trend callback in struct thermal_zone_device_ops has > the prototype: > int (*get_trend) (struct thermal_zone_device *, int, > enum thermal_trend *); > whereas the

Re: [PATCH v4 1/2] Documentation: bindings: add dt doc for Rockchip PCIe controller

Hi, On Fri, Jul 01, 2016 at 02:01:09PM +0100, Marc Zyngier wrote: > On 01/07/16 02:24, Shawn Lin wrote: > > This patch adds a binding that describes the Rockchip PCIe controller > > found on Rockchip SoCs PCIe interface. > > > > Signed-off-by: Shawn Lin > > > > --- >

Re: [PATCH v4 1/2] Documentation: bindings: add dt doc for Rockchip PCIe controller

Hi, On Fri, Jul 01, 2016 at 02:01:09PM +0100, Marc Zyngier wrote: > On 01/07/16 02:24, Shawn Lin wrote: > > This patch adds a binding that describes the Rockchip PCIe controller > > found on Rockchip SoCs PCIe interface. > > > > Signed-off-by: Shawn Lin > > > > --- > > > > Changes in v4: > >

Re: [PATCH 1/4] spi: Add option to wake a device by toggling CS

On Fri, Jul 01, 2016 at 07:17:08PM +0200, Mark Brown wrote: > On Fri, Jul 01, 2016 at 10:05:50AM -0700, Doug Anderson wrote: > > > I'm curious why you you need a timer at all. Can't you just keep > > track of the jiffies that you last sent and do subtraction? ...or you > > could get even more

Re: [PATCH 1/4] spi: Add option to wake a device by toggling CS

On Fri, Jul 01, 2016 at 07:17:08PM +0200, Mark Brown wrote: > On Fri, Jul 01, 2016 at 10:05:50AM -0700, Doug Anderson wrote: > > > I'm curious why you you need a timer at all. Can't you just keep > > track of the jiffies that you last sent and do subtraction? ...or you > > could get even more

[PATCH 1/1] thermal: core: move slop and offset helpers to thermal_helpers.c

Reorganize code to reflect better placement. Cc: Zhang Rui Cc: linux...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Eduardo Valentin --- drivers/thermal/thermal_core.c| 30 --

[PATCH 1/1] thermal: core: move slop and offset helpers to thermal_helpers.c

Reorganize code to reflect better placement. Cc: Zhang Rui Cc: linux...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Eduardo Valentin --- drivers/thermal/thermal_core.c| 30 -- drivers/thermal/thermal_helpers.c | 30

Re: [PATCH 1/4] spi: Add option to wake a device by toggling CS

On Fri, Jul 01, 2016 at 09:02:30AM +0100, Mark Brown wrote: > On Wed, Jun 29, 2016 at 08:54:24PM -0700, apro...@chromium.org wrote: > > From: Andrey Pronin > > > > Some SPI devices may go to sleep after a period of inactivity > > on SPI. For such devices, if enough time has

Re: [PATCH 1/4] spi: Add option to wake a device by toggling CS

On Fri, Jul 01, 2016 at 09:02:30AM +0100, Mark Brown wrote: > On Wed, Jun 29, 2016 at 08:54:24PM -0700, apro...@chromium.org wrote: > > From: Andrey Pronin > > > > Some SPI devices may go to sleep after a period of inactivity > > on SPI. For such devices, if enough time has passed since the > >

Re: [PATCH v5 1/5] thermal: Add support for hardware-tracked trip points

On Wed, Jun 22, 2016 at 11:15:19AM +0800, Zhang Rui wrote: > On 一, 2016-06-06 at 19:44 +0800, Caesar Wang wrote: > > From: Sascha Hauer > > > > This adds support for hardware-tracked trip points to the device tree > > thermal sensor framework. > > > > The framework

Re: [PATCH v5 1/5] thermal: Add support for hardware-tracked trip points

On Wed, Jun 22, 2016 at 11:15:19AM +0800, Zhang Rui wrote: > On 一, 2016-06-06 at 19:44 +0800, Caesar Wang wrote: > > From: Sascha Hauer > > > > This adds support for hardware-tracked trip points to the device tree > > thermal sensor framework. > > > > The framework supports an arbitrary number

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

On 2016年07月02日 00:56, Doug Anderson wrote: Caesar On Thu, Jun 30, 2016 at 9:32 PM, Caesar Wang wrote: From: Elaine Zhang In order to meet low power requirements, a power management unit (PMU) is designed for controlling power resources in

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

On 2016年07月02日 00:56, Doug Anderson wrote: Caesar On Thu, Jun 30, 2016 at 9:32 PM, Caesar Wang wrote: From: Elaine Zhang In order to meet low power requirements, a power management unit (PMU) is designed for controlling power resources in RK3399. The RK3399 PMU is dedicated for managing

Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

Am Freitag, 01 Juli 2016, 17:02:23 schrieb Thiago Jung Bauermann: > Am Freitag, 01 Juli 2016, 14:36:02 schrieb Dave Young: > > On 07/01/16 at 02:51pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 30 Juni 2016, 17:43:57 schrieb Dave Young: > > > > On 06/30/16 at 01:42pm, Thiago Jung Bauermann

Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

Am Freitag, 01 Juli 2016, 17:02:23 schrieb Thiago Jung Bauermann: > Am Freitag, 01 Juli 2016, 14:36:02 schrieb Dave Young: > > On 07/01/16 at 02:51pm, Thiago Jung Bauermann wrote: > > > Am Donnerstag, 30 Juni 2016, 17:43:57 schrieb Dave Young: > > > > On 06/30/16 at 01:42pm, Thiago Jung Bauermann

Re: [PATCH v9 01/10] clk: fix initial state of critical clock's parents

(Resending to everyone) On 06/22, Erin Lo wrote: > From: James Liao > > This patch fixed wrong state of parent clocks if they are registered > after critical clocks. > > Signed-off-by: James Liao > Signed-off-by: Erin Lo

Re: [PATCH v9 01/10] clk: fix initial state of critical clock's parents

(Resending to everyone) On 06/22, Erin Lo wrote: > From: James Liao > > This patch fixed wrong state of parent clocks if they are registered > after critical clocks. > > Signed-off-by: James Liao > Signed-off-by: Erin Lo It would be nice if you included the information about the problem

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

y(cname, device->chip->name, sizeof(cname)); > cname[sizeof(cname) - 1] = '\0'; > - i = strlen(cname); > - while (i) { > - --i; > - cname[i] = tolower(cname[i]); > - } > + strtolower(cname); This function doesn't seem to exist as of next-20160701, where have you found it?

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

); > cname[sizeof(cname) - 1] = '\0'; > - i = strlen(cname); > - while (i) { > - --i; > - cname[i] = tolower(cname[i]); > - } > + strtolower(cname); This function doesn't seem to exist as of next-20160701, where have you found it?

Re: [PATCH RFC 0/7] support clk setting during kernel early boot

On 06/29, Dong Aisheng wrote: > Recently several people met the kernel complaining > "bad: scheduling from the idle thread!" issue which caused by > sleeping during kernel early booting phase by calling clk > APIs like clk_prepare_enable. > > See: > https://lkml.org/lkml/fancy/2016/1/29/695 >

Re: [PATCH RFC 0/7] support clk setting during kernel early boot

On 06/29, Dong Aisheng wrote: > Recently several people met the kernel complaining > "bad: scheduling from the idle thread!" issue which caused by > sleeping during kernel early booting phase by calling clk > APIs like clk_prepare_enable. > > See: > https://lkml.org/lkml/fancy/2016/1/29/695 >

[PATCH 1/1] thermal: qcom: remove declare local symbols as static

Trivial: remove the following: drivers/thermal/qcom/tsens-8916.c:103:24: warning: symbol 'ops_8916' was not declared. Should it be static? drivers/thermal/qcom/tsens-8996.c:76:24: warning: symbol 'ops_8996' was not declared. Should it be static? drivers/thermal/qcom/tsens-8974.c:235:24: warning:

[PATCH 1/1] thermal: qcom: remove declare local symbols as static

Trivial: remove the following: drivers/thermal/qcom/tsens-8916.c:103:24: warning: symbol 'ops_8916' was not declared. Should it be static? drivers/thermal/qcom/tsens-8996.c:76:24: warning: symbol 'ops_8996' was not declared. Should it be static? drivers/thermal/qcom/tsens-8974.c:235:24: warning:

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

On 2016年07月02日 01:09, Javier Martinez Canillas wrote: Hello Caesar, On Fri, Jul 1, 2016 at 12:32 AM, Caesar Wang wrote: From: Elaine Zhang In order to meet low power requirements, a power management unit (PMU) is designed for controlling power

Re: [PATCH v2] arm64: dts: rockchip: add the power domain node for rk3399

On 2016年07月02日 01:09, Javier Martinez Canillas wrote: Hello Caesar, On Fri, Jul 1, 2016 at 12:32 AM, Caesar Wang wrote: From: Elaine Zhang In order to meet low power requirements, a power management unit (PMU) is designed for controlling power resources in RK3399. The RK3399 PMU is

Re: [PATCH V3 4/8] clk: core: support clocks which requires parents enable (part 2)

On 06/30, Dong Aisheng wrote: > On Freescale i.MX7D platform, all clocks operations, including > enable/disable, rate change and re-parent, requires its parent clock on. > Current clock core can not support it well. > This patch adding flag CLK_OPS_PARENT_ENABLE to handle this special case in >

Re: [PATCH V3 3/8] clk: core: support clocks which requires parents enable (part 1)

On 06/30, Dong Aisheng wrote: > On Freescale i.MX7D platform, all clocks operations, including > enable/disable, rate change and re-parent, requires its parent > clock enable. Current clock core can not support it well. > This patch introduce a new flag CLK_OPS_PARENT_ENABLE to handle this >

Re: [PATCH V3 4/8] clk: core: support clocks which requires parents enable (part 2)

On 06/30, Dong Aisheng wrote: > On Freescale i.MX7D platform, all clocks operations, including > enable/disable, rate change and re-parent, requires its parent clock on. > Current clock core can not support it well. > This patch adding flag CLK_OPS_PARENT_ENABLE to handle this special case in >

Re: [PATCH V3 3/8] clk: core: support clocks which requires parents enable (part 1)

On 06/30, Dong Aisheng wrote: > On Freescale i.MX7D platform, all clocks operations, including > enable/disable, rate change and re-parent, requires its parent > clock enable. Current clock core can not support it well. > This patch introduce a new flag CLK_OPS_PARENT_ENABLE to handle this >

Re: [PATCH 1/3] namei: add LOOKUP_DFD_ROOT to use dfd as root

On Tue, Jun 28, 2016 at 10:38:28AM -0700, Andrey Vagin wrote: > The problem is that a pathname can contain absolute symlinks and now > they are resolved relative to the current root. > > If we want to open a file in another mount namespaces and we have a file > descriptor to its root directory,

Re: [PATCH 1/3] namei: add LOOKUP_DFD_ROOT to use dfd as root

On Tue, Jun 28, 2016 at 10:38:28AM -0700, Andrey Vagin wrote: > The problem is that a pathname can contain absolute symlinks and now > they are resolved relative to the current root. > > If we want to open a file in another mount namespaces and we have a file > descriptor to its root directory,

Re: [PATCH V3 1/8] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions

On 06/30, Dong Aisheng wrote: > This can be useful when clock core wants to enable/disable clocks. > Then we don't have to convert the struct clk_core to struct clk to call > clk_enable/clk_disable which is a bit un-align with exist using. > > And after introduce clk_core_{enable|disable}_lock,

Re: [PATCH V3 2/8] clk: move clk_disable_unused after clk_core_disable_unprepare function

On 06/30, Dong Aisheng wrote: > No function level change, just moving code place. > clk_disable_unused function will need to call clk_core_prepare_enable/ > clk_core_disable_unprepare when adding CLK_OPS_PARENT_ENABLE features. > So move it after clk_core_disable_unprepare to avoid adding forward

Re: [PATCH V3 1/8] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions

On 06/30, Dong Aisheng wrote: > This can be useful when clock core wants to enable/disable clocks. > Then we don't have to convert the struct clk_core to struct clk to call > clk_enable/clk_disable which is a bit un-align with exist using. > > And after introduce clk_core_{enable|disable}_lock,

Re: [PATCH V3 2/8] clk: move clk_disable_unused after clk_core_disable_unprepare function

On 06/30, Dong Aisheng wrote: > No function level change, just moving code place. > clk_disable_unused function will need to call clk_core_prepare_enable/ > clk_core_disable_unprepare when adding CLK_OPS_PARENT_ENABLE features. > So move it after clk_core_disable_unprepare to avoid adding forward

Re: [PATCH V3 5/8] clk: imx: re-order and concentrate the same type of clk api

On 06/30, Dong Aisheng wrote: > Re-order and concentrate the same type of clk api for better > code maintenance. > > Cc: Shawn Guo > Signed-off-by: Dong Aisheng > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora

Re: [PATCH V3 6/8] clk: imx: add clk api for supporting CLK_OPS_PARENT_ENABLE clocks

On 06/30, Dong Aisheng wrote: > IMX SoCs like i.MX7D requires using CLK_OPS_PARENT_ENABLE flags, > adding the corresponding clock APIs variants for easily to use. > > Cc: Michael Turquette > Cc: Stephen Boyd > Cc: Shawn Guo >

Re: [PATCH V3 5/8] clk: imx: re-order and concentrate the same type of clk api

On 06/30, Dong Aisheng wrote: > Re-order and concentrate the same type of clk api for better > code maintenance. > > Cc: Shawn Guo > Signed-off-by: Dong Aisheng > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative

Re: [PATCH V3 6/8] clk: imx: add clk api for supporting CLK_OPS_PARENT_ENABLE clocks

On 06/30, Dong Aisheng wrote: > IMX SoCs like i.MX7D requires using CLK_OPS_PARENT_ENABLE flags, > adding the corresponding clock APIs variants for easily to use. > > Cc: Michael Turquette > Cc: Stephen Boyd > Cc: Shawn Guo > Signed-off-by: Dong Aisheng > --- Applied to clk-next --

Re: [PATCH V3 7/8] clk: imx7d: using api with flag CLK_OPS_PARENT_ENABLE

On 06/30, Dong Aisheng wrote: > i.MX7D requires all clocks operations including enable/disable, > rate change and re-parent with its parent clock on. > Changing to the correct APIs to tell clk core such requirement. > > Cc: Michael Turquette > Cc: Stephen Boyd

Re: [PATCH V3 8/8] clk: imx7d: only enable minimum required clocks

On 06/30, Dong Aisheng wrote: > Formerly clk core does not support imx7d clock type well that all > its clock operations requires the parent clock on. > Therefore we enabled all clocks by default in clock driver > initialization for other module clocks operate well. > > After patch 'clk: imx7d:

Re: [PATCH V3 8/8] clk: imx7d: only enable minimum required clocks

On 06/30, Dong Aisheng wrote: > Formerly clk core does not support imx7d clock type well that all > its clock operations requires the parent clock on. > Therefore we enabled all clocks by default in clock driver > initialization for other module clocks operate well. > > After patch 'clk: imx7d:

Re: [PATCH V3 7/8] clk: imx7d: using api with flag CLK_OPS_PARENT_ENABLE

On 06/30, Dong Aisheng wrote: > i.MX7D requires all clocks operations including enable/disable, > rate change and re-parent with its parent clock on. > Changing to the correct APIs to tell clk core such requirement. > > Cc: Michael Turquette > Cc: Stephen Boyd > Cc: Shawn Guo > Signed-off-by:

Re: [PATCH v3 5/7] PCI: Do not use IORESOURCE_STARTALIGN to identify bridge resources

On Fri, Jul 01, 2016 at 03:04:10PM +0800, Yongji Xie wrote: >Hi Gavin, > >On 2016/7/1 10:34, Gavin Shan wrote: > >>On Thu, Jun 30, 2016 at 06:53:11PM +0800, Yongji Xie wrote: >>>Now we use the IORESOURCE_STARTALIGN to identify bridge resources >>>in __assign_resources_sorted(). That's quite

Re: [PATCH v3 5/7] PCI: Do not use IORESOURCE_STARTALIGN to identify bridge resources

On Fri, Jul 01, 2016 at 03:04:10PM +0800, Yongji Xie wrote: >Hi Gavin, > >On 2016/7/1 10:34, Gavin Shan wrote: > >>On Thu, Jun 30, 2016 at 06:53:11PM +0800, Yongji Xie wrote: >>>Now we use the IORESOURCE_STARTALIGN to identify bridge resources >>>in __assign_resources_sorted(). That's quite

Re: [PATCH v3 2/7] PCI: Ignore enforced alignment to VF BARs

On Fri, Jul 01, 2016 at 02:40:16PM +0800, Yongji Xie wrote: >Hi Gavin, > >On 2016/7/1 14:05, Gavin Shan wrote: > >>On Fri, Jul 01, 2016 at 01:27:17PM +0800, Yongji Xie wrote: On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote: >VF BARs are read-only zeroes according to SRIOV spec,

Re: [PATCH v3 2/7] PCI: Ignore enforced alignment to VF BARs

On Fri, Jul 01, 2016 at 02:40:16PM +0800, Yongji Xie wrote: >Hi Gavin, > >On 2016/7/1 14:05, Gavin Shan wrote: > >>On Fri, Jul 01, 2016 at 01:27:17PM +0800, Yongji Xie wrote: On Thu, Jun 30, 2016 at 06:53:08PM +0800, Yongji Xie wrote: >VF BARs are read-only zeroes according to SRIOV spec,

[GIT PULL] irqchip: Core changes for v4.8 (second set)

Hi Thomas, Here's the second round of changes for irqchip. This driver for Aspeed has been in -next for six runs. This is an incremental pull request from tags/irqchip-core-4.8 up to tags/irqchip-core-4.8-2 on the irqchip/core branch. Please pull. thx, Jason. The following changes since

[GIT PULL] irqchip: Core changes for v4.8 (second set)

Hi Thomas, Here's the second round of changes for irqchip. This driver for Aspeed has been in -next for six runs. This is an incremental pull request from tags/irqchip-core-4.8 up to tags/irqchip-core-4.8-2 on the irqchip/core branch. Please pull. thx, Jason. The following changes since

Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags

On 06/29, Jongsung Kim wrote: > On 2016년 06월 29일 06:18, Michael Turquette wrote: > > Quoting Rob Herring (2016-06-28 13:55:18) > >> On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: > >>> There is no way to set additional flags for a DT-initialized fixed- > >>> factor-clock, and it can

Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags

On 06/29, Jongsung Kim wrote: > On 2016년 06월 29일 06:18, Michael Turquette wrote: > > Quoting Rob Herring (2016-06-28 13:55:18) > >> On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: > >>> There is no way to set additional flags for a DT-initialized fixed- > >>> factor-clock, and it can

Re: [PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller.

Hi Mika, On Fri, May 06, 2016 at 08:22:16AM +0300, mika.pentt...@nextfour.com wrote: > From: Mika Penttilä > > Multitouch protocol B support. > > v5: > - rebased to 4.6.0-rc6 > > v4: > - cleanups and fixes according to review feedback > - irq and reset gpios

Re: [PATCH v5 1/2] Input: Driver for SiS 9200 family I2C touchscreen controller.

Hi Mika, On Fri, May 06, 2016 at 08:22:16AM +0300, mika.pentt...@nextfour.com wrote: > From: Mika Penttilä > > Multitouch protocol B support. > > v5: > - rebased to 4.6.0-rc6 > > v4: > - cleanups and fixes according to review feedback > - irq and reset gpios are now optional, > if

Re: [PATCH RFC] sched: Make wake_up_nohz_cpu() handle CPUs going offline

On Sat, Jul 02, 2016 at 01:49:56AM +0200, Frederic Weisbecker wrote: > On Fri, Jul 01, 2016 at 11:40:54AM -0700, Paul E. McKenney wrote: > > On Fri, Jul 01, 2016 at 01:29:59AM +0200, Frederic Weisbecker wrote: > > > > +/* > > > > + * Wake up the specified CPU. If the CPU is going offline, it is

Re: [PATCH RFC] sched: Make wake_up_nohz_cpu() handle CPUs going offline

On Sat, Jul 02, 2016 at 01:49:56AM +0200, Frederic Weisbecker wrote: > On Fri, Jul 01, 2016 at 11:40:54AM -0700, Paul E. McKenney wrote: > > On Fri, Jul 01, 2016 at 01:29:59AM +0200, Frederic Weisbecker wrote: > > > > +/* > > > > + * Wake up the specified CPU. If the CPU is going offline, it is

[GIT PULL] clk fixes for v4.7-rc5

The following changes since commit 72ad679aa7182d23d269cbe4d655f7e129d3b057: clk: nxp: Select MFD_SYSCON for creg driver (2016-06-01 15:14:06 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to

[GIT PULL] clk fixes for v4.7-rc5

The following changes since commit 72ad679aa7182d23d269cbe4d655f7e129d3b057: clk: nxp: Select MFD_SYSCON for creg driver (2016-06-01 15:14:06 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to

Re: [PATCH v2] clk: Add fractional scale clock support

Hi Stephen, On Fri, Jul 1, 2016 at 11:38 AM, Stephen Boyd wrote: > Sorry I replied offlist before. Pressed the wrong key. > > On 06/30, Hoan Tran wrote: >> On Thu, Jun 30, 2016 at 1:23 PM, Stephen Boyd wrote: >> > >> > How is this different from

Re: [PATCH v2] clk: Add fractional scale clock support

Hi Stephen, On Fri, Jul 1, 2016 at 11:38 AM, Stephen Boyd wrote: > Sorry I replied offlist before. Pressed the wrong key. > > On 06/30, Hoan Tran wrote: >> On Thu, Jun 30, 2016 at 1:23 PM, Stephen Boyd wrote: >> > >> > How is this different from clk-fractional-divider.c? >> > >> >> This is a

Re: [PATCH v2] pinctrl: qcom: add support for EBI2

On Fri 01 Jul 16:56 PDT 2016, Linus Walleij wrote: > Add support to mux in the second external bus interface as > follows: > > - CS1 and CS2 on GPIO39 and GPIO40 as func 2 > - ADDR_7 thru ADDR_0 on GPIO123 thru GPIO130 as func 1 > - CS4, CS3 and CS0 on GPIO132, GPIO133, GPIO134 as func 1 > -

Re: [PATCH v2] pinctrl: qcom: add support for EBI2

On Fri 01 Jul 16:56 PDT 2016, Linus Walleij wrote: > Add support to mux in the second external bus interface as > follows: > > - CS1 and CS2 on GPIO39 and GPIO40 as func 2 > - ADDR_7 thru ADDR_0 on GPIO123 thru GPIO130 as func 1 > - CS4, CS3 and CS0 on GPIO132, GPIO133, GPIO134 as func 1 > -

[PATCH v2] pinctrl: qcom: add support for EBI2

Add support to mux in the second external bus interface as follows: - CS1 and CS2 on GPIO39 and GPIO40 as func 2 - ADDR_7 thru ADDR_0 on GPIO123 thru GPIO130 as func 1 - CS4, CS3 and CS0 on GPIO132, GPIO133, GPIO134 as func 1 - DATA_15 thru DATA_0 on GPIO135 thru GPIO150 as func 1 - OE on GPIO151

[PATCH v2] pinctrl: qcom: add support for EBI2

Add support to mux in the second external bus interface as follows: - CS1 and CS2 on GPIO39 and GPIO40 as func 2 - ADDR_7 thru ADDR_0 on GPIO123 thru GPIO130 as func 1 - CS4, CS3 and CS0 on GPIO132, GPIO133, GPIO134 as func 1 - DATA_15 thru DATA_0 on GPIO135 thru GPIO150 as func 1 - OE on GPIO151

Re: [PATCH RFC] sched: Make wake_up_nohz_cpu() handle CPUs going offline

On Fri, Jul 01, 2016 at 11:40:54AM -0700, Paul E. McKenney wrote: > On Fri, Jul 01, 2016 at 01:29:59AM +0200, Frederic Weisbecker wrote: > > > +/* > > > + * Wake up the specified CPU. If the CPU is going offline, it is the > > > + * caller's responsibility to deal with the lost wakeup, for

Re: [PATCH RFC] sched: Make wake_up_nohz_cpu() handle CPUs going offline

On Fri, Jul 01, 2016 at 11:40:54AM -0700, Paul E. McKenney wrote: > On Fri, Jul 01, 2016 at 01:29:59AM +0200, Frederic Weisbecker wrote: > > > +/* > > > + * Wake up the specified CPU. If the CPU is going offline, it is the > > > + * caller's responsibility to deal with the lost wakeup, for

[PATCH 3/4] tracing: Use __get_str() when manipulating strings

Use __get_str(str) rather than __get_dynamic_array(str) when deadling with strings. It is just a code cleanup, no changes on tracepoint ABI. Suggested-by: Steven Rostedt Signed-off-by: Daniel Bristot de Oliveira Reviewed-by: Steven Rostedt

[PATCH 3/4] tracing: Use __get_str() when manipulating strings

Use __get_str(str) rather than __get_dynamic_array(str) when deadling with strings. It is just a code cleanup, no changes on tracepoint ABI. Suggested-by: Steven Rostedt Signed-off-by: Daniel Bristot de Oliveira Reviewed-by: Steven Rostedt Cc: Trond Myklebust Cc: Anna Schumaker Cc: Steven

[PATCH 2/4] tracing, RAS: Cleanup on __get_str() usage

__get_str(msg) does not need (char *) operator overloading to access mgs's elements anymore. This patch substitutes ((char *)__get_str(msg))[0] usage to __get_str(msg)[0]. It is just a code cleanup, no changes on tracepoint ABI. Signed-off-by: Daniel Bristot de Oliveira

[PATCH 0/4] tracing: printk:console fix and __get_str() cleanup

This patch series fixes a problem on printk:console tracepoint that prints a blank line in the trace output after each printk message that finishes with '\n'. It also does some cleanup on __get_str() usage, that was found while fixing the printk:console tracepoint. Daniel Bristot de Oliveira

[PATCH 4/4] printk, tracing: Avoiding unneeded blank lines

Printk messages often finish with '\n' to cause a new line. But as each tracepoint is already printed in a new line, printk messages that finish with '\n' ends up adding a blank line to the trace output. For example: kworker/0:1-86[000] d...46.006949: console: [ 46.006946] usb

[PATCH 1/4] tracing: Use outer () on __get_str() definition

__get_str(str)'s definition includes a (char *) operator overloading that is not protected with outer (). This patch adds () around __get_str()'s definition, enabling some code cleanup. Suggested-by: Steven Rostedt Signed-off-by: Daniel Bristot de Oliveira

[PATCH 2/4] tracing, RAS: Cleanup on __get_str() usage

__get_str(msg) does not need (char *) operator overloading to access mgs's elements anymore. This patch substitutes ((char *)__get_str(msg))[0] usage to __get_str(msg)[0]. It is just a code cleanup, no changes on tracepoint ABI. Signed-off-by: Daniel Bristot de Oliveira Reviewed-by: Steven

[PATCH 0/4] tracing: printk:console fix and __get_str() cleanup

This patch series fixes a problem on printk:console tracepoint that prints a blank line in the trace output after each printk message that finishes with '\n'. It also does some cleanup on __get_str() usage, that was found while fixing the printk:console tracepoint. Daniel Bristot de Oliveira

  1   2   3   4   5   6   7   8   9   10   >