Re: [PATCH v15 04/13] task_isolation: add initial support

On 8/29/2016 12:48 PM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote: On 8/29/2016 12:33 PM, Peter Zijlstra wrote: On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: + /* +* Request rescheduling unless we are in full dynticks

Re: [PATCH v15 04/13] task_isolation: add initial support

On 8/29/2016 12:48 PM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote: On 8/29/2016 12:33 PM, Peter Zijlstra wrote: On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: + /* +* Request rescheduling unless we are in full dynticks

Re: [RESEND PATCH 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

On 8/29/2016 12:51 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: > > [...] > > + */ > + if (of_device_is_compatible(np, "rockchip,rk3288-usb")) > + hsotg->phy->ops->reset(hsotg->phy); > +

Re: [RESEND PATCH 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

On 8/29/2016 12:51 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: > > [...] > > + */ > + if (of_device_is_compatible(np, "rockchip,rk3288-usb")) > + hsotg->phy->ops->reset(hsotg->phy); > + You should

RE: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

The DAX lock bit is analogous to the PageLock. You can't serialise on the mapping lock; the contention will be too high. And the point of having the radix tree support the same entry for many indices is that we don't have to go and probe the radix tree multiple times looking for the first or

RE: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

The DAX lock bit is analogous to the PageLock. You can't serialise on the mapping lock; the contention will be too high. And the point of having the radix tree support the same entry for many indices is that we don't have to go and probe the radix tree multiple times looking for the first or

Re: [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

On 08/29, Masahiro Yamada wrote: > Hi Stephen, > > > 2016-08-20 4:16 GMT+09:00 Stephen Boyd : > >> > >> >> + > >> >> + parent = of_get_parent(dev->of_node); /* parent should be syscon > >> >> node */ > >> >> + regmap = syscon_node_to_regmap(parent); > >> >> +

Re: [PATCH v6 1/2] clk: uniphier: add core support code for UniPhier clock driver

On 08/29, Masahiro Yamada wrote: > Hi Stephen, > > > 2016-08-20 4:16 GMT+09:00 Stephen Boyd : > >> > >> >> + > >> >> + parent = of_get_parent(dev->of_node); /* parent should be syscon > >> >> node */ > >> >> + regmap = syscon_node_to_regmap(parent); > >> >> + of_node_put(parent); >

Re: [PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On Mon, Aug 29, 2016 at 11:11:24AM -0700, Doug Anderson wrote: > On rk3399 we explicitly set ppll in the device tree to 67600. The > ppll has one major child, pclk_pmu_src, that is the parent of lots of > other clocks. Right now nobody is setting that clock rate and we're > relying on the

Re: [PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On Mon, Aug 29, 2016 at 11:11:24AM -0700, Doug Anderson wrote: > On rk3399 we explicitly set ppll in the device tree to 67600. The > ppll has one major child, pclk_pmu_src, that is the parent of lots of > other clocks. Right now nobody is setting that clock rate and we're > relying on the

RE: [PATCH V2] ARM: dts: imx6ul iomuxc syscon is compatible to imx6q

Best Regards! Anson Huang > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: 2016-08-29 10:35 PM > To: Yongcai Huang > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > devicet...@vger.kernel.org;

RE: [PATCH V2] ARM: dts: imx6ul iomuxc syscon is compatible to imx6q

Best Regards! Anson Huang > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: 2016-08-29 10:35 PM > To: Yongcai Huang > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > devicet...@vger.kernel.org; mark.rutl...@arm.com;

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Mon, Aug 29, 2016 at 9:08 PM, Matthew Wilcox wrote: > The DAX lock bit is analogous to the PageLock. You can't serialise on the > mapping lock; the contention will be too high. I mean DAX lock bit is protected by mapping lock thus we can set/clear it for all entries

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Mon, Aug 29, 2016 at 9:08 PM, Matthew Wilcox wrote: > The DAX lock bit is analogous to the PageLock. You can't serialise on the > mapping lock; the contention will be too high. I mean DAX lock bit is protected by mapping lock thus we can set/clear it for all entries if needed. > > And the

[PATCH v2] power: bq24735-charger: Request status GPIO with initial input setup

This requests the status GPIO with initial input setup. it is required to read the GPIO status at probe time and thus correctly avoid sending i2c messages when AC is not plugged. When requesting the GPIO without initial input setup, it always reads 0 which causes probe to fail as it assumes the

[PATCH v2] power: bq24735-charger: Request status GPIO with initial input setup

This requests the status GPIO with initial input setup. it is required to read the GPIO status at probe time and thus correctly avoid sending i2c messages when AC is not plugged. When requesting the GPIO without initial input setup, it always reads 0 which causes probe to fail as it assumes the

Re: [PATCH 1/2] power: bq24735-charger: Request status GPIO with initial input setup

Le lundi 29 août 2016 à 02:36 +0200, Sebastian Reichel a écrit : > Hi, > > On Sun, Aug 28, 2016 at 07:34:45PM +0200, Paul Kocialkowski wrote: > > > > This requests the status GPIO with initial input setup. it is required > > to read the GPIO status at probe time and thus correctly avoid sending

Re: [PATCH 1/2] power: bq24735-charger: Request status GPIO with initial input setup

Le lundi 29 août 2016 à 02:36 +0200, Sebastian Reichel a écrit : > Hi, > > On Sun, Aug 28, 2016 at 07:34:45PM +0200, Paul Kocialkowski wrote: > > > > This requests the status GPIO with initial input setup. it is required > > to read the GPIO status at probe time and thus correctly avoid sending

Re: [PATCH] arm64: KVM: Save two instructions in __guest_enter()

On Mon, Aug 29, 2016 at 10:22:06AM -0500, Shanker Donthineni wrote: > Hi Christoffer, > > This is change may not provide the measurable performance > improvement, but still we can > save a few cpu cycles on vCPU context switch and also improves the > code readability. I'm not so convinced about

Re: [PATCH] arm64: KVM: Save two instructions in __guest_enter()

On Mon, Aug 29, 2016 at 10:22:06AM -0500, Shanker Donthineni wrote: > Hi Christoffer, > > This is change may not provide the measurable performance > improvement, but still we can > save a few cpu cycles on vCPU context switch and also improves the > code readability. I'm not so convinced about

Re: [PATCH] arm64: KVM: Save two instructions in __guest_enter()

On Tue, Aug 09, 2016 at 08:15:36PM -0500, Shanker Donthineni wrote: > We are doing an unnecessary stack push/pop operation when restoring > the guest registers x0-x18 in __guest_enter(). This patch saves the > two instructions by using x18 as a base register. No need to store > the vcpu context

Re: [PATCH] arm64: KVM: Save two instructions in __guest_enter()

On Tue, Aug 09, 2016 at 08:15:36PM -0500, Shanker Donthineni wrote: > We are doing an unnecessary stack push/pop operation when restoring > the guest registers x0-x18 in __guest_enter(). This patch saves the > two instructions by using x18 as a base register. No need to store > the vcpu context

[PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On rk3399 we explicitly set ppll in the device tree to 67600. The ppll has one major child, pclk_pmu_src, that is the parent of lots of other clocks. Right now nobody is setting that clock rate and we're relying on the divider to just happen to be something sane. Let's be explicit in our

[PATCH] arm64: dts: rockchip: Explicitly set pclk_pmu_src on rk3399

On rk3399 we explicitly set ppll in the device tree to 67600. The ppll has one major child, pclk_pmu_src, that is the parent of lots of other clocks. Right now nobody is setting that clock rate and we're relying on the divider to just happen to be something sane. Let's be explicit in our

[PATCH v5 12/13] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

[PATCH v5 12/13] media: platform: pxa_camera: change stop_streaming semantics

Instead of the legacy behavior where it was required to wait for all video buffers to be finished by the hardware, use a cancel like strategy : as soon as the stop_streaming() call is done, abort all DMA transfers, report the already buffers as failed and return. This makes stop_streaming() more

[PATCH v5 06/13] media: platform: pxa_camera: introduce sensor_call

Introduce sensor_call(), which will be used for all sensor invocations. This is a preparation move to v4l2 device conversion, ie. soc_camera adherence removal. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 27

[PATCH v5 11/13] media: platform: pxa_camera: add debug register access

Add pxa_camera registers access through advanced video debugging. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 32 ++ 1 file changed, 32 insertions(+) diff --git

[PATCH v5 11/13] media: platform: pxa_camera: add debug register access

Add pxa_camera registers access through advanced video debugging. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 32 ++ 1 file changed, 32 insertions(+) diff --git a/drivers/media/platform/soc_camera/pxa_camera.c

[PATCH v5 06/13] media: platform: pxa_camera: introduce sensor_call

Introduce sensor_call(), which will be used for all sensor invocations. This is a preparation move to v4l2 device conversion, ie. soc_camera adherence removal. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 27 ++ 1 file changed, 15

[PATCH v5 05/13] media: platform: pxa_camera: trivial move of functions

Move the functions in the file to be regrouped into meaningful blocks : 1. pxa camera core handling functions, manipulating the herdware 2. videobuf2 functions, dealing with video buffers 3. video ioctl (vidioc) related functions 4. driver probing, removal, suspend and resume This patch

[PATCH v5 05/13] media: platform: pxa_camera: trivial move of functions

Move the functions in the file to be regrouped into meaningful blocks : 1. pxa camera core handling functions, manipulating the herdware 2. videobuf2 functions, dealing with video buffers 3. video ioctl (vidioc) related functions 4. driver probing, removal, suspend and resume This patch

Re: [PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

Hi Maxime, On Sat, 27 Aug 2016 14:02:51 +0200 Maxime Ripard wrote: > Please send your patches using send-email. If you are referring to "git send-email", I did send the patch series using that (with almost the same setup I use for many other projects). It

[PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

This patch adds support for some mixer controls: * Line-In * FM-In * Mic 2 * Capture Source * Differential Line-In v9 changes compared to v8 are: - added Line Differential Capture Switch. - split Capture Source into Left Capture Select, Right Capture Select. - added Line Capture Volume. -

Re: [PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

Hi Maxime, On Sat, 27 Aug 2016 14:02:51 +0200 Maxime Ripard wrote: > Please send your patches using send-email. If you are referring to "git send-email", I did send the patch series using that (with almost the same setup I use for many other projects). It probably barfed because my

[PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

This patch adds support for some mixer controls: * Line-In * FM-In * Mic 2 * Capture Source * Differential Line-In v9 changes compared to v8 are: - added Line Differential Capture Switch. - split Capture Source into Left Capture Select, Right Capture Select. - added Line Capture Volume. -

[PATCH v5 09/13] media: platform: pxa_camera: remove set_crop

This is to be seen as a regression as the set_crop function is removed. This is a temporary situation in the v4l2 porting, and will have to be added later. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 76 -- 1

[PATCH v9 2/2] Add mixer controls: Line-In, FM-In, Mic 2, Capture Source, Differential Line-In.

Note: Mic1 Capture Volume is in a different register on A20 than on A10. Note: Mic2 Capture Volume is in a different register on A20 than on A10. --- sound/soc/sunxi/sun4i-codec.c | 256 ++ 1 file changed, 236 insertions(+), 20 deletions(-) diff --git

[PATCH v5 09/13] media: platform: pxa_camera: remove set_crop

This is to be seen as a regression as the set_crop function is removed. This is a temporary situation in the v4l2 porting, and will have to be added later. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 76 -- 1 file changed, 76

[PATCH v9 2/2] Add mixer controls: Line-In, FM-In, Mic 2, Capture Source, Differential Line-In.

Note: Mic1 Capture Volume is in a different register on A20 than on A10. Note: Mic2 Capture Volume is in a different register on A20 than on A10. --- sound/soc/sunxi/sun4i-codec.c | 256 ++ 1 file changed, 236 insertions(+), 20 deletions(-) diff --git

[PATCH v9 1/2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

This distinguishes sun4i from sun7i. It is necessary because they use different registers for the audio mixer. --- sound/soc/sunxi/sun4i-codec.c | 44 +-- 1 file changed, 34 insertions(+), 10 deletions(-) diff --git a/sound/soc/sunxi/sun4i-codec.c

[PATCH v5 10/13] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH v9 1/2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

This distinguishes sun4i from sun7i. It is necessary because they use different registers for the audio mixer. --- sound/soc/sunxi/sun4i-codec.c | 44 +-- 1 file changed, 34 insertions(+), 10 deletions(-) diff --git a/sound/soc/sunxi/sun4i-codec.c

[PATCH v5 10/13] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

Re: checkkpatch (in)sanity ?

Joe Perches writes: > On Mon, 2016-08-29 at 14:15 +0300, Kalle Valo wrote: >> I wish that checkpatch would have a way to enable/disable warnings per >> directory (or file). For example, there would be >> drivers/net/wireless/ath/ath10k/.checkpatch which would disable the >>

Re: checkkpatch (in)sanity ?

Joe Perches writes: > On Mon, 2016-08-29 at 14:15 +0300, Kalle Valo wrote: >> I wish that checkpatch would have a way to enable/disable warnings per >> directory (or file). For example, there would be >> drivers/net/wireless/ath/ath10k/.checkpatch which would disable the >> warnings are not

Re: [Ksummit-discuss] checkkpatch (in)sanity ?

On Mon, 2016-08-29 at 17:46 +, Luck, Tony wrote: > > > > 80 columns is simply silly when dealing with either > > long identifiers or many levels of indentation. > > > > One thing that 80 column limit does do is encourage > > shorter identifiers and fewer levels of indentation. > > > >

Re: [Ksummit-discuss] checkkpatch (in)sanity ?

On Mon, 2016-08-29 at 17:46 +, Luck, Tony wrote: > > > > 80 columns is simply silly when dealing with either > > long identifiers or many levels of indentation. > > > > One thing that 80 column limit does do is encourage > > shorter identifiers and fewer levels of indentation. > > > >

[PATCH v2] cpu: Fix node state for whether it contains CPU

In current kernel code, we only call node_set_state(cpu_to_node(cpu), N_CPU) when a cpu is hot plugged. But we do not set the node state for N_CPU when the cpus are brought online during boot. So this could lead to failure when we check to see if a node contains cpu with node_state(node_id,

Re: [PATCH v2] mm/usercopy: get rid of CONFIG_DEBUG_STRICT_USER_COPY_CHECKS

On Mon, Aug 29, 2016 at 12:08:13PM -0500, Josh Poimboeuf wrote: > On Mon, Aug 29, 2016 at 08:36:46AM -0700, Linus Torvalds wrote: > > On Mon, Aug 29, 2016 at 7:48 AM, Josh Poimboeuf wrote: > > > > > > So I *think* your patch fixes the wrong problem. That's probably at > > >

[PATCH v2] cpu: Fix node state for whether it contains CPU

In current kernel code, we only call node_set_state(cpu_to_node(cpu), N_CPU) when a cpu is hot plugged. But we do not set the node state for N_CPU when the cpus are brought online during boot. So this could lead to failure when we check to see if a node contains cpu with node_state(node_id,

Re: [PATCH v2] mm/usercopy: get rid of CONFIG_DEBUG_STRICT_USER_COPY_CHECKS

On Mon, Aug 29, 2016 at 12:08:13PM -0500, Josh Poimboeuf wrote: > On Mon, Aug 29, 2016 at 08:36:46AM -0700, Linus Torvalds wrote: > > On Mon, Aug 29, 2016 at 7:48 AM, Josh Poimboeuf wrote: > > > > > > So I *think* your patch fixes the wrong problem. That's probably at > > > least somewhat my

[PATCH v5 03/13] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |

[PATCH v5 03/13] media: mt9m111: move mt9m111 out of soc_camera

As the mt9m111 is now working as a standalone v4l2 subdevice sensor, move it out of soc_camera directory and severe its dependency on soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/Kconfig |7 + drivers/media/i2c/Makefile |1 +

[PATCH v5 13/13] media: platform: pxa_camera: move pxa_camera out of soc_camera

As the conversion to a v4l2 standalone device is finished, move pxa_camera one directory up and finish severing any dependency to soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/platform/Kconfig |8 + drivers/media/platform/Makefile

[PATCH v5 00/13] pxa_camera transition to v4l2 standalone device

There is no change between v4 and v5, ie. the global diff is empty, only one line was shifted to prevent breaking bisectablility. All the text in https://lkml.org/lkml/2016/8/15/609 is still applicable. Cheers. -- Robert Robert Jarzmik (13): media: mt9m111: make a standalone v4l2 subdevice

[PATCH v5 08/13] media: platform: pxa_camera: add buffer sequencing

Add sequence numbers to completed buffers. Signed-off-by: Robert Jarzmik --- Since v3: reset buffer sequence number in start_streaming() --- drivers/media/platform/soc_camera/pxa_camera.c | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v5 13/13] media: platform: pxa_camera: move pxa_camera out of soc_camera

As the conversion to a v4l2 standalone device is finished, move pxa_camera one directory up and finish severing any dependency to soc_camera. Signed-off-by: Robert Jarzmik --- drivers/media/platform/Kconfig |8 + drivers/media/platform/Makefile|1 +

[PATCH v5 00/13] pxa_camera transition to v4l2 standalone device

There is no change between v4 and v5, ie. the global diff is empty, only one line was shifted to prevent breaking bisectablility. All the text in https://lkml.org/lkml/2016/8/15/609 is still applicable. Cheers. -- Robert Robert Jarzmik (13): media: mt9m111: make a standalone v4l2 subdevice

[PATCH v5 08/13] media: platform: pxa_camera: add buffer sequencing

Add sequence numbers to completed buffers. Signed-off-by: Robert Jarzmik --- Since v3: reset buffer sequence number in start_streaming() --- drivers/media/platform/soc_camera/pxa_camera.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/media/platform/soc_camera/pxa_camera.c

[PATCH v5 04/13] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

[PATCH v5 07/13] media: platform: pxa_camera: make printk consistent

Make all print consistent by always using : - dev_xxx(pcdev_to_dev(pcdev), ) This prepares the soc_camera adherence removal by making these call rely on only pcdev, and not the soc_camera icd structure. Signed-off-by: Robert Jarzmik ---

[PATCH v5 04/13] media: platform: pxa_camera: convert to vb2

Convert pxa_camera from videobuf to videobuf2. As the soc_camera was already compatible with videobuf2, the port is quite straightforward. The special case of this code in which the vb2 to prepare is "too big" in terms of size for the new capture format, the pxa_camera will fail. Signed-off-by:

[PATCH v5 07/13] media: platform: pxa_camera: make printk consistent

Make all print consistent by always using : - dev_xxx(pcdev_to_dev(pcdev), ) This prepares the soc_camera adherence removal by making these call rely on only pcdev, and not the soc_camera icd structure. Signed-off-by: Robert Jarzmik --- drivers/media/platform/soc_camera/pxa_camera.c | 70

[PATCH v5 01/13] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

[PATCH v5 01/13] media: mt9m111: make a standalone v4l2 subdevice

Remove the soc_camera adherence. Mostly the change removes the power manipulation provided by soc_camera, and instead : - powers on the sensor when the s_power control is activated - powers on the sensor in initial probe - enables and disables the MCLK provided to it in power on/off

[PATCH v5 02/13] media: mt9m111: use only the SRGB colorspace

mt9m111 being a camera sensor, its colorspace should always be SRGB, for both RGB based formats or YCbCr based ones. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/soc_camera/mt9m111.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v5 02/13] media: mt9m111: use only the SRGB colorspace

mt9m111 being a camera sensor, its colorspace should always be SRGB, for both RGB based formats or YCbCr based ones. Signed-off-by: Robert Jarzmik --- drivers/media/i2c/soc_camera/mt9m111.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Am Montag, 29. August 2016, 10:35:44 schrieb Doug Anderson: > Hi, > > On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: > > Hi Xing, Elaine, > > > > Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: > >> From: Elaine Zhang > >> > >> The

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Am Montag, 29. August 2016, 10:35:44 schrieb Doug Anderson: > Hi, > > On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: > > Hi Xing, Elaine, > > > > Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: > >> From: Elaine Zhang > >> > >> The goal is that we can configure the most

Re: OOM detection regressions since 4.7

On Mon, 2016-08-29 at 10:28 -0700, Linus Torvalds wrote: > > On Mon, Aug 29, 2016 at 7:52 AM, Olaf Hering wrote: > > > > > > Today I noticed the nfsserver was disabled, probably since months already. > > Starting it gives a OOM, not sure if this is new with 4.7+. > > That's not

Re: OOM detection regressions since 4.7

On Mon, 2016-08-29 at 10:28 -0700, Linus Torvalds wrote: > > On Mon, Aug 29, 2016 at 7:52 AM, Olaf Hering wrote: > > > > > > Today I noticed the nfsserver was disabled, probably since months already. > > Starting it gives a OOM, not sure if this is new with 4.7+. > > That's not an oom, that's

Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt

On Mon, Aug 29, 2016 at 10:55:47PM +0800, Chao Yu wrote: > Hi Ted, Jaegeuk, > > On 2016/8/28 14:16, Chao Yu wrote: > > Hi Ted, > > > > On 2016/8/28 13:13, Theodore Ts'o wrote: > >> On Sun, Aug 28, 2016 at 09:13:28AM +0800, Chao Yu wrote: > >>> From: Chao Yu > >>> > >>> This

Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt

On Mon, Aug 29, 2016 at 10:55:47PM +0800, Chao Yu wrote: > Hi Ted, Jaegeuk, > > On 2016/8/28 14:16, Chao Yu wrote: > > Hi Ted, > > > > On 2016/8/28 13:13, Theodore Ts'o wrote: > >> On Sun, Aug 28, 2016 at 09:13:28AM +0800, Chao Yu wrote: > >>> From: Chao Yu > >>> > >>> This patch fixes to add

Re: [PATCH] x86, cpu: Fix node state for whether it contains CPU

On Mon, 2016-08-29 at 15:36 +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 04:26:49PM -0700, Tim Chen wrote: > >  > > > > Signed-off-by: Tim Chen > > --- > >  arch/x86/kernel/smpboot.c | 1 + > >  1 file changed, 1 insertion(+) > > > > diff --git

Re: [PATCH] x86, cpu: Fix node state for whether it contains CPU

On Mon, 2016-08-29 at 15:36 +0200, Peter Zijlstra wrote: > On Wed, Aug 24, 2016 at 04:26:49PM -0700, Tim Chen wrote: > >  > > > > Signed-off-by: Tim Chen > > --- > >  arch/x86/kernel/smpboot.c | 1 + > >  1 file changed, 1 insertion(+) > > > > diff --git a/arch/x86/kernel/smpboot.c

RE: [Ksummit-discuss] checkkpatch (in)sanity ?

> 80 columns is simply silly when dealing with either > long identifiers or many levels of indentation. > > One thing that 80 column limit does do is encourage > shorter identifiers and fewer levels of indentation. > > Generally, both of those are good things. I think the main complaint with the

RE: [Ksummit-discuss] checkkpatch (in)sanity ?

> 80 columns is simply silly when dealing with either > long identifiers or many levels of indentation. > > One thing that 80 column limit does do is encourage > shorter identifiers and fewer levels of indentation. > > Generally, both of those are good things. I think the main complaint with the

Re: [PATCH v12 1/4] clk: mediatek: Add MT2701 clock support

On 08/27, James Liao wrote: > On Wed, 2016-08-24 at 10:49 -0700, Stephen Boyd wrote: > > On 08/22, Erin Lo wrote: > > > + > > > +static void __init mtk_infrasys_init_early(struct device_node *node) > > > +{ > > > + int r, i; > > > + > > > + if (!infra_clk_data) { > > > + infra_clk_data =

Re: [PATCH v12 1/4] clk: mediatek: Add MT2701 clock support

On 08/27, James Liao wrote: > On Wed, 2016-08-24 at 10:49 -0700, Stephen Boyd wrote: > > On 08/22, Erin Lo wrote: > > > + > > > +static void __init mtk_infrasys_init_early(struct device_node *node) > > > +{ > > > + int r, i; > > > + > > > + if (!infra_clk_data) { > > > + infra_clk_data =

Re: [PATCH v2 3/3] ARM64: dts: meson-gxbb: Add GXBB AO Clock and Reset node

Michael Turquette writes: > Quoting Kevin Hilman (2016-08-19 15:03:06) >> Neil Armstrong writes: >> >> > Add the AO clock controller node for the AmLogic GXBB SoC. >> > >> > Signed-off-by: Neil Armstrong >> > --- >>

Re: [PATCH v2 3/3] ARM64: dts: meson-gxbb: Add GXBB AO Clock and Reset node

Michael Turquette writes: > Quoting Kevin Hilman (2016-08-19 15:03:06) >> Neil Armstrong writes: >> >> > Add the AO clock controller node for the AmLogic GXBB SoC. >> > >> > Signed-off-by: Neil Armstrong >> > --- >> >> Applying this to the amlogic tree, but will need to wait a cycle due to

Re: [Ksummit-discuss] checkkpatch (in)sanity ?

On Mon, 2016-08-29 at 10:16 -0700, Josh Triplett wrote: > On Mon, Aug 29, 2016 at 05:47:59AM -0700, Joe Perches wrote: > > > > I generally don't run it on my own patches, mostly out > > of possibly misplaced confidence in my own adherence to > > the nominal kernel style.  It sometimes leads to

Re: [Ksummit-discuss] checkkpatch (in)sanity ?

On Mon, 2016-08-29 at 10:16 -0700, Josh Triplett wrote: > On Mon, Aug 29, 2016 at 05:47:59AM -0700, Joe Perches wrote: > > > > I generally don't run it on my own patches, mostly out > > of possibly misplaced confidence in my own adherence to > > the nominal kernel style.  It sometimes leads to

Re: [PATCH 1/4 v4] spinlock: Document memory barrier rules

On Mon, 29 Aug 2016, Manfred Spraul wrote: Right now, the spinlock machinery tries to guarantee barriers even for unorthodox locking cases, which ends up as a constant stream of updates as the architectures try to support new unorthodox ideas. The patch proposes to clarify the rules: spin_lock

Re: [PATCH 1/4 v4] spinlock: Document memory barrier rules

On Mon, 29 Aug 2016, Manfred Spraul wrote: Right now, the spinlock machinery tries to guarantee barriers even for unorthodox locking cases, which ends up as a constant stream of updates as the architectures try to support new unorthodox ideas. The patch proposes to clarify the rules: spin_lock

Re: [BISECTED REGRESSION] v4.8-rc: DT/OCTEON driver probing broken

On Tue, Aug 16, 2016 at 10:00 AM, Aaro Koskinen wrote: > Hi, > > Commit 44a7185c2ae6 ("of/platform: Add common method to populate default > bus") added new arch_initcall of_platform_default_populate_init() that > will be called before device_initcall

Re: [BISECTED REGRESSION] v4.8-rc: DT/OCTEON driver probing broken

On Tue, Aug 16, 2016 at 10:00 AM, Aaro Koskinen wrote: > Hi, > > Commit 44a7185c2ae6 ("of/platform: Add common method to populate default > bus") added new arch_initcall of_platform_default_populate_init() that > will be called before device_initcall octeon_publish_devices(). Now the >

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Hi, On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: > Hi Xing, Elaine, > > Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: >> From: Elaine Zhang >> >> The goal is that we can configure the most suitable pll params >> automatically. >>

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Hi, On Sun, Aug 28, 2016 at 8:21 AM, Heiko Stübner wrote: > Hi Xing, Elaine, > > Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: >> From: Elaine Zhang >> >> The goal is that we can configure the most suitable pll params >> automatically. >> >> If setting freq is not supported in

[PATCH 6/7 v5] k3dma: Add cyclic mode for audio

From: Andy Green Currently the k3dma driver doesn't offer the cyclic mode necessary for handling audio. This patch adds it. Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard

[PATCH 6/7 v5] k3dma: Add cyclic mode for audio

From: Andy Green Currently the k3dma driver doesn't offer the cyclic mode necessary for handling audio. This patch adds it. Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard Cc: Vinod Koul Cc: Dan Williams Cc: Mark Brown Cc: Andy Green Acked-by: Zhangfei Gao Signed-off-by:

[PATCH 2/7 v5] k3dma: Fix dma err offsets

From: Andy Green The offsets for ERR1 and ERR2 are wrong actually. That's why you can never clear an error. Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard Cc: Vinod Koul

[PATCH 4/7 v5] k3dma: Fix occasional DMA ERR issue by using proper dma api

After lots of debugging on an occasional DMA ERR issue, I realized that the desc structures which we point the dma hardware are being allocated out of regular memory. This means when we fill the desc structures, that data doesn't always get flushed out to memory by the time we start the dma

[PATCH 3/7 v5] k3dma: Fix "nobody cared" message seen on any error

From: Andy Green As it was before, as soon as the DMAC IP felt there was an error he would return IRQ_NONE since no actual transfer had completed. After spinning on that for 100K interrupts, Linux yanks the IRQ with a "nobody cared" error. This patch lets it handle the

[PATCH 1/7 v5] k3dma: Fix hisi burst clipping

From: Andy Green Max burst len is a 4-bit field, but at the moment it's clipped with a 5-bit constant... reduce it to that which can be expressed Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard

[PATCH 2/7 v5] k3dma: Fix dma err offsets

From: Andy Green The offsets for ERR1 and ERR2 are wrong actually. That's why you can never clear an error. Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard Cc: Vinod Koul Cc: Dan Williams Cc: Mark Brown Cc: Andy Green Acked-by: Zhangfei Gao Signed-off-by: Andy Green

[PATCH 4/7 v5] k3dma: Fix occasional DMA ERR issue by using proper dma api

After lots of debugging on an occasional DMA ERR issue, I realized that the desc structures which we point the dma hardware are being allocated out of regular memory. This means when we fill the desc structures, that data doesn't always get flushed out to memory by the time we start the dma

[PATCH 3/7 v5] k3dma: Fix "nobody cared" message seen on any error

From: Andy Green As it was before, as soon as the DMAC IP felt there was an error he would return IRQ_NONE since no actual transfer had completed. After spinning on that for 100K interrupts, Linux yanks the IRQ with a "nobody cared" error. This patch lets it handle the interrupt and keep the

[PATCH 1/7 v5] k3dma: Fix hisi burst clipping

From: Andy Green Max burst len is a 4-bit field, but at the moment it's clipped with a 5-bit constant... reduce it to that which can be expressed Cc: Zhangfei Gao Cc: Krzysztof Kozlowski Cc: Maxime Ripard Cc: Vinod Koul Cc: Dan Williams Cc: Mark Brown Cc: Andy Green Acked-by: Zhangfei

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