Re: [PATCH v7 05/24] clocksource: Add a new timer-ingenic driver

2018-09-23 Thread Daniel Lezcano
On 24/09/2018 07:49, Paul Cercueil wrote: > > Le 24 sept. 2018 07:35, Daniel Lezcano a > écrit : >> >> On 24/09/2018 07:24, Paul Cercueil wrote: >>> Hi Daniel, >>> >>> Le 24 sept. 2018 05:12, Daniel Lezcano >>> a écrit : On 21/08/2018 19:16, Paul Cercueil wrote: > This driver ha

Re: [PATCH v7 05/24] clocksource: Add a new timer-ingenic driver

2018-09-23 Thread Daniel Lezcano
On 24/09/2018 07:24, Paul Cercueil wrote: > Hi Daniel, > > Le 24 sept. 2018 05:12, Daniel Lezcano a écrit : >> >> On 21/08/2018 19:16, Paul Cercueil wrote: >>> This driver handles the TCU (Timer Counter Unit) present on the Ingenic >>> JZ47xx SoCs, and provides the kernel with a system timer, a

Re: [PATCH v7 05/24] clocksource: Add a new timer-ingenic driver

2018-09-23 Thread Daniel Lezcano
On 21/08/2018 19:16, Paul Cercueil wrote: > This driver handles the TCU (Timer Counter Unit) present on the Ingenic > JZ47xx SoCs, and provides the kernel with a system timer, and optionally > with a clocksource and a sched_clock. > > It also provides clocks and interrupt handling to client driver

Re: [PATCH v4 1/2] dt-bindings: hwmon: Add ina3221 documentation

2018-09-23 Thread Nicolin Chen
On Sat, Sep 22, 2018 at 11:36:22PM -0700, Guenter Roeck wrote: > >+ Optional properties: > >+ - input-label: Name of the input source > > Just noticed the "input-" here. Please just use "label". Will fix in v5. > >+ input1 { > >+ input-id = <0x1>; > > We'll h

[PATCH 2/2] gpiolib: Fix array members of same chip processed separately

2018-09-23 Thread Janusz Krzysztofik
New code introduced by commit bf9346f5d47b ("gpiolib: Identify arrays matching GPIO hardware") forcibly tries to find an array member which has its array index number equal to its hardware pin number and set up an array info for possible fast bitmap processing of all arrray pins belonging to that c

[PATCH 0/2] gpiolib: Fix issues introduced by fast bitmap processing path

2018-09-23 Thread Janusz Krzysztofik
While investigating possible reasons of GPIO fast bitmap processing related boot hang on Samsung Snow Chromebook, reported by Marek Szyprowski (thanks!), I've discovered one coding bug, addressed by PATCH 1/2 of this series, and one potential regression introduced at design level of the solution,

[PATCH 1/2] gpiolib: Fix missing updates of bitmap index

2018-09-23 Thread Janusz Krzysztofik
In new code introduced by commit b17566a6b08b ("gpiolib: Implement fast processing path in get/set array"), bitmap index is not updated with next found zero bit position as it should while skipping over pins already processed via fast bitmap path, possibly resulting in an infinite loop. Fix it. S

[PATCH 1/4] Drivers: hv: vmbus: Fix the descriptions of some function parameters

2018-09-23 Thread kys
From: Dexuan Cui No functional change. Added descriptions for some parameters. Fixed some typos. Removed some out-of-date comments. Signed-off-by: Dexuan Cui Cc: Jonathan Corbet Cc: linux-doc@vger.kernel.org Cc: K. Y. Srinivasan Cc: Haiyang Zhang Cc: Stephen Hemminger Signed-off-by: K. Y.

Re: [PATCH v7 4/4] gpiolib: Implement fast processing path in get/set array

2018-09-23 Thread Janusz Krzysztofik
On Friday, September 21, 2018 4:14:06 PM CEST Marek Szyprowski wrote: > Hi Janusz, > > > On 2018-09-21 12:51, Janusz Krzysztofik wrote: > > 2018-09-21 10:18 GMT+02:00, Marek Szyprowski : > >> On 2018-09-20 18:21, Janusz Krzysztofik wrote: > >>> On Thursday, September 20, 2018 5:48:22 PM CEST Janu