Re: [linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.1

2016-07-21 Thread Bruce Ashfield
On 2016-07-21 1:24 PM, Daniel Dragomir wrote: Hello Bruce! This series of patches brings various improvements to the Intel Axxia drivers from linux-yocto-4.1, including NCR, USB, PEI, FEMAC and also some DTB updates. Please pull the patches from https://github.com/axxia/axxia_yocto_linux_4.1_pu

Re: [linux-yocto] [PATCH 00/10] pwm related fixes for standard/intel/* branches

2016-07-21 Thread Bruce Ashfield
On 2016-07-21 7:47 PM, California Sullivan wrote: The drm forklift brought in some changes to structs and enums used by PWM drivers. These drivers didn't get updated, causing them to fail compilation. This set of backports updates the drivers to use the new structs and methods and fixes compilati

Re: [linux-yocto] [PATCH] drivers/mfd/pca9685-pwm.c: Update to reflect changes in patches from upstream

2016-07-21 Thread Bruce Ashfield
On 2016-07-21 3:21 PM, Saul Wold wrote: There are some patches brought into to 4.4 from upstream that change the pwm structure and move period and duty_cycle into a state structure so fix these up. Additional address the removal of PWMF_ENABLED in favor checking the state via pwm_is_enabled().

Re: [linux-yocto] [PATCH] features/powertop: To provide wakeup/seconds events

2016-07-21 Thread Bacchewar, Nilesh
Thanks Saul for your comment. We will check if this can help us & revisit the requirement if needs. Regards, Nilesh -Original Message- From: Saul Wold [mailto:s...@linux.intel.com] Sent: Thursday, July 21, 2016 12:27 AM To: Bacchewar, Nilesh ; linux-yocto@yoctoproject.org Subject: Re:

Re: [linux-yocto] [PATCH 5/6] [UPSTREAMED] acpi: add support for configfs

2016-07-21 Thread Sullivan, California L
In an allmodconfig build I found that configfs (CONFIG_ACPI_CONFIGFS=m introduced in this patch) fails to compile on both standard/intel/base and standard/intel/bxt-rebase branches. Sebastien, could you look into what it takes to fix this? Thanks, Cal Sullivan On 07/11/2016 03:35 PM, Sebastien Bo

[linux-yocto] [PATCH 07/10] UPSTREAM: clk: pwm: Use pwm_get_args() where appropriate

2016-07-21 Thread California Sullivan
From: Boris Brezillon The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. Thi

[linux-yocto] [PATCH 05/10] UPSTREAM: backlight: pwm_bl: Use pwm_get_args() where appropriate

2016-07-21 Thread California Sullivan
From: Boris Brezillon The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. Thi

[linux-yocto] [PATCH 10/10] UPSTREAM: hwmon: pwm-fan: Use pwm_get_args() where appropriate

2016-07-21 Thread California Sullivan
From: Boris Brezillon The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. Thi

[linux-yocto] [PATCH 09/10] UPSTREAM: pwm: Use pwm_get/set_xxx() helpers where appropriate

2016-07-21 Thread California Sullivan
From: Boris Brezillon Use pwm_get/set_xxx() helpers instead of directly accessing the pwm->xxx field. Doing that will ease adaptation of the PWM framework to support atomic update. Signed-off-by: Boris Brezillon Signed-off-by: Thierry Reding CONFLICTS: This patch originally fixed up omap-dmt

[linux-yocto] [PATCH 06/10] UPSTREAM: backlight: lm3630a_bl: Stop messing with the pwm->period field

2016-07-21 Thread California Sullivan
From: Boris BREZILLON pwm->period field is not supposed to be changed by PWM users. The only ones authorized to change it are the PWM core and PWM drivers. Signed-off-by: Boris Brezillon Acked-by: Lee Jones Signed-off-by: Thierry Reding (cherry picked from 4ff66efd59102280a71d432c9f0e89cdaf66

[linux-yocto] [PATCH 02/10] UPSTREAM: backlight: pwm_bl: Fix broken PWM backlight for non-dt platforms

2016-07-21 Thread California Sullivan
From: Philipp Zabel Commit ee65ad0e2a9e ("backlight: pwm_bl: Avoid backlight flicker when probed from DT") tries to dereference the device of_node pointer unconditionally, causing a NULL pointer dereference on non-dt platforms. Fix it by replacing the phandle variable with a node variable and by

[linux-yocto] [PATCH 04/10] UPSTREAM: backlight: pwm_bl: Remove useless call to pwm_set_period()

2016-07-21 Thread California Sullivan
From: Boris BREZILLON The PWM period will be set when calling pwm_config. Remove this useless call to pwm_set_period(), which might mess up the internal PWM state. Signed-off-by: Boris Brezillon Acked-by: Lee Jones Signed-off-by: Thierry Reding (cherry picked from commit 7f044b09b68d36811518c

[linux-yocto] [PATCH 08/10] UPSTREAM: pwm: rcar: Make use of pwm_is_enabled()

2016-07-21 Thread California Sullivan
From: Boris BREZILLON Commit 5c31252c4a86 ("pwm: Add the pwm_is_enabled() helper") introduced a new function to test whether a PWM device is enabled or not without manipulating PWM internal fields. Hiding this is necessary if we want to smoothly move to the atomic PWM config approach without imp

[linux-yocto] [PATCH 03/10] UPSTREAM: backlight: pwm_bl: Free PWM requested by legacy API on error path

2016-07-21 Thread California Sullivan
From: Vladimir Zapolskiy If pwm is requested by legacy pwm_request() and if the following backlight_device_register() call fails, add pwm_free() clean-up. Signed-off-by: Vladimir Zapolskiy Signed-off-by: Lee Jones (cherry picked from commit 60d613d6aef4ae49988eeb3ad38af948c561db1e) Signed-off-

[linux-yocto] [PATCH 00/10] pwm related fixes for standard/intel/* branches

2016-07-21 Thread California Sullivan
The drm forklift brought in some changes to structs and enums used by PWM drivers. These drivers didn't get updated, causing them to fail compilation. This set of backports updates the drivers to use the new structs and methods and fixes compilation. This set of patches is also available at ssh://

[linux-yocto] [PATCH 01/10] UPSTREAM: backlight: pwm_bl: Avoid backlight flicker when probed from DT

2016-07-21 Thread California Sullivan
From: Philipp Zabel If the driver is probed from the device tree, and there is a phandle property set on it, and the enable GPIO is already configured as output, and the backlight is currently disabled, keep it disabled. If all these conditions are met, assume there will be some other driver that

[linux-yocto] [PATCH] drivers/mfd/pca9685-pwm.c: Update to reflect changes in patches from upstream

2016-07-21 Thread Saul Wold
There are some patches brought into to 4.4 from upstream that change the pwm structure and move period and duty_cycle into a state structure so fix these up. Additional address the removal of PWMF_ENABLED in favor checking the state via pwm_is_enabled(). Signed-off-by: Saul Wold --- drivers/mfd/

Re: [linux-yocto] dwc3 pm enabling backport for standard/intel/base

2016-07-21 Thread Ernst, Eric
On Thu, Jul 21, 2016 at 01:12:25PM -0400, Bruce Ashfield wrote: > On 2016-07-20 06:34 PM, Ernst, Eric wrote: > >Please consider pull-request listed below. We tested on Grosse Tete and > >verify > >proper PM for USB after applying the set. This was rebased onto latest of > >bxt-rebase, but I thin

[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.1

2016-07-21 Thread Daniel Dragomir
Hello Bruce! This series of patches brings various improvements to the Intel Axxia drivers from linux-yocto-4.1, including NCR, USB, PEI, FEMAC and also some DTB updates. Please pull the patches from https://github.com/axxia/axxia_yocto_linux_4.1_pull.git into git://git.yoctoproject.org/linux-yoc

Re: [linux-yocto] dwc3 pm enabling backport for standard/intel/base

2016-07-21 Thread Bruce Ashfield
On 2016-07-20 06:34 PM, Ernst, Eric wrote: Please consider pull-request listed below. We tested on Grosse Tete and verify proper PM for USB after applying the set. This was rebased onto latest of bxt-rebase, but I think we should consider also for standard/intel/base. They looked clean enoug

Re: [linux-yocto] [PATCH] features/powertop: To provide wakeup/seconds events

2016-07-21 Thread Bruce Ashfield
On 2016-07-21 03:26 AM, Saul Wold wrote: On Wed, 2016-07-20 at 16:20 -0700, Nilesh Bacchewar wrote: for powertop to provide wakeup/seconds events Signed-off-by: Nilesh Bacchewar --- features/powertop/powertop.cfg | 5 + features/soc/broxton/broxton.scc | 2 ++ 2 files changed, 7 ins

Re: [linux-yocto] [standard/base] mei: drop wr_msg from the mei_dev structure

2016-07-21 Thread Bruce Ashfield
On 2016-07-20 03:37 PM, Tomas Winkler wrote: From: Alexander Usyskin commit c0ff9019ee64101fda8f19338da799fda8217e14 upstream The control messages are usually small, around 8 bytes, and can be allocated on the stack. Using on stack allocation allows us to drop 'wr_msg' a rather large buffer re

Re: [linux-yocto] [PATCH] features/powertop: To provide wakeup/seconds events

2016-07-21 Thread Saul Wold
On Wed, 2016-07-20 at 16:20 -0700, Nilesh Bacchewar wrote: > > for powertop to provide wakeup/seconds events > > Signed-off-by: Nilesh Bacchewar > --- >  features/powertop/powertop.cfg   | 5 + >  features/soc/broxton/broxton.scc | 2 ++ >  2 files changed, 7 insertions(+) >  create mode 10064