Re: [PATCH v2 02/10] clk: ccu-sun8i-a33: Add CLK_SET_RATE_PARENT to ac-dig

Hi, On 17/01/2017 17:44, Maxime Ripard wrote: Hi, On Tue, Jan 17, 2017 at 03:02:22PM +0100, Mylène Josserand wrote: The audio DAI needs to set the clock rates of the ac-dig clock. To make it possible, the parent PLL audio clock rates should also be changed. This is possible via

Re: [PATCH v2 02/10] clk: ccu-sun8i-a33: Add CLK_SET_RATE_PARENT to ac-dig

Hi, On 17/01/2017 17:44, Maxime Ripard wrote: Hi, On Tue, Jan 17, 2017 at 03:02:22PM +0100, Mylène Josserand wrote: The audio DAI needs to set the clock rates of the ac-dig clock. To make it possible, the parent PLL audio clock rates should also be changed. This is possible via

Re: [RESEND RFC 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

Hi Shawn, On 1/10/2017 2:45 PM, Shawn Lin wrote: On 2017/1/10 14:41, Ritesh Harjani wrote: From: Sahitya Tummala Add new host operation ->platform_dumpregs to provide a mechanism through which host drivers can dump platform specific registers in addition to SDHC

Re: [RESEND RFC 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

Hi Shawn, On 1/10/2017 2:45 PM, Shawn Lin wrote: On 2017/1/10 14:41, Ritesh Harjani wrote: From: Sahitya Tummala Add new host operation ->platform_dumpregs to provide a mechanism through which host drivers can dump platform specific registers in addition to SDHC registers during error

Re: [RESEND PATCHv1 0/8] mmc: sdhci-msm: Provide support for enhanced strobe

On 1/17/2017 6:37 AM, Jeremy McNicoll wrote: On Tue, Jan 10, 2017 at 12:30:44PM +0530, Ritesh Harjani wrote: Hi, Resending this patch series, as no one could review it -possibly due to holidays during that time. This patch series mainly provides enhanced strobe support to sdhci-msm driver

Re: [RESEND PATCHv1 0/8] mmc: sdhci-msm: Provide support for enhanced strobe

On 1/17/2017 6:37 AM, Jeremy McNicoll wrote: On Tue, Jan 10, 2017 at 12:30:44PM +0530, Ritesh Harjani wrote: Hi, Resending this patch series, as no one could review it -possibly due to holidays during that time. This patch series mainly provides enhanced strobe support to sdhci-msm driver

Re: [RFC PATCH] initramfs: finish fput() before accessing any binary from initramfs

On Tuesday 17 January 2017 06:23 PM, Tero Kristo wrote: > On 17/01/17 13:14, Lokesh Vutla wrote: >> commit 4a9d4b024a31 ("switch fput to task_work_add") implements a >> schedule_work() for completing fput(), but did not guarantee calling >> __fput() after unpacking initramfs. Because of this,

Re: [RFC PATCH] initramfs: finish fput() before accessing any binary from initramfs

On Tuesday 17 January 2017 06:23 PM, Tero Kristo wrote: > On 17/01/17 13:14, Lokesh Vutla wrote: >> commit 4a9d4b024a31 ("switch fput to task_work_add") implements a >> schedule_work() for completing fput(), but did not guarantee calling >> __fput() after unpacking initramfs. Because of this,

Re: [PATCH v11 09/12] drm/mediatek: add dsi transfer function

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > From: shaoming chen > > add dsi read/write commands for transfer function > > Signed-off-by: shaoming chen Acked-by: CK Hu > --- >

Re: [PATCH v11 09/12] drm/mediatek: add dsi transfer function

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > From: shaoming chen > > add dsi read/write commands for transfer function > > Signed-off-by: shaoming chen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_dsi.c | 168 > - > 1 file

Re: [PATCHSET v2] slab: make memcg slab destruction scalable

On Tue, Jan 17, 2017 at 08:49:13AM -0800, Tejun Heo wrote: > Hello, > > On Tue, Jan 17, 2017 at 09:12:57AM +0900, Joonsoo Kim wrote: > > Could you confirm that your series solves the problem that is reported > > by Doug? It would be great if the result is mentioned to the patch > > description. >

Re: [PATCHSET v2] slab: make memcg slab destruction scalable

On Tue, Jan 17, 2017 at 08:49:13AM -0800, Tejun Heo wrote: > Hello, > > On Tue, Jan 17, 2017 at 09:12:57AM +0900, Joonsoo Kim wrote: > > Could you confirm that your series solves the problem that is reported > > by Doug? It would be great if the result is mentioned to the patch > > description. >

Re: [PATCH] ARM: dts: sun6i: sina31s: Enable USB OTG controller in peripheral mode

On Wed, Jan 18, 2017 at 09:01:05AM +0800, Chen-Yu Tsai wrote: > While the SinA31s does have a proper 5-pin mini USB OTG port, the ID > pin does not seem to work. The pin used in the schematics is always low, > regardless of the attached OTG cable or SoC internal pin bias settings. > > The v1.5

Re: [PATCH] ARM: dts: sun6i: sina31s: Enable USB OTG controller in peripheral mode

On Wed, Jan 18, 2017 at 09:01:05AM +0800, Chen-Yu Tsai wrote: > While the SinA31s does have a proper 5-pin mini USB OTG port, the ID > pin does not seem to work. The pin used in the schematics is always low, > regardless of the attached OTG cable or SoC internal pin bias settings. > > The v1.5

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Tue, Jan 17, 2017 at 09:58:33AM -0800, Stephen Boyd wrote: > Quoting Peter Chen (2017-01-15 19:45:51) > > > > So, you need to call phy_set_mode when switching between host and device. > > Besides, you also need to toggle VBUSVLDEXT when the external vbus > > is on or off at device mode

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Tue, Jan 17, 2017 at 09:58:33AM -0800, Stephen Boyd wrote: > Quoting Peter Chen (2017-01-15 19:45:51) > > > > So, you need to call phy_set_mode when switching between host and device. > > Besides, you also need to toggle VBUSVLDEXT when the external vbus > > is on or off at device mode

[PATCH v2] block: Don't register a registered bdi device

Following calltrace is quoted from Sreekanth Reddy's patch email, we found the same issue in our platform. link:https://patchwork.kernel.org/patch/9394471/ Observing below kernel panic while creating second raid disk on LSI SAS3008 HBA card. [ +0.55] [ cut here ] [

[PATCH v2] block: Don't register a registered bdi device

Following calltrace is quoted from Sreekanth Reddy's patch email, we found the same issue in our platform. link:https://patchwork.kernel.org/patch/9394471/ Observing below kernel panic while creating second raid disk on LSI SAS3008 HBA card. [ +0.55] [ cut here ] [

Re: [RFC 3/4] mm, page_alloc: move cpuset seqcount checking to slowpath

On Wednesday, January 18, 2017 6:16 AM Vlastimil Babka wrote: > > This is a preparation for the following patch to make review simpler. While > the primary motivation is a bug fix, this could also save some cycles in the > fast path. > This also gets kswapd involved. Dunno how frequent cpuset

Re: [RFC 3/4] mm, page_alloc: move cpuset seqcount checking to slowpath

On Wednesday, January 18, 2017 6:16 AM Vlastimil Babka wrote: > > This is a preparation for the following patch to make review simpler. While > the primary motivation is a bug fix, this could also save some cycles in the > fast path. > This also gets kswapd involved. Dunno how frequent cpuset

Re: [PATCH] printk: Correctly handle preemption in console_unlock()

On (01/18/17 14:45), Sergey Senozhatsky wrote: [..] > > there is a function that clears @console_may_schedule out of > console_sem scope - console_flush_on_panic(). > so I *may be* can think about a worst case scenario of race > condition between >

Re: [PATCH] printk: Correctly handle preemption in console_unlock()

On (01/18/17 14:45), Sergey Senozhatsky wrote: [..] > > there is a function that clears @console_may_schedule out of > console_sem scope - console_flush_on_panic(). > so I *may be* can think about a worst case scenario of race > condition between >

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On 2017-01-17 Michal Hocko wrote: > On Tue 17-01-17 14:21:14, Mel Gorman wrote: > > On Tue, Jan 17, 2017 at 02:52:28PM +0100, Michal Hocko wrote: > > > On Mon 16-01-17 11:09:34, Mel Gorman wrote: > > > [...] > > > > diff --git a/mm/vmscan.c b/mm/vmscan.c > > > > index

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On 2017-01-17 Michal Hocko wrote: > On Tue 17-01-17 14:21:14, Mel Gorman wrote: > > On Tue, Jan 17, 2017 at 02:52:28PM +0100, Michal Hocko wrote: > > > On Mon 16-01-17 11:09:34, Mel Gorman wrote: > > > [...] > > > > diff --git a/mm/vmscan.c b/mm/vmscan.c > > > > index

Re: [PATCH 12/13] pwm: jz4740: Let the pinctrl driver configure the pins

On Wed, Jan 18, 2017 at 12:14:20AM +0100, Paul Cercueil wrote: > Now that the JZ4740 and similar SoCs have a pinctrl driver, we rely on > the pins being properly configured before the driver probes. > > One inherent problem of this new approach is that the pinctrl framework > does not allow us to

Re: [PATCH 12/13] pwm: jz4740: Let the pinctrl driver configure the pins

On Wed, Jan 18, 2017 at 12:14:20AM +0100, Paul Cercueil wrote: > Now that the JZ4740 and similar SoCs have a pinctrl driver, we rely on > the pins being properly configured before the driver probes. > > One inherent problem of this new approach is that the pinctrl framework > does not allow us to

Re: [PATCH 13/13] MIPS: jz4740: Remove custom GPIO code

On Wed, Jan 18, 2017 at 12:14:21AM +0100, Paul Cercueil wrote: > All the drivers for the various hardware elements of the jz4740 SoC have > been modified to use the pinctrl framework for their pin configuration > needs. > As such, this platform code is now unused and can be deleted. > >

Re: [PATCH 13/13] MIPS: jz4740: Remove custom GPIO code

On Wed, Jan 18, 2017 at 12:14:21AM +0100, Paul Cercueil wrote: > All the drivers for the various hardware elements of the jz4740 SoC have > been modified to use the pinctrl framework for their pin configuration > needs. > As such, this platform code is now unused and can be deleted. > >

Re: [PATCH tip/core/rcu 11/20] sched,rcu: Make cond_resched() provide RCU quiescent state

On Tue, Jan 17, 2017 at 01:11:46PM +0100, Michal Hocko wrote: > On Tue 17-01-17 04:05:13, Paul E. McKenney wrote: > > On Tue, Jan 17, 2017 at 11:51:41AM +0100, Michal Hocko wrote: > > > On Mon 16-01-17 16:54:03, Paul E. McKenney wrote: > > > > On Mon, Jan 16, 2017 at 06:11:30PM +0100, Peter

Re: [PATCH tip/core/rcu 11/20] sched,rcu: Make cond_resched() provide RCU quiescent state

On Tue, Jan 17, 2017 at 01:11:46PM +0100, Michal Hocko wrote: > On Tue 17-01-17 04:05:13, Paul E. McKenney wrote: > > On Tue, Jan 17, 2017 at 11:51:41AM +0100, Michal Hocko wrote: > > > On Mon 16-01-17 16:54:03, Paul E. McKenney wrote: > > > > On Mon, Jan 16, 2017 at 06:11:30PM +0100, Peter

Re: [PATCH 00/13] Ingenic JZ4740 / JZ4780 pinctrl driver

On Wed, Jan 18, 2017 at 12:14:08AM +0100, Paul Cercueil wrote: [...] > One problem still unresolved: the pinctrl framework does not allow us to > configure each pin on demand (someone please prove me wrong), when the > various PWM channels are requested or released. For instance, the PWM >

Re: [PATCH] arm64: dts: exynos: Remove address node from usb parent node

Hi Pankaj, This issue already posted by Javier Martinez Canillas[1]. Maybe, he will post v2. [1] https://lkml.org/lkml/2017/1/10/907 - ("Re: [PATCH v2 3/3] arm64: dts: exynos: Remove unneeded unit names in Exynos5433 nodes") On 2017년 01월 18일 14:46, Pankaj Dubey wrote: > Address node does not

Re: [PATCH 00/13] Ingenic JZ4740 / JZ4780 pinctrl driver

On Wed, Jan 18, 2017 at 12:14:08AM +0100, Paul Cercueil wrote: [...] > One problem still unresolved: the pinctrl framework does not allow us to > configure each pin on demand (someone please prove me wrong), when the > various PWM channels are requested or released. For instance, the PWM >

Re: [PATCH] arm64: dts: exynos: Remove address node from usb parent node

Hi Pankaj, This issue already posted by Javier Martinez Canillas[1]. Maybe, he will post v2. [1] https://lkml.org/lkml/2017/1/10/907 - ("Re: [PATCH v2 3/3] arm64: dts: exynos: Remove unneeded unit names in Exynos5433 nodes") On 2017년 01월 18일 14:46, Pankaj Dubey wrote: > Address node does not

Re: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()

On Mon, Jan 16, 2017 at 12:01:02PM -0800, Florian Fainelli wrote: > On 01/15/2017 11:16 AM, Andrew Lunn wrote: > >>> What exactly is the relationship between these devices (a ascii-art tree > >>> or sysfs tree output might be nice) so I can try to understand what is > >>> going on here. > > > >

Re: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()

On Mon, Jan 16, 2017 at 12:01:02PM -0800, Florian Fainelli wrote: > On 01/15/2017 11:16 AM, Andrew Lunn wrote: > >>> What exactly is the relationship between these devices (a ascii-art tree > >>> or sysfs tree output might be nice) so I can try to understand what is > >>> going on here. > > > >

Re: [PATCH net-next v4 05/10] drivers: base: Add device_find_in_class_name()

On Tue, Jan 17, 2017 at 03:21:47PM -0800, Florian Fainelli wrote: > Add a helper function to lookup a device reference given a class name. > This is a preliminary patch to remove adhoc code from net/dsa/dsa.c and > make it more generic. > > Signed-off-by: Florian Fainelli >

Re: [PATCH net-next v4 05/10] drivers: base: Add device_find_in_class_name()

On Tue, Jan 17, 2017 at 03:21:47PM -0800, Florian Fainelli wrote: > Add a helper function to lookup a device reference given a class name. > This is a preliminary patch to remove adhoc code from net/dsa/dsa.c and > make it more generic. > > Signed-off-by: Florian Fainelli > --- >

Re: [RFC 4/4] mm, page_alloc: fix premature OOM when racing with cpuset mems update

On Wednesday, January 18, 2017 6:16 AM Vlastimil Babka wrote: > > @@ -3802,13 +3811,8 @@ __alloc_pages_nodemask(gfp_t gfp_mask, unsigned int > order, >* Also recalculate the starting point for the zonelist iterator or >* we could end up iterating over non-eligible zones

Re: [RFC 4/4] mm, page_alloc: fix premature OOM when racing with cpuset mems update

On Wednesday, January 18, 2017 6:16 AM Vlastimil Babka wrote: > > @@ -3802,13 +3811,8 @@ __alloc_pages_nodemask(gfp_t gfp_mask, unsigned int > order, >* Also recalculate the starting point for the zonelist iterator or >* we could end up iterating over non-eligible zones

Re: [linux-sunxi] Re: [PATCH] ASoC: sunxi: Add bindings for sun8i to SPDIF

On 17 January 2017 at 19:15, Mark Brown wrote: > On Thu, Jan 12, 2017 at 06:33:43PM +0100, codekip...@gmail.com wrote: >> From: Marcus Cooper >> >> The H3 SoC uses the same SPDIF block as found in earlier SoCs, but the >> transmit fifo is at a different

Re: [linux-sunxi] Re: [PATCH] ASoC: sunxi: Add bindings for sun8i to SPDIF

On 17 January 2017 at 19:15, Mark Brown wrote: > On Thu, Jan 12, 2017 at 06:33:43PM +0100, codekip...@gmail.com wrote: >> From: Marcus Cooper >> >> The H3 SoC uses the same SPDIF block as found in earlier SoCs, but the >> transmit fifo is at a different address. >> >> Signed-off-by: Marcus

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On 2017-01-16 Mel Gorman wrote: > > > You can easily check whether this is memcg related by trying to > > > run the same workload with cgroup_disable=memory kernel command > > > line parameter. This will put all the memcg specifics out of the > > > way. > > > > I will try booting now into

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On 2017-01-16 Mel Gorman wrote: > > > You can easily check whether this is memcg related by trying to > > > run the same workload with cgroup_disable=memory kernel command > > > line parameter. This will put all the memcg specifics out of the > > > way. > > > > I will try booting now into

[PATCH 2/3] PM / devfreq: Fix wrong trans_stat of passive devfreq device

Until now, the trans_stat information of passive devfreq is not updated. This patch updates the trans_stat information after setting the target frequency of passive devfreq device. Fixes: 996133119f57 ("PM / devfreq: Add new passive governor") Cc: sta...@vger.kernel.org Signed-off-by: Chanwoo

[PATCH 2/3] PM / devfreq: Fix wrong trans_stat of passive devfreq device

Until now, the trans_stat information of passive devfreq is not updated. This patch updates the trans_stat information after setting the target frequency of passive devfreq device. Fixes: 996133119f57 ("PM / devfreq: Add new passive governor") Cc: sta...@vger.kernel.org Signed-off-by: Chanwoo

[PATCH 0/3] PM / devfreq: Fix issues about passive governor

This patchset fix the two issues about passive governor and remove the unneeded separate _remove_devfreq() function. First, the parent devfreq device can use the governors except for the passive governor on the fly through sysfs entry and the passive devfreq device is only possible to use the

[PATCH 1/3] PM / devfreq: Fix available_governor sysfs

The devfreq using passive governor is not able to change the governor. So, the user can not change the governor through 'available_governor' sysfs entry. Also, the devfreq which don't use the passive governor is not able to change to 'passive' governor on the fly. Fixes: 996133119f57 ("PM /

[PATCH 3/3] PM / devfreq: Remove unnecessary separate _remove_devfreq()

The _remove_devfreq() releases the all resources of the devfreq device. This function is only called in the devfreq_dev_release(). For that reason, the devfreq core doesn't need to leave the _remove_devfreq() separately. This patch releases the all resources in the devfreq_dev_release() and then

[PATCH 0/3] PM / devfreq: Fix issues about passive governor

This patchset fix the two issues about passive governor and remove the unneeded separate _remove_devfreq() function. First, the parent devfreq device can use the governors except for the passive governor on the fly through sysfs entry and the passive devfreq device is only possible to use the

[PATCH 1/3] PM / devfreq: Fix available_governor sysfs

The devfreq using passive governor is not able to change the governor. So, the user can not change the governor through 'available_governor' sysfs entry. Also, the devfreq which don't use the passive governor is not able to change to 'passive' governor on the fly. Fixes: 996133119f57 ("PM /

[PATCH 3/3] PM / devfreq: Remove unnecessary separate _remove_devfreq()

The _remove_devfreq() releases the all resources of the devfreq device. This function is only called in the devfreq_dev_release(). For that reason, the devfreq core doesn't need to leave the _remove_devfreq() separately. This patch releases the all resources in the devfreq_dev_release() and then

Re: [PATCH v4 3/4] dt-bindings: phy: Add support for QMP phy

Hi Kishon, On 01/16/2017 02:19 PM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 10 January 2017 04:21 PM, Vivek Gautam wrote: Qualcomm chipsets have QMP phy controller that provides support to a number of controller, viz. PCIe, UFS, and USB. Adding dt binding information for the same.

Re: [PATCH v4 3/4] dt-bindings: phy: Add support for QMP phy

Hi Kishon, On 01/16/2017 02:19 PM, Kishon Vijay Abraham I wrote: Hi, On Tuesday 10 January 2017 04:21 PM, Vivek Gautam wrote: Qualcomm chipsets have QMP phy controller that provides support to a number of controller, viz. PCIe, UFS, and USB. Adding dt binding information for the same.

Re: [PATCH v4 15/15] lockdep: Crossrelease feature documentation

On Fri, Dec 09, 2016 at 02:12:11PM +0900, Byungchul Park wrote: [...] > +Example 1: > + > + CONTEXT XCONTEXT Y > + -- > + mutext_lock A > +lock_page B > + lock_page B > +mutext_lock A /* DEADLOCK */

Re: [PATCH v4 15/15] lockdep: Crossrelease feature documentation

On Fri, Dec 09, 2016 at 02:12:11PM +0900, Byungchul Park wrote: [...] > +Example 1: > + > + CONTEXT XCONTEXT Y > + -- > + mutext_lock A > +lock_page B > + lock_page B > +mutext_lock A /* DEADLOCK */

RE: [PATCHv2] firmware: Correct handling of fw_state_wait_timeout() return value

>From: Jakub Kicinski [mailto:jakub.kicin...@netronome.com] >Sent: Dienstag, 17. Januar 2017 22:18 > >On Tue, Jan 17, 2017 at 12:53 PM, Luis R. Rodriguez >wrote: >> On Tue, Jan 17, 2017 at 10:04:20AM -0800, Jakub Kicinski wrote: >>> On Tue, Jan 17, 2017 at 9:30 AM, Luis R.

RE: [PATCHv2] firmware: Correct handling of fw_state_wait_timeout() return value

>From: Jakub Kicinski [mailto:jakub.kicin...@netronome.com] >Sent: Dienstag, 17. Januar 2017 22:18 > >On Tue, Jan 17, 2017 at 12:53 PM, Luis R. Rodriguez >wrote: >> On Tue, Jan 17, 2017 at 10:04:20AM -0800, Jakub Kicinski wrote: >>> On Tue, Jan 17, 2017 at 9:30 AM, Luis R. Rodriguez >wrote: >>>

[RESEND PATCH v5 2/3] perf tool: add PERF_RECORD_NAMESPACES to include namespaces related info

This patch updates perf tool to examine PERF_RECORD_NAMESPACES events emitted by the kernel when fork, clone, setns or unshare are invoked. Also, it synthesizes PERF_RECORD_NAMESPACES events for processes that were running prior to invocation of perf record, the data for which is taken from

[RESEND PATCH v5 0/3] perf: add support for analyzing events for containers

Please ignore the previously sent v5 of this patchset. Currently, there is no trivial mechanism to analyze events based on containers. perf -G can be used, but it will not filter events for the containers created after perf is invoked, making it difficult to assess/ analyze performance issues of

[RESEND PATCH v5 3/3] perf tool: add cgroup identifier entry in perf report

This patch introduces a cgroup identifier entry field in perf report to identify or distinguish data of different cgroups. It uses the device number and inode number of cgroup namespace, included in perf data with the new PERF_RECORD_NAMESPACES event, as cgroup identifier. With the assumption that

[RESEND PATCH v5 2/3] perf tool: add PERF_RECORD_NAMESPACES to include namespaces related info

This patch updates perf tool to examine PERF_RECORD_NAMESPACES events emitted by the kernel when fork, clone, setns or unshare are invoked. Also, it synthesizes PERF_RECORD_NAMESPACES events for processes that were running prior to invocation of perf record, the data for which is taken from

[RESEND PATCH v5 0/3] perf: add support for analyzing events for containers

Please ignore the previously sent v5 of this patchset. Currently, there is no trivial mechanism to analyze events based on containers. perf -G can be used, but it will not filter events for the containers created after perf is invoked, making it difficult to assess/ analyze performance issues of

[RESEND PATCH v5 3/3] perf tool: add cgroup identifier entry in perf report

This patch introduces a cgroup identifier entry field in perf report to identify or distinguish data of different cgroups. It uses the device number and inode number of cgroup namespace, included in perf data with the new PERF_RECORD_NAMESPACES event, as cgroup identifier. With the assumption that

[RESEND PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

With the advert of container technologies like docker, that depend on namespaces for isolation, there is a need for tracing support for namespaces. This patch introduces new PERF_RECORD_NAMESPACES event for tracing based on namespaces related info. Signed-off-by: Hari Bathini

[RESEND PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info

With the advert of container technologies like docker, that depend on namespaces for isolation, there is a need for tracing support for namespaces. This patch introduces new PERF_RECORD_NAMESPACES event for tracing based on namespaces related info. Signed-off-by: Hari Bathini --- Changes from

Re: [PATCH v11 08/12] drm/mediatek: add dsi interrupt control

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > From: shaoming chen > > add dsi interrupt control > > Signed-off-by: shaoming chen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_dsi.c | 92 >

Re: [PATCH v11 08/12] drm/mediatek: add dsi interrupt control

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > From: shaoming chen > > add dsi interrupt control > > Signed-off-by: shaoming chen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_dsi.c | 92 > ++ > 1 file changed, 92 insertions(+) > >

Re: [PATCH v5 0/4] usb: early: add support for early printk through USB3 debug port

Hi Greg, This patch series has been there for 2 months without further comments. Will you consider it for usb-next? Best regards, Lu Baolu On 11/15/2016 02:02 PM, Lu Baolu wrote: > xHCI debug capability (DbC) is an optional but standalone > functionality provided by an xHCI host controller.

Re: [PATCH v5 0/4] usb: early: add support for early printk through USB3 debug port

Hi Greg, This patch series has been there for 2 months without further comments. Will you consider it for usb-next? Best regards, Lu Baolu On 11/15/2016 02:02 PM, Lu Baolu wrote: > xHCI debug capability (DbC) is an optional but standalone > functionality provided by an xHCI host controller.

[PATCH] mm/memblock.c: remove unnecessary log and clean up

There is no variable named flags in memblock_add() and memblock_reserve() so remove it from the log messages. This patch also cleans up the type casting for phys_addr_t by using %pa to print them. Signed-off-by: Miles Chen --- mm/memblock.c | 54

[PATCH] mm/memblock.c: remove unnecessary log and clean up

There is no variable named flags in memblock_add() and memblock_reserve() so remove it from the log messages. This patch also cleans up the type casting for phys_addr_t by using %pa to print them. Signed-off-by: Miles Chen --- mm/memblock.c | 54

[PATCH 3/6] usb: xhci-mtk: add reference clock

usually, the reference clock comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 15 +++ drivers/usb/host/xhci-mtk.h |1 + 2 files changed, 16

[PATCH 3/6] usb: xhci-mtk: add reference clock

usually, the reference clock comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/usb/host/xhci-mtk.c | 15 +++ drivers/usb/host/xhci-mtk.h |1 + 2 files changed, 16 insertions(+) diff --git

[PATCH 2/6] usb: mtu3: add reference clock

usually, the reference clock comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3.h |1 + drivers/usb/mtu3/mtu3_plat.c | 21 +++-- 2 files changed, 20

[PATCH 2/6] usb: mtu3: add reference clock

usually, the reference clock comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3.h |1 + drivers/usb/mtu3/mtu3_plat.c | 21 +++-- 2 files changed, 20 insertions(+), 2 deletions(-)

logical cpu number is discontinuity

Hi, On v4.9 and v4.10 kernel, when I booted my box which has two nodes and each nodes have 48 logical cpus (Hyper Threading is enabled), the logical cpu number is discontinuity as follows. node 0: 0-23, 256-279 node 1: 24-47, 280-303 So the following shell script fail to run. --- #!/bin/bash

logical cpu number is discontinuity

Hi, On v4.9 and v4.10 kernel, when I booted my box which has two nodes and each nodes have 48 logical cpus (Hyper Threading is enabled), the logical cpu number is discontinuity as follows. node 0: 0-23, 256-279 node 1: 24-47, 280-303 So the following shell script fail to run. --- #!/bin/bash

[PATCH 1/6] usb: mtu3: get resources that cause deferred probe earlier

Some resources such as regulator, clock usually cause deferred probe, get them earlier to avoid more ineffective processing. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_plat.c | 24 1 file changed, 12 insertions(+), 12 deletions(-)

[PATCH 6/6] dt-bindings: mt8173-mtu3: add reference clock

add a reference clock for compatibility Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/usb/mt8173-mtu3.txt| 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/mt8173-mtu3.txt

[PATCH 1/6] usb: mtu3: get resources that cause deferred probe earlier

Some resources such as regulator, clock usually cause deferred probe, get them earlier to avoid more ineffective processing. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_plat.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git

[PATCH 6/6] dt-bindings: mt8173-mtu3: add reference clock

add a reference clock for compatibility Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/usb/mt8173-mtu3.txt| 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/mt8173-mtu3.txt

[PATCH 4/6] arm64: dts: mt8173: add reference clock for usb

add 26M reference clock for ssusb and xhci nodes Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173.dtsi |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi

[PATCH 5/6] dt-bindings: mt8173-xhci: add reference clock

add a reference clock for compatibility Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/usb/mt8173-xhci.txt| 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/mt8173-xhci.txt

[PATCH 4/6] arm64: dts: mt8173: add reference clock for usb

add 26M reference clock for ssusb and xhci nodes Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173.dtsi |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi index

[PATCH 5/6] dt-bindings: mt8173-xhci: add reference clock

add a reference clock for compatibility Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/usb/mt8173-xhci.txt| 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/mt8173-xhci.txt

[PATCH v2 tip/core/rcu 07/18] rcu: Add long-term CPU kicking

Commit d2db185bfee8 ("rcu: Remove short-term CPU kicking") removed frequent calls to resched_cpu(), which means that the only time resched_cpu() is invoked is after an RCU CPU stall warning. Although this is good from an avoid-IPIs perspective, we should try to break things loose -before-

[PATCH v2 tip/core/rcu 07/18] rcu: Add long-term CPU kicking

Commit d2db185bfee8 ("rcu: Remove short-term CPU kicking") removed frequent calls to resched_cpu(), which means that the only time resched_cpu() is invoked is after an RCU CPU stall warning. Although this is good from an avoid-IPIs perspective, we should try to break things loose -before-

[PATCH v2 tip/core/rcu 05/18] rcu: Remove unneeded rcu_process_callbacks() declarations

The declarations of __rcu_process_callbacks() and rcu_process_callbacks() are not needed, as the definition of both of these functions appear before any uses. This commit therefore removes both declarations. Reported-by: "Ahmed, Iftekhar" Signed-off-by: Paul E. McKenney

[PATCH v2 tip/core/rcu 05/18] rcu: Remove unneeded rcu_process_callbacks() declarations

The declarations of __rcu_process_callbacks() and rcu_process_callbacks() are not needed, as the definition of both of these functions appear before any uses. This commit therefore removes both declarations. Reported-by: "Ahmed, Iftekhar" Signed-off-by: Paul E. McKenney Reviewed-by: Josh

[RESEND PATCH 6/6] dt-bindings: phy-mt65xx-usb: add support for mt2712 platform

add a new compatible string for "mt2712", and a new reference clock for SuperSpeed analog phy; Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/phy/phy-mt65xx-usb.txt | 81 +--- 1 file changed, 70 insertions(+), 11 deletions(-) diff --git

[RESEND PATCH 6/6] dt-bindings: phy-mt65xx-usb: add support for mt2712 platform

add a new compatible string for "mt2712", and a new reference clock for SuperSpeed analog phy; Signed-off-by: Chunfeng Yun --- .../devicetree/bindings/phy/phy-mt65xx-usb.txt | 81 +--- 1 file changed, 70 insertions(+), 11 deletions(-) diff --git

[RESEND PATCH 1/6] phy: phy-mt65xx-usb3: add reference clock of usb3 analog phy

usually, the reference clock of usb3 analog phy comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 36 1 file changed, 28

[RESEND PATCH 1/6] phy: phy-mt65xx-usb3: add reference clock of usb3 analog phy

usually, the reference clock of usb3 analog phy comes from 26M oscillator directly, but some SoCs are not, add it for compatibility. Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 36 1 file changed, 28 insertions(+), 8 deletions(-) diff

Re: [PATCH v11 07/12] drm/mediatek: cleaning up and refine

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > cleaning up unused define and refine function name and variable > > Signed-off-by: shaoming chen > Signed-off-by: YT Shen Acked-by: CK Hu > --- >

[RESEND PATCH 4/6] arm64: dts: mt8173: add a new reference clock for usb3 analog phy

add a new reference clock which comes from 26M oscillator directly for SuperSpeed analog phy. and the old one which comes for PLL is 48M for HighSpeed analog phy. Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173.dtsi |4 ++-- 1 file changed, 2

[RESEND PATCH 2/6] phy: phy-mt65xx-usb3: split SuperSpeed port into two ones

Currently usb3 port in fact includes two sub-ports, but it is not flexible for some cases, such as following one: usb3 port0 includes u2port0 and u3port0; usb2 port0 includes u2port1; If wants to support only HS, we can use u2port0 or u2port1, when select u2port0, u3port0 is not needed; If

Re: [PATCH v11 07/12] drm/mediatek: cleaning up and refine

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > cleaning up unused define and refine function name and variable > > Signed-off-by: shaoming chen > Signed-off-by: YT Shen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_dsi.c | 73 > -- >

[RESEND PATCH 4/6] arm64: dts: mt8173: add a new reference clock for usb3 analog phy

add a new reference clock which comes from 26M oscillator directly for SuperSpeed analog phy. and the old one which comes for PLL is 48M for HighSpeed analog phy. Signed-off-by: Chunfeng Yun --- arch/arm64/boot/dts/mediatek/mt8173.dtsi |4 ++-- 1 file changed, 2 insertions(+), 2

[RESEND PATCH 2/6] phy: phy-mt65xx-usb3: split SuperSpeed port into two ones

Currently usb3 port in fact includes two sub-ports, but it is not flexible for some cases, such as following one: usb3 port0 includes u2port0 and u3port0; usb2 port0 includes u2port1; If wants to support only HS, we can use u2port0 or u2port1, when select u2port0, u3port0 is not needed; If

  1   2   3   4   5   6   7   8   9   10   >