Re: [PATCH 4.8 50/96] firmware: fix usermode helper fallback loading

Greg Kroah-Hartman writes: > On Fri, Jan 06, 2017 at 10:54:38PM +0100, Yves-Alexis Perez wrote: >> On Fri, 2017-01-06 at 22:43 +0100, Greg Kroah-Hartman wrote: >> > 4.8-stable review patch.  If anyone has any objections, please let me know. >> >> Hi Greg, >&

[REGRESSION] Kernel panic in firmware_request since v4.9

Hello everyone, After a recent upgrade to 4.10-rc2 I noticed that my wireless adapter didn't come up due to a kernel panic in the firmware class induced by iwlwifi, BUG: unable to handle kernel NULL pointer dereference at 0038 IP: _request_firmware+0x995/0xa40 PGD 0

Re: OpRegion conflicts for Skylake LPSS

Mika Westerberg writes: > On Fri, Apr 29, 2016 at 09:30:27AM +0200, Ben Gamari wrote: >> Ben Gamari writes: >> >> > [ Unknown signature status ] >> > Mika Westerberg writes: >> > >> >> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari w

Re: OpRegion conflicts for Skylake LPSS

Ben Gamari writes: > [ Unknown signature status ] > Mika Westerberg writes: > >> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote: >>> > snip > >>> It looks very much like these are describing the same device. Perhaps >>> the lps

Re: OpRegion conflicts for Skylake LPSS

Mika Westerberg writes: > On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote: >> snip >> It looks very much like these are describing the same device. Perhaps >> the lpss driver should be binding to this ACPI node? Or perhaps this is >> a firmware issue? An

Re: [PATCH v5 0/12] cpufreq: Add support for Exynos 5800, 5420, and 5422

Viresh Kumar writes: > On 03-12-15, 11:26, Ben Gamari wrote: >> Sounds reasonable to me. However, I'd just like to reiterate that this >> line of work can be pursued independently from the upstreaming of this >> series. > > I think this is the right time to u

Re: [PATCH 11/12] cpufreq: arm-big-little: clarify frequency units

"Jon Medhurst (Tixy)" writes: > On Wed, 2015-12-02 at 22:19 +0100, Ben Gamari wrote: >> The frequency units are very confusing in this area as OPPs use Hz >> whereas cpufreq uses kHz. Be explicit about this in variable naming. >> >> Cc: Javier Martinez C

Re: [PATCH v5 0/12] cpufreq: Add support for Exynos 5800, 5420, and 5422

Viresh Kumar writes: > On 03-12-15, 11:26, Ben Gamari wrote: >> Viresh Kumar writes: >> > But, before I start reviewing this series, I have few comments. >> > - We weren't able to use cpufreq-dt driver for big LITTLE platforms >> > earlier, as it neve

Re: [PATCH 02/12] clk: samsung: exynos5420: add cpu clock configuration data and instantiate cpu clock

Krzysztof Kozlowski writes: > On 03.12.2015 06:19, Ben Gamari wrote: >> From: Thomas Abraham >> >> With the addition of the new Samsung specific cpu-clock type, the >> arm clock can be represented as a cpu-clock type. Add the CPU clock >> configuration data a

Re: [PATCH v5 0/12] cpufreq: Add support for Exynos 5800, 5420, and 5422

Viresh Kumar writes: > Hi Ben, Hi Viresh, > On 02-12-15, 22:19, Ben Gamari wrote: >> >> This patch series adds cpufreq support for the Exynos 5800, 5420, and 5422 >> SOCs. In particular, it adds support for operating-points-v2 bindings to the >> arm-big-little

[PATCH 03/12] ARM: dts: Exynos5420: add CPU OPP and regulator supply property

From: Thomas Abraham For Exynos5420 platforms, add CPU operating points and CPU regulator supply properties for migrating from Exynos specific cpufreq driver to using generic cpufreq driver. Changes by Bartlomiej: - split Exynos5420 support from the original patch Changes by Ben Gamari: - Port

[PATCH 04/12] ARM: Exynos: use generic cpufreq driver for Exynos5420

From: Thomas Abraham The new CPU clock type allows the use of generic arm_big_little_dt cpufreq driver for Exynos5420. Changes by Bartlomiej: - split Exynos5420 support from the original patch - disable cpufreq if big.LITTLE switcher support is enabled Changes by Ben Gamari: - rebase Cc

[PATCH 12/12] cpufreq: arm-big-little: warn on invalid regulator

Cc: Javier Martinez Canillas Signed-off-by: Ben Gamari --- drivers/cpufreq/arm_big_little.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/cpufreq/arm_big_little.c b/drivers/cpufreq/arm_big_little.c index 2d5761c..5d30c26 100644 --- a/drivers/cpufreq/arm_big_little.c +++ b

[PATCH 01/12] cpufreq: arm_big_little: add cluster regulator support

x27;s voltage value) for CPU clusters. Cc: Kukjin Kim Cc: Doug Anderson Cc: Javier Martinez Canillas Cc: Andreas Faerber Cc: Sachin Kamat Cc: Thomas Abraham Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Ben Gamari --- .../bindings/cpufreq/arm_big_little_dt.txt | 4 + dr

[PATCH 11/12] cpufreq: arm-big-little: clarify frequency units

The frequency units are very confusing in this area as OPPs use Hz whereas cpufreq uses kHz. Be explicit about this in variable naming. Cc: Javier Martinez Canillas Signed-off-by: Ben Gamari --- drivers/cpufreq/arm_big_little.c | 20 ++-- 1 file changed, 10 insertions(+), 10

[PATCH v5 0/12] cpufreq: Add support for Exynos 5800, 5420, and 5422

This patch series adds cpufreq support for the Exynos 5800, 5420, and 5422 SOCs. In particular, it adds support for operating-points-v2 bindings to the arm-big-little cpufreq driver and updates the above-mentioned SOCs' devicetrees to take advantage of this support. There are also a couple of patc

[PATCH 10/12] cpufreq: arm-big-little: accept operating-points-v2 nodes

The arm_big_little cpufreq driver can use operating points from operating-points-v2 nodes without any trouble. Cc: Javier Martinez Canillas Signed-off-by: Ben Gamari --- drivers/cpufreq/arm_big_little_dt.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/drivers

[PATCH 02/12] clk: samsung: exynos5420: add cpu clock configuration data and instantiate cpu clock

patches - moved E5420_[EGL,KFC]_DIV0() macros to clk-exynos5420.c Changes by Ben Gamari: - Rebased Cc: Tomasz Figa Cc: Mike Turquette Cc: Javier Martinez Canillas Signed-off-by: Thomas Abraham Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Ben Gamari --- drivers/clk/samsung/clk

[PATCH 09/12] ARM: dts: Exynos5420/5800: add cluster regulator supply properties

From: Bartlomiej Zolnierkiewicz Add cluster regulator supply properties as a preparation to adding generic arm_big_little_dt cpufreq driver support for Exynos5420 and Exynos5800 based boards. Changes by Ben Gamari: - Add regulators to odroidxu4 Cc: Kukjin Kim Cc: Doug Anderson Cc: Javier

[PATCH 07/12] ARM: dts: Exynos5422: fix OPP tables

clocks. These are otherwise inherited from the exynos5800 devicetree, which has the CPU clusters reversed compared to the 5422. This results in the A15 cores only reaching 1.4GHz, the maximum rate of the KFC clock. Cc: Javier Martinez Canillas Signed-off-by: Ben Gamari --- arch/arm/boot/dts

[PATCH 05/12] clk: samsung: exynos5800: fix cpu clock configuration data

s Cc: Thomas Abraham Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Ben Gamari --- drivers/clk/samsung/clk-exynos5420.c | 36 +--- 1 file changed, 33 insertions(+), 3 deletions(-) diff --git a/drivers/clk/samsung/clk-exynos5420.c b/drivers/clk/samsun

[PATCH 08/12] ARM: Exynos: use generic cpufreq driver for Exynos5800

From: Thomas Abraham The new CPU clock type allows the use of generic arm_big_little_dt cpufreq driver for Exynos5800. Changes by Bartlomiej: - split Exynos5800 support from the original patch - disable cpufreq if big.LITTLE switcher support is enabled Changes by Ben Gamari: - rebase Cc

[PATCH 06/12] ARM: dts: Exynos5800: fix CPU OPP

-XU3 Lite board (which doesn't support these higher OPPs). Based on Hardkernel's kernel for ODROID-XU3 board. Cc: Kukjin Kim Cc: Doug Anderson Cc: Javier Martinez Canillas Cc: Andreas Faerber Cc: Sachin Kamat Cc: Thomas Abraham Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Be

intel_pstate throttling stuck at low frequency

Hello all, I have a Dell Latitude E7440 running Ubuntu 15.04 which seems to be suffering from the intel_pstate driver getting stuck in a throttled state while under load. The issue typically occurs on warm days when the while the machine is under load for an extended period of time (e.g. while co

Re: [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.

Mario Limonciello writes: > On 04/10/2015 06:14 PM, Pali Rohár wrote: snip >> Can you comment if this is also same problem with invalid packets >> on E6440/E7440 machines? >> > Hi Pali, > snip > > The invalid packets on the Exx40 machines I believe is caused by some > behavior that happens if th

Re: [PATCH v4 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs

Andreas Färber writes: > Hello, > > This series adds a dedicated ODROID-XU device tree and enhances it with > LED configuration, to match the downstream 3.14 based behavior. > Any word on merging this? Cheers, - Ben pgp362BgH0_z0.pgp Description: PGP signature

Re: [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.

Hi Mario, It's great to hear from someone with knowledge of the inner workings of Dell's firmware. Mario Limonciello writes: > Hi Pali & Dmitry, > > On 02/20/2015 01:24 PM, Pali Rohár wrote: >> On Friday 20 February 2015 19:47:17 Dmitry Torokhov wrote: snip >> Dell Latitude Exx40 models (wi

Re: [PATCH] PM / devfreq: remove checks for CONFIG_EXYNOS_ASV

MyungJoo Ham writes: > On Fri, May 23, 2014 at 1:52 PM, MyungJoo Ham > wrote: >> On Thu, May 22, 2014 at 5:37 AM, Paul Bolle wrote: >>> Checks for CONFIG_EXYNOS_ASV were added in v3.3. But the related Kconfig >>> symbol has never been added to the tree. Remove these checks, as they >>> always

Re: [RFC 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs

Andreas Färber writes: > Kukjin, > > Am 28.07.2014 14:18, schrieb Andreas Färber: >> Hello, >> >> This series adds a dedicated ODROID-XU device tree and enhances it with >> LED configuration, to match the downstream 3.14 based behavior. >> >> It had turned out less trivial than I initially tho

Re: Touchpad/Clickpad Linux Project

Felipe Lavratti writes: > Hello, > > I'd like to ask if there's any undergoing Linux project regarding the > Touchpad/Clickpad Linux sub system and where can I get in touch with > them. > Is there a particular driver you are interested in? If so you may want to see who is responsible for it in th

Re: rotary encoder linux driver

Johan Hovold writes: > On Sun, Oct 12, 2014 at 06:29:03PM -0700, tecfacet wrote: >> Hello. >> >> I am interested in the rotary encoder kernel driver. I am very new to >> this linux kernel driver thing. >> >> How do I pass the gpio and interrupt stuff to the kernel module.. I >> think it is t

Re: [RFC PATCH] gpio: add GPIO hogging mechanism

Ben Gamari writes: > Hi Boris, > > I'm just returning to this now. > > > Greg Kroah-Hartman writes: > >> I don't understand what makes GPIO's "special" enough to get included in >> the driver core like this, and called for each and ev

Re: [RFC PATCH] gpio: add GPIO hogging mechanism

Hi Boris, I'm just returning to this now. Greg Kroah-Hartman writes: > I don't understand what makes GPIO's "special" enough to get included in > the driver core like this, and called for each and every device that is > added to the system. > I'm also a bit confused why GPIOs ended up in the d