There are some different REGs about coalescing setting between HNS V2 and
HNS V1. The current HNS driver is only considering the situation for HNS
V1. It needs to support both of them. And Ethtool needs to know if it is
successful to set the parameters as well.
The patchset as below:
>from
From: Lisheng
It may fail to set coalesce usecs to HW, and Ethtool needs to know if it
is successful to cfg the parameter or not. So it needs return the errno by
dsaf.ko.
Signed-off-by: Lisheng
Signed-off-by: Yisen Zhuang
There are some different REGs about coalescing setting between HNS V2 and
HNS V1. The current HNS driver is only considering the situation for HNS
V1. It needs to support both of them. And Ethtool needs to know if it is
successful to set the parameters as well.
The patchset as below:
>from
From: Lisheng
It may fail to set coalesce usecs to HW, and Ethtool needs to know if it
is successful to cfg the parameter or not. So it needs return the errno by
dsaf.ko.
Signed-off-by: Lisheng
Signed-off-by: Yisen Zhuang
---
drivers/net/ethernet/hisilicon/hns/hnae.h | 2 +-
Signed-off-by: Wang Nan
---
man2/perf_event_open.2 | 57 --
1 file changed, 55 insertions(+), 2 deletions(-)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index b232cba..942a410 100644
---
Signed-off-by: Wang Nan
---
man2/perf_event_open.2 | 57 --
1 file changed, 55 insertions(+), 2 deletions(-)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index b232cba..942a410 100644
--- a/man2/perf_event_open.2
+++
Signed-off-by: Wang Nan
---
man2/perf_event_open.2 | 11 +++
1 file changed, 11 insertions(+)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index c90fc51..b232cba 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -2719,6 +2719,17 @@
Signed-off-by: Wang Nan
---
man2/perf_event_open.2 | 11 +++
1 file changed, 11 insertions(+)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index c90fc51..b232cba 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -2719,6 +2719,17 @@ The argument is a BPF
Am Donnerstag, 10. März 2016, 05:22:53 schrieb Elaine Zhang:
> Not all new socs need to handle idle states on domain state changes,
> so add the possibility to make them optional.
>
> Signed-off-by: Elaine Zhang
applied to my armsoc/drivers branch for 4.7
Thanks
> > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> > enable/disable the bus at each i2c transfer and must wait for
> > the enable/disable to happen before sending the data.
> >
> > When reading data in the trigger handler, the bmc150 accel driver does
should refer to bmg160
> > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> > enable/disable the bus at each i2c transfer and must wait for
> > the enable/disable to happen before sending the data.
> >
> > When reading data in the trigger handler, the bmc150 accel driver does
should refer to bmg160
Am Donnerstag, 10. März 2016, 05:22:53 schrieb Elaine Zhang:
> Not all new socs need to handle idle states on domain state changes,
> so add the possibility to make them optional.
>
> Signed-off-by: Elaine Zhang
applied to my armsoc/drivers branch for 4.7
Thanks
Heiko
Am Donnerstag, 10. März 2016, 05:22:54 schrieb Elaine Zhang:
> On some Rockchip SoC there exist child-domains only handling their
> idle state with the actual power-state handled by a parent-domain.
>
> So allow such types of domains. For them, we can determine their
> state (on/of) by checking
Am Donnerstag, 10. März 2016, 05:22:54 schrieb Elaine Zhang:
> On some Rockchip SoC there exist child-domains only handling their
> idle state with the actual power-state handled by a parent-domain.
>
> So allow such types of domains. For them, we can determine their
> state (on/of) by checking
For the input parameter count, it's better to use the size
of destination buffer size, as nla_memcpy would take into
account the length of the source netlink attribute when
a data is copied from an attribute.
Signed-off-by: Haishuang Yan
---
For the input parameter count, it's better to use the size
of destination buffer size, as nla_memcpy would take into
account the length of the source netlink attribute when
a data is copied from an attribute.
Signed-off-by: Haishuang Yan
---
net/openvswitch/conntrack.c | 3 ++-
1 file changed,
On 24/03/16 09:00, Irina Tirdea wrote:
> bmc150_i2c_regmap_conf is defined in bmc150-accel-core.c, but
> never used here. The definition is needed in bmc150-accel-i2c.c,
> where it is again defined.
>
> Remove the unnecessary definition of bmc150_i2c_regmap_conf from
> bmc150-accel-core.c and
On 24/03/16 09:00, Irina Tirdea wrote:
> bmc150_i2c_regmap_conf is defined in bmc150-accel-core.c, but
> never used here. The definition is needed in bmc150-accel-i2c.c,
> where it is again defined.
>
> Remove the unnecessary definition of bmc150_i2c_regmap_conf from
> bmc150-accel-core.c and
+Rhyland Klein who original wrote this code...
On Mon, Mar 28, 2016 at 10:32 AM, YH Huang wrote:
>
> On Fri, 2016-03-25 at 11:06 +0800, Daniel Kurtz wrote:
> > On Thu, Mar 24, 2016 at 2:43 PM, YH Huang wrote:
> > >
> > > Hi Daniel,
> > >
> > > On
+Rhyland Klein who original wrote this code...
On Mon, Mar 28, 2016 at 10:32 AM, YH Huang wrote:
>
> On Fri, 2016-03-25 at 11:06 +0800, Daniel Kurtz wrote:
> > On Thu, Mar 24, 2016 at 2:43 PM, YH Huang wrote:
> > >
> > > Hi Daniel,
> > >
> > > On Thu, 2016-03-24 at 12:01 +0800, Daniel Kurtz
On 24/03/16 09:05, Irina Tirdea wrote:
> Commit 845c877009cf014b ("i2c / ACPI: Assign IRQ for devices that have
> GpioInt automatically") automatically assigns the first ACPI GPIO
> interrupt in client->irq, so we can remove the probing code from
> drivers that use only one interrupt.
>
> Commit
On 24/03/16 09:05, Irina Tirdea wrote:
> Commit 845c877009cf014b ("i2c / ACPI: Assign IRQ for devices that have
> GpioInt automatically") automatically assigns the first ACPI GPIO
> interrupt in client->irq, so we can remove the probing code from
> drivers that use only one interrupt.
>
> Commit
On 24/03/16 09:08, Irina Tirdea wrote:
> GPIO handling code has been removed from the drivers (since
> this is now handled by the ACPI core) in commit 0f0796509c07 ("iio:
> remove gpio interrupt probing from drivers that use a single interrupt").
>
> Remove the include for linux/gpio/consumer.h
On 24/03/16 09:08, Irina Tirdea wrote:
> GPIO handling code has been removed from the drivers (since
> this is now handled by the ACPI core) in commit 0f0796509c07 ("iio:
> remove gpio interrupt probing from drivers that use a single interrupt").
>
> Remove the include for linux/gpio/consumer.h
On 24/03/16 09:23, Lars-Peter Clausen wrote:
> On 03/24/2016 10:09 AM, Irina Tirdea wrote:
>> config structure is set to 0 when updating the buffers, so by
>> default config->watermark will be 0. When computing the minimum
>> between config->watermark and the buffer->watermark or
>>
On 24/03/16 09:23, Lars-Peter Clausen wrote:
> On 03/24/2016 10:09 AM, Irina Tirdea wrote:
>> config structure is set to 0 when updating the buffers, so by
>> default config->watermark will be 0. When computing the minimum
>> between config->watermark and the buffer->watermark or
>>
Hi,
> Sent: Monday, March 28, 2016 5:30 PM
>
> Hi,
>
> Yoshihiro Shimoda writes:
> >> > ps: there might be bugs there, but it's a holiday and I really shouldn't
> >> > be spending time on this right now ;-)
> >>
> >> I'm also off on holiday now until Sunday
Hi,
> Sent: Monday, March 28, 2016 5:30 PM
>
> Hi,
>
> Yoshihiro Shimoda writes:
> >> > ps: there might be bugs there, but it's a holiday and I really shouldn't
> >> > be spending time on this right now ;-)
> >>
> >> I'm also off on holiday now until Sunday 10th April... yay :-)
> >> >
> >> >
On 24/03/16 09:29, Irina Tirdea wrote:
> From: Adriana Reus
>
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data
On 24/03/16 09:29, Irina Tirdea wrote:
> From: Adriana Reus
>
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data in the trigger handler,
On 24/03/16 09:29, Irina Tirdea wrote:
> From: Adriana Reus
>
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by:
On 24/03/16 09:29, Irina Tirdea wrote:
> From: Adriana Reus
>
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by: Adriana Reus
>
On 24/03/16 09:29, Irina Tirdea wrote:
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data in the trigger handler, the bmc150 accel driver
On 24/03/16 09:29, Irina Tirdea wrote:
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data in the trigger handler, the bmc150 accel driver
From: Borislav Petkov
This should contain important aspects of how we represent the system
topology on x86. If people have questions about it and this file doesn't
answer it, then it must be updated.
Signed-off-by: Borislav Petkov
Cc: Thomas Gleixner
From: Borislav Petkov
This should contain important aspects of how we represent the system
topology on x86. If people have questions about it and this file doesn't
answer it, then it must be updated.
Signed-off-by: Borislav Petkov
Cc: Thomas Gleixner
---
Let me add a reference to the generic
On 24/03/16 09:29, Irina Tirdea wrote:
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data in the trigger handler, the bmc150 accel driver
On 24/03/16 09:29, Irina Tirdea wrote:
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by: Irina Tirdea
Applied,
On 24/03/16 09:29, Irina Tirdea wrote:
> Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> enable/disable the bus at each i2c transfer and must wait for
> the enable/disable to happen before sending the data.
>
> When reading data in the trigger handler, the bmc150 accel driver
On 24/03/16 09:29, Irina Tirdea wrote:
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by: Irina Tirdea
Applied,
Thanks,
> ---
>
Add devicetree bindings for Rockchip cru which found on
Rockchip SoCs.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v6:
- update some clock contents
Changes in v5: None
Changes in
Add devicetree bindings for Rockchip cru which found on
Rockchip SoCs.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v6:
- update some clock contents
Changes in v5: None
Changes in v3: None
Changes in v2: None
Add the clock tree definition for the new RK3399 SoC.
Signed-off-by: Xing Zheng
---
Changes in v6:
- fix the source of the pclkin_isp1_wrapper should be pclkin_cif
- remove unused the GRF reference in the clock driver
- use the frac mux type for spdif and i2s
- remove
Add the clock tree definition for the new RK3399 SoC.
Signed-off-by: Xing Zheng
---
Changes in v6:
- fix the source of the pclkin_isp1_wrapper should be pclkin_cif
- remove unused the GRF reference in the clock driver
- use the frac mux type for spdif and i2s
- remove useless defines
Add the dt-bindings header for the rk3399, that gets shared between
the clock controller and the clock references in the dts.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v6: None
Hi,
The patch series add support more mux parameters and multiple
clock providers for the rockchip features of the clock framework,
and support the clock controller for the RK3399.
Changes in v6:
- update some clock contents
- fix the source of the pclkin_isp1_wrapper should be pclkin_cif
-
Add the dt-bindings header for the rk3399, that gets shared between
the clock controller and the clock references in the dts.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v6: None
Changes in v5:
- add some necessary clock IDs
- keep PPLL independent
Hi,
The patch series add support more mux parameters and multiple
clock providers for the rockchip features of the clock framework,
and support the clock controller for the RK3399.
Changes in v6:
- update some clock contents
- fix the source of the pclkin_isp1_wrapper should be pclkin_cif
-
On 24/03/16 09:29, Irina Tirdea wrote:
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by: Irina Tirdea
Applied to
On 24/03/16 09:29, Irina Tirdea wrote:
> Use available_scan_masks to allow the iio core to select
> the data to send to userspace depending on which axes are
> enabled, instead of doing this in the driver's interrupt
> handler.
>
> Signed-off-by: Irina Tirdea
Applied to the togreg branch of
> https://github.com/0day-ci/linux/commits/James-Liao/arm-dts-mt2701-Add-clock-controller-device-nodes/20160328-133113
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux for-next
> config: arm-multi_v7_defconfig (attached as .config)
> reproduce:
> wg
> https://github.com/0day-ci/linux/commits/James-Liao/arm-dts-mt2701-Add-clock-controller-device-nodes/20160328-133113
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux for-next
> config: arm-multi_v7_defconfig (attached as .config)
> reproduce:
> wg
Hi Marek, Vladimir,
On Sat, 2016-03-26 at 21:24 +0100, Marek Vasut wrote:
> On 03/26/2016 09:12 PM, Vladimir Zapolskiy wrote:
> >
> > On 26.03.2016 21:52, Marek Vasut wrote:
> > >
> > > On 03/26/2016 07:16 PM, Vladimir Zapolskiy wrote:
> > > >
> > > > On 26.03.2016 20:10, Marek Vasut wrote:
>
Hi Marek, Vladimir,
On Sat, 2016-03-26 at 21:24 +0100, Marek Vasut wrote:
> On 03/26/2016 09:12 PM, Vladimir Zapolskiy wrote:
> >
> > On 26.03.2016 21:52, Marek Vasut wrote:
> > >
> > > On 03/26/2016 07:16 PM, Vladimir Zapolskiy wrote:
> > > >
> > > > On 26.03.2016 20:10, Marek Vasut wrote:
>
On Mon, Mar 28, 2016 at 01:32:14PM +0800, Huang Rui wrote:
> This patch introduces an algorithm that computes the average power by
> reading a delta value of “core power accumulator” register during
> measurement interval, and then dividing delta value by the length of
> the time interval.
>
>
On Mon, Mar 28, 2016 at 01:32:14PM +0800, Huang Rui wrote:
> This patch introduces an algorithm that computes the average power by
> reading a delta value of “core power accumulator” register during
> measurement interval, and then dividing delta value by the length of
> the time interval.
>
>
On Mon, Mar 28, 2016 at 01:32:12PM +0800, Huang Rui wrote:
> This patch adds a member in fam15h_power_data which specifies the
> compute unit accumulated power. It adds do_read_registers_on_cu to do
> all the read to all MSRs and run it on one of the online cores on each
> compute unit with
On Mon, Mar 28, 2016 at 01:32:12PM +0800, Huang Rui wrote:
> This patch adds a member in fam15h_power_data which specifies the
> compute unit accumulated power. It adds do_read_registers_on_cu to do
> all the read to all MSRs and run it on one of the online cores on each
> compute unit with
Adding new DCS commands which are specified in the
DCS 1.3 spec related to CABC.
v2: Sorted the Macro`s by value (Andrzej)
Cc: Andrzej Hajda
Cc: Thierry Reding
Cc: David Airlie
Cc: Ville Syrjälä
Adding new DCS commands which are specified in the
DCS 1.3 spec related to CABC.
v2: Sorted the Macro`s by value (Andrzej)
Cc: Andrzej Hajda
Cc: Thierry Reding
Cc: David Airlie
Cc: Ville Syrjälä
Cc: Daniel Vetter
Suggested-by: Jani Nikula
Signed-off-by: Deepak M
---
Dear Ivan, dear Jeann,
There is an unwanted regression due to commit d7f96f97 (firmware:
dmi_scan: add SBMIOS entry and DMI tables).
Since Linux kernel 4.2 the utility `cbmem`, used to access information
stored in memory, from the coreboot project [1] does not work anymore
on a lot of systems
Dear Ivan, dear Jeann,
There is an unwanted regression due to commit d7f96f97 (firmware:
dmi_scan: add SBMIOS entry and DMI tables).
Since Linux kernel 4.2 the utility `cbmem`, used to access information
stored in memory, from the coreboot project [1] does not work anymore
on a lot of systems
The correct compatible name is "nvidia,gk20a".
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
This clock is required for the GPU to operate.
Signed-off-by: Alexandre Courbot
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
This clock is required for the GPU to operate.
Signed-off-by: Alexandre Courbot
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index
The correct compatible name is "nvidia,gk20a".
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
GK20A can optionally make use of an IOMMU.
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4
1 file changed, 4 insertions(+)
diff --git
Nouveau can take advantage of this declaration to remove the need for
contiguous memory.
Signed-off-by: Alexandre Courbot
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
GK20A can optionally make use of an IOMMU.
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
Nouveau can take advantage of this declaration to remove the need for
contiguous memory.
Signed-off-by: Alexandre Courbot
---
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
GM20B's definition is mostly similar to GK20A's, but requires an
additional clock.
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
.../devicetree/bindings/gpu/nvidia,gk20a.txt | 29 +++---
1 file changed, 26 insertions(+),
Small series that fixes/completes DT bindings for Tegra GPUs and add two
missing entries required for the Tegra210 GPU to operate properly.
Without these fixes, GM20B will crash during probe on 4.6 because a
required clock is not activated.
Changes since v2:
- Fixed device address in DT examples
GM20B's definition is mostly similar to GK20A's, but requires an
additional clock.
Signed-off-by: Alexandre Courbot
Acked-by: Rob Herring
---
.../devicetree/bindings/gpu/nvidia,gk20a.txt | 29 +++---
1 file changed, 26 insertions(+), 3 deletions(-)
diff --git
Small series that fixes/completes DT bindings for Tegra GPUs and add two
missing entries required for the Tegra210 GPU to operate properly.
Without these fixes, GM20B will crash during probe on 4.6 because a
required clock is not activated.
Changes since v2:
- Fixed device address in DT examples
On 03/28/2016 10:35 AM, Jonathan Cameron wrote:
> On 27/03/16 08:42, zhaoxiu.zeng wrote:
>> From: Zeng Zhaoxiu
>>
>> Signed-off-by: Zeng Zhaoxiu
> Interesting. Whilst obviously correct I wonder if this obscures the
> intent of the code a little.
On 03/28/2016 10:35 AM, Jonathan Cameron wrote:
> On 27/03/16 08:42, zhaoxiu.zeng wrote:
>> From: Zeng Zhaoxiu
>>
>> Signed-off-by: Zeng Zhaoxiu
> Interesting. Whilst obviously correct I wonder if this obscures the
> intent of the code a little. Lars, what do you think?
The parity function is
Hi Marek,
Firstly, thank you very much for your comments.
On 2016/3/27 9:47, Marek Vasut wrote:
> On 03/26/2016 09:11 AM, Jiancheng Xue wrote:
>> Add hisilicon spi-nor flash controller driver
>>
>> Signed-off-by: Binquan Peng
>> Signed-off-by: Jiancheng Xue
Hi Marek,
Firstly, thank you very much for your comments.
On 2016/3/27 9:47, Marek Vasut wrote:
> On 03/26/2016 09:11 AM, Jiancheng Xue wrote:
>> Add hisilicon spi-nor flash controller driver
>>
>> Signed-off-by: Binquan Peng
>> Signed-off-by: Jiancheng Xue
>> Acked-by: Rob Herring
>>
On 28 March 2016 at 15:13, Peter Chen wrote:
> On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang wrote:
>> On 25 March 2016 at 15:09, Peter Chen wrote:
>> > On Thu, Mar 24, 2016 at 08:35:53PM +0800, Baolin Wang wrote:
>> >> Currently the Linux
On 28 March 2016 at 15:13, Peter Chen wrote:
> On Mon, Mar 28, 2016 at 02:51:40PM +0800, Baolin Wang wrote:
>> On 25 March 2016 at 15:09, Peter Chen wrote:
>> > On Thu, Mar 24, 2016 at 08:35:53PM +0800, Baolin Wang wrote:
>> >> Currently the Linux kernel does not provide any standard integration
On 22-03-16, 02:54, Rafael J. Wysocki wrote:
> Index: linux-pm/kernel/sched/cpufreq_schedutil.c
> ===
> --- /dev/null
> +++ linux-pm/kernel/sched/cpufreq_schedutil.c
> @@ -0,0 +1,528 @@
> +/*
> + * CPUFreq governor based on
On 22-03-16, 02:54, Rafael J. Wysocki wrote:
> Index: linux-pm/kernel/sched/cpufreq_schedutil.c
> ===
> --- /dev/null
> +++ linux-pm/kernel/sched/cpufreq_schedutil.c
> @@ -0,0 +1,528 @@
> +/*
> + * CPUFreq governor based on
On 25/03/16 22:40, Richard Weinberger wrote:
> Not all archs have io memory.
> Instead of selecting I2C_MUX (and bypassing the HAS_IOMEM dependency)
> depend directly on it.
>
> Fixes the following kconfig warning:
> warning: (MEDIA_SUBDRV_AUTOSELECT && VIDEO_CX231XX && INV_MPU6050_I2C)
>
On 25/03/16 22:40, Richard Weinberger wrote:
> Not all archs have io memory.
> Instead of selecting I2C_MUX (and bypassing the HAS_IOMEM dependency)
> depend directly on it.
>
> Fixes the following kconfig warning:
> warning: (MEDIA_SUBDRV_AUTOSELECT && VIDEO_CX231XX && INV_MPU6050_I2C)
>
On Mon, Mar 28, 2016 at 01:32:11PM +0800, Huang Rui wrote:
> This patch adds CONFIG_CPU_SUP_AMD as the dependence of fam15h_power
> driver. Because the following patch will use the interface from
> x86/kernel/cpu/amd.c.
>
> Otherwise, the below error might be encountered:
>
> All errors (new
On Mon, Mar 28, 2016 at 01:32:11PM +0800, Huang Rui wrote:
> This patch adds CONFIG_CPU_SUP_AMD as the dependence of fam15h_power
> driver. Because the following patch will use the interface from
> x86/kernel/cpu/amd.c.
>
> Otherwise, the below error might be encountered:
>
> All errors (new
Hi Jonsoo,
On Mon, Mar 28, 2016 at 7:26 AM, wrote:
> From: Joonsoo Kim
>
> Initial attemp to remove BAD_ALIEN_MAGIC is once reverted by
> 'commit edcad2509550 ("Revert "slab: remove BAD_ALIEN_MAGIC"")'
> because it causes a problem on m68k which has
Hi Jonsoo,
On Mon, Mar 28, 2016 at 7:26 AM, wrote:
> From: Joonsoo Kim
>
> Initial attemp to remove BAD_ALIEN_MAGIC is once reverted by
> 'commit edcad2509550 ("Revert "slab: remove BAD_ALIEN_MAGIC"")'
> because it causes a problem on m68k which has many node
> but !CONFIG_NUMA. In this case,
On 05/03/16 18:49, Jonathan Cameron wrote:
> On 04/03/16 01:05, Krzysztof Kozlowski wrote:
>> The devres.o gets linked if HAS_IOMEM is present so on ARCH=um
>> allyesconfig (COMPILE_TEST) failed with:
>>
>> drivers/built-in.o: In function `at91_adc_probe':
>> at91-sama5d2_adc.c:(.text+0x48f548):
On 05/03/16 18:49, Jonathan Cameron wrote:
> On 04/03/16 01:05, Krzysztof Kozlowski wrote:
>> The devres.o gets linked if HAS_IOMEM is present so on ARCH=um
>> allyesconfig (COMPILE_TEST) failed with:
>>
>> drivers/built-in.o: In function `at91_adc_probe':
>> at91-sama5d2_adc.c:(.text+0x48f548):
On 25/03/16 22:40, Richard Weinberger wrote:
> Not all archs have io memory.
>
> Fixes the following build error:
> ERROR: "devm_ioremap_resource" [drivers/iio/adc/at91-sama5d2_adc.ko]
> undefined!
>
> Cc: Jonathan Cameron
> Cc: Hartmut Knaack
> Cc:
On 25/03/16 22:40, Richard Weinberger wrote:
> Not all archs have io memory.
>
> Fixes the following build error:
> ERROR: "devm_ioremap_resource" [drivers/iio/adc/at91-sama5d2_adc.ko]
> undefined!
>
> Cc: Jonathan Cameron
> Cc: Hartmut Knaack
> Cc: Lars-Peter Clausen
> Cc: Peter Meerwald
>
Commit be3d7d023b87 ("ARM: kirkwood: Add DTS file for NSA320")
created the new file kirkwood-nsa320.dts but did not
add it to the Makefile.
Fixes: be3d7d023b87 ("ARM: kirkwood: Add DTS file for NSA320")
Signed-off-by: Heinrich Schuchardt
---
arch/arm/boot/dts/Makefile | 1 +
Commit be3d7d023b87 ("ARM: kirkwood: Add DTS file for NSA320")
created the new file kirkwood-nsa320.dts but did not
add it to the Makefile.
Fixes: be3d7d023b87 ("ARM: kirkwood: Add DTS file for NSA320")
Signed-off-by: Heinrich Schuchardt
---
arch/arm/boot/dts/Makefile | 1 +
1 file changed, 1
On 26/03/16 19:58, Joe Perches wrote:
> On Sat, 2016-03-26 at 12:50 -0700, Alison Schofield wrote:
>> Use kernel preferred unsigned int declaration style.
>>
>> Patch created using:
>> git ls-files drivers/staging/iio | \
>> xargs ./scripts/checkpatch.pl -f --fix-inplace --types=unspecified_int
>>
On 26/03/16 19:58, Joe Perches wrote:
> On Sat, 2016-03-26 at 12:50 -0700, Alison Schofield wrote:
>> Use kernel preferred unsigned int declaration style.
>>
>> Patch created using:
>> git ls-files drivers/staging/iio | \
>> xargs ./scripts/checkpatch.pl -f --fix-inplace --types=unspecified_int
>>
On 27/03/16 08:42, zhaoxiu.zeng wrote:
> From: Zeng Zhaoxiu
>
> Signed-off-by: Zeng Zhaoxiu
Interesting. Whilst obviously correct I wonder if this obscures the
intent of the code a little. Lars, what do you think?
Jonathan
> ---
>
On 27/03/16 08:42, zhaoxiu.zeng wrote:
> From: Zeng Zhaoxiu
>
> Signed-off-by: Zeng Zhaoxiu
Interesting. Whilst obviously correct I wonder if this obscures the
intent of the code a little. Lars, what do you think?
Jonathan
> ---
> drivers/iio/gyro/adxrs450.c | 8 ++--
> 1 file changed, 2
Hi,
Yoshihiro Shimoda writes:
>> > ps: there might be bugs there, but it's a holiday and I really shouldn't
>> > be spending time on this right now ;-)
>>
>> I'm also off on holiday now until Sunday 10th April... yay :-)
>> >
>> > Anyway, have fun testing. Let
Hi,
Yoshihiro Shimoda writes:
>> > ps: there might be bugs there, but it's a holiday and I really shouldn't
>> > be spending time on this right now ;-)
>>
>> I'm also off on holiday now until Sunday 10th April... yay :-)
>> >
>> > Anyway, have fun testing. Let me know if it doesn't work.
>>
901 - 1000 of 1106 matches
Mail list logo