January 2017 - linaro-kernel - lists.linaro.org

[PATCH V3 00/16] PM / OPP: Introduce APIs to transition OPPs

by Viresh Kumar

Hi Guys, This patchset add APIs in OPP layer to allow OPPs transitioning from within OPP layer. Currently all OPP users need to replicate the same code to switch between OPPs. While the same can be handled easily by OPP-core. The first 7 patches update the OPP core to introduce the new APIs and the next Nine patches update cpufreq-dt for the same. 11 out of 17 are already Reviewed by Stephen, only few are left :) I hope this is the last version of the series :) Testing: - Tested on exynos 5250-arndale (dual-cortex-A15) - Tested for both Old-V1 bindings and New V2 bindings - Tested with regulator names as: 'cpu-supply' and 'cpu0-supply' - Tested with Unsupported supply ranges as well, to check the opp-disable logic V2->V3: - Very minor updates. - find_supply_name() doesn't return an error value now, and so its callers don't check for it. - And so we don't need to initialize name to NULL Viresh Kumar (16): PM / OPP: get/put regulators from OPP core PM / OPP: Disable OPPs that aren't supported by the regulator PM / OPP: Introduce dev_pm_opp_get_max_volt_latency() PM / OPP: Introduce dev_pm_opp_get_max_transition_latency() PM / OPP: Parse clock-latency and voltage-tolerance for v1 bindings PM / OPP: Manage device clk PM / OPP: Add dev_pm_opp_set_rate() cpufreq: dt: Convert few pr_debug/err() calls to dev_dbg/err() cpufreq: dt: Rename 'need_update' to 'opp_v1' cpufreq: dt: OPP layers handles clock-latency for V1 bindings as well cpufreq: dt: Pass regulator name to the OPP core cpufreq: dt: Unsupported OPPs are already disabled cpufreq: dt: Reuse dev_pm_opp_get_max_transition_latency() cpufreq: dt: Use dev_pm_opp_set_rate() to switch frequency cpufreq: dt: No need to fetch voltage-tolerance cpufreq: dt: No need to allocate resources anymore drivers/base/power/opp/core.c | 420 ++++++++++++++++++++++++++++++++++++++++++ drivers/base/power/opp/opp.h | 13 ++ drivers/cpufreq/cpufreq-dt.c | 300 +++++++++++------------------- include/linux/pm_opp.h | 27 +++ 4 files changed, 565 insertions(+), 195 deletions(-) -- 2.7.1.370.gb2aa7f8

7 years, 10 months

4
26
0 0

[PATCH 00/34] CPUFreq: Move freq change notifications out of drivers

by Viresh Kumar

Another 452 lines gone :) Total stats upto now for all the 5 patchsets: Viresh Kumar (186): ... 69 files changed, 700 insertions(+), 2451 deletions(-) Net: 1751 lines gone.. -----x-------------x---------------- Most of the drivers do following in their ->target_index() routines: struct cpufreq_freqs freqs; freqs.old = old freq... freqs.new = new freq... cpufreq_notify_transition(policy, &freqs, CPUFREQ_PRECHANGE); /* Change rate here */ cpufreq_notify_transition(policy, &freqs, CPUFREQ_POSTCHANGE); This is replicated over all cpufreq drivers today and there doesn't exists a good enough reason why this shouldn't be moved to cpufreq core instead. There are few special cases though, like exynos5440, which doesn't do everything on the call to ->target_index() routine and call some kind of bottom halves for doing this work, work/tasklet/etc.. They may continue doing notification from their own code and so this patch introduces another flag: CPUFREQ_NO_NOTIFICATION, which will be set by such drivers. This is Fifth part of my cleanup work for CPUFreq, first three are (And obviously its rebased over them): 1: cpufreq: Introduce cpufreq_table_validate_and_show() https://lkml.org/lkml/2013/8/8/263 2: cpufreq: define generic routines for cpufreq drivers https://lkml.org/lkml/2013/8/10/48 3. CPUFreq: Implement light weight ->target(): for 3.13 https://lkml.org/lkml/2013/8/13/349 4. CPUFreq: set policy->cur in cpufreq core instead of drivers https://lkml.org/lkml/2013/8/14/288 All these are pushed here: https://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/… -- viresh Cc: Andrew Lunn <andrew(a)lunn.ch> Cc: David S. Miller <davem(a)davemloft.net> Cc: Dmitry Eremin-Solenikov <dbaryshkov(a)gmail.com> Cc: Eric Miao <eric.y.miao(a)gmail.com> Cc: Hans-Christian Egtvedt <egtvedt(a)samfundet.no> Cc: Jesper Nilsson <jesper.nilsson(a)axis.com> Cc: John Crispin <blogic(a)openwrt.org> Cc: Kukjin Kim <kgene.kim(a)samsung.com> Cc: Linus Walleij <linus.walleij(a)linaro.org> Cc: linux-cris-kernel(a)axis.com Cc: Mikael Starvik <starvik(a)axis.com> Cc: Russell King <linux(a)arm.linux.org.uk> Cc: Santosh Shilimkar <santosh.shilimkar(a)ti.com> Cc: Sekhar Nori <nsekhar(a)ti.com> Cc: Shawn Guo <shawn.guo(a)linaro.org> Cc: sparclinux(a)vger.kernel.org Cc: spear-devel(a)list.st.com Cc: Stephen Warren <swarren(a)nvidia.com> Cc: Steven Miao <realmz6(a)gmail.com> Cc: Tony Luck <tony.luck(a)intel.com> Viresh Kumar (34): cpufreq: move freq change notifications to cpufreq core cpufreq: acpi: remove calls to cpufreq_notify_transition() cpufreq: arm_big_little: remove calls to cpufreq_notify_transition() cpufreq: at32ap: remove calls to cpufreq_notify_transition() cpufreq: blackfin: remove calls to cpufreq_notify_transition() cpufreq: cpu0: remove calls to cpufreq_notify_transition() cpufreq: cris: remove calls to cpufreq_notify_transition() cpufreq: davinci: remove calls to cpufreq_notify_transition() cpufreq: dbx500: remove calls to cpufreq_notify_transition() cpufreq: e_powersaver: remove calls to cpufreq_notify_transition() cpufreq: elanfreq: remove calls to cpufreq_notify_transition() cpufreq: exynos: remove calls to cpufreq_notify_transition() cpufreq: exynos5440: set CPUFREQ_NO_NOTIFICATION flag cpufreq: ia64-acpi: remove calls to cpufreq_notify_transition() cpufreq: imx6q: remove calls to cpufreq_notify_transition() cpufreq: kirkwood: remove calls to cpufreq_notify_transition() cpufreq: longhaul: set CPUFREQ_NO_NOTIFICATION flag cpufreq: loongson2: remove calls to cpufreq_notify_transition() cpufreq: maple: remove calls to cpufreq_notify_transition() cpufreq: omap: remove calls to cpufreq_notify_transition() cpufreq: p4-clockmod: remove calls to cpufreq_notify_transition() cpufreq: pasemi: remove calls to cpufreq_notify_transition() cpufreq: pmac: remove calls to cpufreq_notify_transition() cpufreq: powernow: remove calls to cpufreq_notify_transition() cpufreq: ppc: remove calls to cpufreq_notify_transition() cpufreq: pxa: remove calls to cpufreq_notify_transition() cpufreq: s3c: remove calls to cpufreq_notify_transition() cpufreq: s5pv210: remove calls to cpufreq_notify_transition() cpufreq: sa11x0: remove calls to cpufreq_notify_transition() cpufreq: sc520: remove calls to cpufreq_notify_transition() cpufreq: sparc: remove calls to cpufreq_notify_transition() cpufreq: SPEAr: remove calls to cpufreq_notify_transition() cpufreq: speedstep: remove calls to cpufreq_notify_transition() cpufreq: tegra: remove calls to cpufreq_notify_transition() drivers/cpufreq/acpi-cpufreq.c | 14 ++------- drivers/cpufreq/arm_big_little.c | 25 ++-------------- drivers/cpufreq/at32ap-cpufreq.c | 22 ++++++-------- drivers/cpufreq/blackfin-cpufreq.c | 22 +++++--------- drivers/cpufreq/cpufreq-cpu0.c | 33 ++++++++------------- drivers/cpufreq/cpufreq.c | 34 +++++++++++++++++++++ drivers/cpufreq/cris-artpec3-cpufreq.c | 8 ----- drivers/cpufreq/cris-etraxfs-cpufreq.c | 8 ----- drivers/cpufreq/davinci-cpufreq.c | 30 +++++++------------ drivers/cpufreq/dbx500-cpufreq.c | 22 +------------- drivers/cpufreq/e_powersaver.c | 23 ++------------- drivers/cpufreq/elanfreq.c | 13 -------- drivers/cpufreq/exynos-cpufreq.c | 28 +++++------------- drivers/cpufreq/exynos5440-cpufreq.c | 2 +- drivers/cpufreq/ia64-acpi-cpufreq.c | 19 ------------ drivers/cpufreq/imx6q-cpufreq.c | 39 ++++++++++-------------- drivers/cpufreq/kirkwood-cpufreq.c | 54 +++++++++++++--------------------- drivers/cpufreq/longhaul.c | 1 + drivers/cpufreq/loongson2_cpufreq.c | 16 ---------- drivers/cpufreq/maple-cpufreq.c | 18 +----------- drivers/cpufreq/omap-cpufreq.c | 39 +++++++++--------------- drivers/cpufreq/p4-clockmod.c | 10 ------- drivers/cpufreq/pasemi-cpufreq.c | 14 +-------- drivers/cpufreq/pmac32-cpufreq.c | 20 +++---------- drivers/cpufreq/pmac64-cpufreq.c | 18 +----------- drivers/cpufreq/powernow-k6.c | 8 ----- drivers/cpufreq/powernow-k7.c | 11 +------ drivers/cpufreq/powernow-k8.c | 15 +--------- drivers/cpufreq/ppc-corenet-cpufreq.c | 19 +----------- drivers/cpufreq/ppc_cbe_cpufreq.c | 19 +----------- drivers/cpufreq/pxa2xx-cpufreq.c | 27 ++++------------- drivers/cpufreq/pxa3xx-cpufreq.c | 12 -------- drivers/cpufreq/s3c2416-cpufreq.c | 21 +++---------- drivers/cpufreq/s3c64xx-cpufreq.c | 48 ++++++++++-------------------- drivers/cpufreq/s5pv210-cpufreq.c | 16 ++++------ drivers/cpufreq/sa1100-cpufreq.c | 17 ++++------- drivers/cpufreq/sa1110-cpufreq.c | 12 ++------ drivers/cpufreq/sc520_freq.c | 11 ------- drivers/cpufreq/sparc-us2e-cpufreq.c | 7 ----- drivers/cpufreq/sparc-us3-cpufreq.c | 7 ----- drivers/cpufreq/spear-cpufreq.c | 13 +------- drivers/cpufreq/speedstep-centrino.c | 20 +------------ drivers/cpufreq/speedstep-ich.c | 9 ------ drivers/cpufreq/speedstep-smi.c | 7 ----- drivers/cpufreq/tegra-cpufreq.c | 25 ++++------------ include/linux/cpufreq.h | 6 ++++ 46 files changed, 205 insertions(+), 657 deletions(-) -- 1.7.12.rc2.18.g61b472e

8 years, 8 months

6
45
0 0

[PATCH] usb: dwc3: ep0: Fix the possible missed request for handling delay STATUS phase

by Baolin Wang

When handing the SETUP packet by composite_setup(), we will release the dwc->lock. If we get the 'USB_GADGET_DELAYED_STATUS' result from setup function, which means we need to delay handling the STATUS phase. But during the lock release period, maybe the request for handling delay STATUS phase has been queued into list before we set 'dwc->delayed_status' flag or entering 'EP0_STATUS_PHASE' phase, then we will miss the chance to handle the STATUS phase. Thus we should check if the request for delay STATUS phase has been enqueued when entering 'EP0_STATUS_PHASE' phase in dwc3_ep0_xfernotready(), if so, we should handle it. Signed-off-by: Baolin Wang <baolin.wang(a)linaro.org> --- drivers/usb/dwc3/ep0.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/drivers/usb/dwc3/ep0.c b/drivers/usb/dwc3/ep0.c index 9bb1f85..e689ced 100644 --- a/drivers/usb/dwc3/ep0.c +++ b/drivers/usb/dwc3/ep0.c @@ -1123,7 +1123,21 @@ static void dwc3_ep0_xfernotready(struct dwc3 *dwc, dwc->ep0state = EP0_STATUS_PHASE; if (dwc->delayed_status) { + struct dwc3_ep *dep = dwc->eps[0]; + WARN_ON_ONCE(event->endpoint_number != 1); + /* + * We should handle the delay STATUS phase here if the + * request for handling delay STATUS has been queued + * into the list. + */ + if (!list_empty(&dep->pending_list)) { + dwc->delayed_status = false; + usb_gadget_set_state(&dwc->gadget, + USB_STATE_CONFIGURED); + dwc3_ep0_do_control_status(dwc, event); + } + return; } -- 1.7.9.5

9 years, 3 months

3
22
0 0

[PATCH v6] clk: mediatek: Export CPU mux clocks for CPU frequency control

by Pi-Cheng Chen

From: "pi-cheng.chen" <pi-cheng.chen(a)linaro.org> This patch adds CPU mux clocks which are used by Mediatek cpufreq driver for intermediate clock source switching. Signed-off-by: Pi-Cheng Chen <pi-cheng.chen(a)linaro.org> --- Changes in v6: - Relace __clk_get_num_parents with clk_hw_get_num_parents to reflect API change Changes in v5: - Replace __initdata with __initconst to fix compiling error Changes in v4: - Fix some minor issues for v3 - Rebase to the patch that adds 13mhz clock for MT8173[1] Changes in v3: - Rebase to 4.2-rc1 - Fix some issues of v2 Changes in v2: - Remove use of .determine_rate callback --- drivers/clk/mediatek/Makefile | 2 +- drivers/clk/mediatek/clk-cpumux.c | 127 +++++++++++++++++++++++++++++++++ drivers/clk/mediatek/clk-cpumux.h | 22 ++++++ drivers/clk/mediatek/clk-mt8173.c | 23 ++++++ include/dt-bindings/clock/mt8173-clk.h | 4 +- 5 files changed, 176 insertions(+), 2 deletions(-) create mode 100644 drivers/clk/mediatek/clk-cpumux.c create mode 100644 drivers/clk/mediatek/clk-cpumux.h diff --git a/drivers/clk/mediatek/Makefile b/drivers/clk/mediatek/Makefile index 8e4b2a4..299917a 100644 --- a/drivers/clk/mediatek/Makefile +++ b/drivers/clk/mediatek/Makefile @@ -1,4 +1,4 @@ -obj-y += clk-mtk.o clk-pll.o clk-gate.o +obj-y += clk-mtk.o clk-pll.o clk-gate.o clk-cpumux.o obj-$(CONFIG_RESET_CONTROLLER) += reset.o obj-y += clk-mt8135.o obj-y += clk-mt8173.o diff --git a/drivers/clk/mediatek/clk-cpumux.c b/drivers/clk/mediatek/clk-cpumux.c new file mode 100644 index 0000000..91b5238 --- /dev/null +++ b/drivers/clk/mediatek/clk-cpumux.c @@ -0,0 +1,127 @@ +/* + * Copyright (c) 2015 Linaro Ltd. + * Author: Pi-Cheng Chen <pi-cheng.chen(a)linaro.org> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#include <linux/clk-provider.h> +#include <linux/mfd/syscon.h> +#include <linux/slab.h> + +#include "clk-mtk.h" +#include "clk-cpumux.h" + +struct mtk_clk_cpumux { + struct clk_hw hw; + struct regmap *regmap; + u32 reg; + u32 mask; + u8 shift; +}; + +static inline struct mtk_clk_cpumux *to_clk_mux(struct clk_hw *_hw) +{ + return container_of(_hw, struct mtk_clk_cpumux, hw); +} + +static u8 clk_cpumux_get_parent(struct clk_hw *hw) +{ + struct mtk_clk_cpumux *mux = to_clk_mux(hw); + int num_parents = clk_hw_get_num_parents(hw); + unsigned int val; + + regmap_read(mux->regmap, mux->reg, &val); + + val >>= mux->shift; + val &= mux->mask; + + if (val >= num_parents) + return -EINVAL; + + return val; +} + +static int clk_cpumux_set_parent(struct clk_hw *hw, u8 index) +{ + struct mtk_clk_cpumux *mux = to_clk_mux(hw); + u32 mask, val; + + val = index << mux->shift; + mask = mux->mask << mux->shift; + + return regmap_update_bits(mux->regmap, mux->reg, mask, val); +} + +static const struct clk_ops clk_cpumux_ops = { + .get_parent = clk_cpumux_get_parent, + .set_parent = clk_cpumux_set_parent, +}; + +static struct clk __init *mtk_clk_register_cpumux(const struct mtk_composite *mux, + struct regmap *regmap) +{ + struct mtk_clk_cpumux *cpumux; + struct clk *clk; + struct clk_init_data init; + + cpumux = kzalloc(sizeof(*cpumux), GFP_KERNEL); + if (!cpumux) + return ERR_PTR(-ENOMEM); + + init.name = mux->name; + init.ops = &clk_cpumux_ops; + init.parent_names = mux->parent_names; + init.num_parents = mux->num_parents; + init.flags = mux->flags; + + cpumux->reg = mux->mux_reg; + cpumux->shift = mux->mux_shift; + cpumux->mask = BIT(mux->mux_width) - 1; + cpumux->regmap = regmap; + cpumux->hw.init = &init; + + clk = clk_register(NULL, &cpumux->hw); + if (IS_ERR(clk)) + kfree(cpumux); + + return clk; +} + +int __init mtk_clk_register_cpumuxes(struct device_node *node, + const struct mtk_composite *clks, int num, + struct clk_onecell_data *clk_data) +{ + int i; + struct clk *clk; + struct regmap *regmap; + + regmap = syscon_node_to_regmap(node); + if (IS_ERR(regmap)) { + pr_err("Cannot find regmap for %s: %ld\n", node->full_name, + PTR_ERR(regmap)); + return PTR_ERR(regmap); + } + + for (i = 0; i < num; i++) { + const struct mtk_composite *mux = &clks[i]; + + clk = mtk_clk_register_cpumux(mux, regmap); + if (IS_ERR(clk)) { + pr_err("Failed to register clk %s: %ld\n", + mux->name, PTR_ERR(clk)); + continue; + } + + clk_data->clks[mux->id] = clk; + } + + return 0; +} diff --git a/drivers/clk/mediatek/clk-cpumux.h b/drivers/clk/mediatek/clk-cpumux.h new file mode 100644 index 0000000..52c769f --- /dev/null +++ b/drivers/clk/mediatek/clk-cpumux.h @@ -0,0 +1,22 @@ +/* + * Copyright (c) 2015 Linaro Ltd. + * Author: Pi-Cheng Chen <pi-cheng.chen(a)linaro.org> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#ifndef __DRV_CLK_CPUMUX_H +#define __DRV_CLK_CPUMUX_H + +int mtk_clk_register_cpumuxes(struct device_node *node, + const struct mtk_composite *clks, int num, + struct clk_onecell_data *clk_data); + +#endif /* __DRV_CLK_CPUMUX_H */ diff --git a/drivers/clk/mediatek/clk-mt8173.c b/drivers/clk/mediatek/clk-mt8173.c index 9ea6aa1..b02d310 100644 --- a/drivers/clk/mediatek/clk-mt8173.c +++ b/drivers/clk/mediatek/clk-mt8173.c @@ -20,6 +20,7 @@ #include "clk-mtk.h" #include "clk-gate.h" +#include "clk-cpumux.h" #include <dt-bindings/clock/mt8173-clk.h> @@ -518,6 +519,25 @@ static const char * const i2s3_b_ck_parents[] __initconst = { "apll2_div5" }; +static const char * const ca53_parents[] __initconst = { + "clk26m", + "armca7pll", + "mainpll", + "univpll" +}; + +static const char * const ca57_parents[] __initconst = { + "clk26m", + "armca15pll", + "mainpll", + "univpll" +}; + +static const struct mtk_composite cpu_muxes[] __initconst = { + MUX(CLK_INFRA_CA53SEL, "infra_ca53_sel", ca53_parents, 0x0000, 0, 2), + MUX(CLK_INFRA_CA57SEL, "infra_ca57_sel", ca57_parents, 0x0000, 2, 2), +}; + static const struct mtk_composite top_muxes[] __initconst = { /* CLK_CFG_0 */ MUX(CLK_TOP_AXI_SEL, "axi_sel", axi_parents, 0x0040, 0, 3), @@ -760,6 +780,9 @@ static void __init mtk_infrasys_init(struct device_node *node) clk_data); mtk_clk_register_factors(infra_divs, ARRAY_SIZE(infra_divs), clk_data); + mtk_clk_register_cpumuxes(node, cpu_muxes, ARRAY_SIZE(cpu_muxes), + clk_data); + r = of_clk_add_provider(node, of_clk_src_onecell_get, clk_data); if (r) pr_err("%s(): could not register clock provider: %d\n", diff --git a/include/dt-bindings/clock/mt8173-clk.h b/include/dt-bindings/clock/mt8173-clk.h index fa2a2bb..a17cbaa 100644 --- a/include/dt-bindings/clock/mt8173-clk.h +++ b/include/dt-bindings/clock/mt8173-clk.h @@ -188,7 +188,9 @@ #define CLK_INFRA_PMICSPI 10 #define CLK_INFRA_PMICWRAP 11 #define CLK_INFRA_CLK_13M 12 -#define CLK_INFRA_NR_CLK 13 +#define CLK_INFRA_CA53SEL 13 +#define CLK_INFRA_CA57SEL 14 +#define CLK_INFRA_NR_CLK 15 /* PERI_SYS */ -- 1.9.1

9 years, 4 months

4
8
0 0

[PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework

by Viresh Kumar

Hi, This patchset adds support for cpufreq selftests to the kernel selftest framework. More details can be found on individual patches. These are all tested after installation of selftests on ARM Dual A15 core Exynos platform. The content of the output file for the basic tests looks like this: http://pastebin.com/nBY9AfD5 . -- viresh Viresh Kumar (4): selftest: cpufreq: Add support for cpufreq tests selftest: cpufreq: Add suspend/resume/hibernate support selftest: cpufreq: Add support to test cpufreq modules selftest: cpufreq: Add special tests tools/testing/selftests/Makefile | 1 + tools/testing/selftests/cpufreq/Makefile | 8 + tools/testing/selftests/cpufreq/cpu.sh | 84 ++++++++ tools/testing/selftests/cpufreq/cpufreq.sh | 241 ++++++++++++++++++++++ tools/testing/selftests/cpufreq/governor.sh | 153 ++++++++++++++ tools/testing/selftests/cpufreq/main.sh | 194 ++++++++++++++++++ tools/testing/selftests/cpufreq/module.sh | 243 +++++++++++++++++++++++ tools/testing/selftests/cpufreq/special-tests.sh | 115 +++++++++++ 8 files changed, 1039 insertions(+) create mode 100644 tools/testing/selftests/cpufreq/Makefile create mode 100755 tools/testing/selftests/cpufreq/cpu.sh create mode 100755 tools/testing/selftests/cpufreq/cpufreq.sh create mode 100755 tools/testing/selftests/cpufreq/governor.sh create mode 100755 tools/testing/selftests/cpufreq/main.sh create mode 100755 tools/testing/selftests/cpufreq/module.sh create mode 100755 tools/testing/selftests/cpufreq/special-tests.sh -- 2.7.1.410.g6faf27b

9 years, 4 months

2
11
0 0

[PATCH 0/6] PM / Domains: Implement domain performance states

by Viresh Kumar

Hi, An earlier series[1] tried to implement bindings for PM domain performance states. Rob Herring suggested that we can actually write the supporting code first instead of bindings, as that will make things easier to understand for all. The bindings [1] aren't discarded yet and this series is based on a version of those only. The bindings are only used by the last patch, which should not be applied and is only sent for completeness. All other patches can be reviewed/applied whenever the maintainers feel they look good. A brief summary of the problem this series is trying to solve: Some platforms have the capability to configure the performance state of their Power Domains. The performance levels are represented by positive integer values, a lower value represents lower performance state. We decided earlier that we should extend Power Domain framework to support active state power management as well. The power-domains until now were only concentrating on the idle state management of the device and this needs to change in order to reuse the infrastructure of power domains for active state management. The first 5 patches update the PM domain and QoS frameworks to support that and the last one presents the front end interface to it. All the patches are tested by hacking the OPP core a bit for now. -- viresh [1] https://marc.info/?l=linux-kernel&m=148154020127722&w=2 Viresh Kumar (6): PM / QOS: Add default case to the switch PM / QOS: Pass request type to dev_pm_qos_{add|remove}_notifier() PM / QOS: Add 'performance' request PM / domain: Register for PM QOS performance notifier PM / domain: Save/restore performance state at runtime suspend/resume PM / OPP: Add support to parse domain-performance-state Documentation/power/pm_qos_interface.txt | 11 ++-- drivers/base/power/domain.c | 102 ++++++++++++++++++++++++++++--- drivers/base/power/opp/core.c | 75 +++++++++++++++++++++++ drivers/base/power/opp/debugfs.c | 4 ++ drivers/base/power/opp/of.c | 44 +++++++++++++ drivers/base/power/opp/opp.h | 12 ++++ drivers/base/power/qos.c | 74 +++++++++++++++++++--- include/linux/pm_domain.h | 6 ++ include/linux/pm_qos.h | 16 +++-- 9 files changed, 322 insertions(+), 22 deletions(-) -- 2.7.1.410.g6faf27b

9 years, 4 months

3
12
0 0

next-20170131 build: 2 failures 3 warnings (next-20170131)

by Build bot for Mark Brown

Tree/Branch: next-20170131 Git describe: next-20170131 Commit: 7c088bd91d Add linux-next specific files for 20170131 Build Time: 105 min 2 sec Passed: 8 / 10 ( 80.00 %) Failed: 2 / 10 ( 20.00 %) Errors: 6 Warnings: 3 Section Mismatches: 0 Failed defconfigs: arm-allmodconfig Errors: arm-allmodconfig ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : x86_64-allnoconfig 1 warnings 0 mismatches : arm64-allnoconfig 2 warnings 0 mismatches : arm-allmodconfig 1 warnings 0 mismatches : arm-allnoconfig ------------------------------------------------------------------------------- Errors summary: 6 1 ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' 1 ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' 1 ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] Warnings Summary: 3 3 ../drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] 1 ../include/linux/dynamic_debug.h:126:3: warning: 'ept_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:815:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- x86_64-allnoconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] ------------------------------------------------------------------------------- arm64-allnoconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] ------------------------------------------------------------------------------- arm-allmodconfig : FAIL, 6 errors, 2 warnings, 0 section mismatches Errors: ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:815:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ../include/linux/dynamic_debug.h:126:3: warning: 'ept_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allnoconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but not used [-Wunused-variable] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

4
3
0 0

RE: [PATCH V2 07/12] PM / OPP: Update OPP users to put reference

by MyungJoo Ham

> This patch updates dev_pm_opp_find_freq_*() routines to get a reference > to the OPPs returned by them. > > Also updates the users of dev_pm_opp_find_freq_*() routines to call > dev_pm_opp_put() after they are done using the OPPs. > > As it is guaranteed the that OPPs wouldn't get freed while being used, > the RCU read side locking present with the users isn't required anymore. > Drop it as well. > > This patch also updates all users of devfreq_recommended_opp() which was > returning an OPP received from the OPP core. > > Note that some of the OPP core routines have gained > rcu_read_{lock|unlock}() calls, as those still use RCU specific APIs > within them. > > Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> > Reviewed-by: Chanwoo Choi <cw00.choi(a)samsung.com> [Devfreq] This patch gets a lot of fails during application. For devfreq-side, I've got: error: drivers/devfreq/devfreq.c: patch does not apply error: patch failed: drivers/devfreq/exynos-bus.c:103 error: drivers/devfreq/exynos-bus.c: patch does not apply error: patch failed: drivers/devfreq/governor_passive.c:59 error: drivers/devfreq/governor_passive.c: patch does not apply error: patch failed: drivers/devfreq/rk3399_dmc.c:91 error: drivers/devfreq/rk3399_dmc.c: patch does not apply error: patch failed: drivers/devfreq/tegra-devfreq.c:487 error: drivers/devfreq/tegra-devfreq.c: patch does not apply With the condition that you are going to properly rebase the patch, you may add "Reviewed-by" from me. (the code itself looks fine.) Cheers, MyungJoo > --- > arch/arm/mach-omap2/pm.c | 5 +- > drivers/base/power/opp/core.c | 114 +++++++++++++++++++---------------- > drivers/base/power/opp/cpu.c | 22 ++----- > drivers/clk/tegra/clk-dfll.c | 17 ++---- > drivers/cpufreq/exynos5440-cpufreq.c | 5 +- > drivers/cpufreq/imx6q-cpufreq.c | 10 +-- > drivers/cpufreq/mt8173-cpufreq.c | 8 +-- > drivers/cpufreq/omap-cpufreq.c | 4 +- > drivers/devfreq/devfreq.c | 14 ++--- > drivers/devfreq/exynos-bus.c | 14 ++--- > drivers/devfreq/governor_passive.c | 4 +- > drivers/devfreq/rk3399_dmc.c | 16 ++--- > drivers/devfreq/tegra-devfreq.c | 4 +- > drivers/thermal/cpu_cooling.c | 11 +--- > drivers/thermal/devfreq_cooling.c | 15 ++--- > 15 files changed, 110 insertions(+), 153 deletions(-) >

9 years, 4 months

2
1
0 0

master build: 0 failures 0 warnings (v4.10-rc6-8-gf9a42e0)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc6-8-gf9a42e0 Commit: f9a42e0d58 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc Build Time: 104 min 0 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc6-2-g751321b)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc6-2-g751321b Commit: 751321b3dd Merge tag 'rtc-4.10-2' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux Build Time: 103 min 47 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

next-20170130 build: 1 failures 3 warnings (next-20170130)

by Build bot for Mark Brown

Tree/Branch: next-20170130 Git describe: next-20170130 Commit: 14dcd7ee9f Add linux-next specific files for 20170130 Build Time: 104 min 18 sec Passed: 9 / 10 ( 90.00 %) Failed: 1 / 10 ( 10.00 %) Errors: 6 Warnings: 3 Section Mismatches: 0 Failed defconfigs: arm-allmodconfig Errors: arm-allmodconfig ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 2 warnings 0 mismatches : arm-allmodconfig 1 warnings 0 mismatches : arm-multi_v5_defconfig ------------------------------------------------------------------------------- Errors summary: 6 1 ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' 1 ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' 1 ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] 1 ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] Warnings Summary: 3 1 ../include/linux/dynamic_debug.h:126:3: warning: 'ept_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/pinctrl/mvebu/pinctrl-kirkwood.c:460:19: warning: unused variable 'res' [-Wunused-variable] 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:816:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : FAIL, 6 errors, 2 warnings, 0 section mismatches Errors: ../drivers/hsi/clients/cmt_speech.c:1114:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/armada/armada_gem.c:38:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_drv.c:468:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/etnaviv/etnaviv_gem.c:178:5: error: conflicting types for 'etnaviv_gem_fault' ../drivers/gpu/drm/omapdrm/omap_drv.c:696:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] ../drivers/gpu/drm/omapdrm/omap_gem.c:531:5: error: conflicting types for 'omap_gem_fault' Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:816:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ../include/linux/dynamic_debug.h:126:3: warning: 'ept_cfg' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-multi_v5_defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/pinctrl/mvebu/pinctrl-kirkwood.c:460:19: warning: unused variable 'res' [-Wunused-variable] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

[PATCH 1/2] ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START

by Viresh Kumar

acpi_processor_ppc_notifier() can live without using CPUFREQ_START (which is gonna be removed soon). Simplify it a bit. Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- Rebased over: https://marc.info/?l=linux-kernel&m=148359167516831&w=2 drivers/acpi/processor_perflib.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/acpi/processor_perflib.c b/drivers/acpi/processor_perflib.c index f0b4a981b8d3..1ceea1143a1c 100644 --- a/drivers/acpi/processor_perflib.c +++ b/drivers/acpi/processor_perflib.c @@ -75,14 +75,12 @@ static int acpi_processor_ppc_notifier(struct notifier_block *nb, struct acpi_processor *pr; unsigned int ppc = 0; - if (event == CPUFREQ_START && ignore_ppc <= 0) { - ignore_ppc = 0; - return 0; - } - if (ignore_ppc) return 0; + if (ignore_ppc < 0) + ignore_ppc = 0; + if (event != CPUFREQ_ADJUST) return 0; -- 2.7.1.410.g6faf27b

9 years, 4 months

3
5
0 0

v4.10-rc6 build: 0 failures 0 warnings (v4.10-rc6)

by Build bot for Mark Brown

Tree/Branch: v4.10-rc6 Git describe: v4.10-rc6 Commit: 566cf877a1 Linux 4.10-rc6 Build Time: 103 min 18 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc5-396-g2c5d955)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc5-396-g2c5d955 Commit: 2c5d9555d6 Merge branch 'parisc-4.10-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux Build Time: 103 min 20 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc5-393-g53cd1ad)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc5-393-g53cd1ad Commit: 53cd1ad1a6 Merge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux Build Time: 103 min 23 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

[PATCH v9 0/8] Add PWM and IIO timer drivers for STM32

by Benjamin Gaignard

version 9: - fix pwm commit message header - re-oerder nodes in DT file version 8: - rebase on v4.10-rc4 - fix comments done by Thierry on PWM - reword "reg" parameter description - change kernel kernel in IIO ABI documentation version 7: - rebase on v4.10-rc2 - remove iio_device code from driver and keep only the trigger part version 6: - rename stm32-gptimer in stm32-timers. - change "st,stm32-gptimer" compatible to "st,stm32-timers". - modify "st,breakinput" parameter in pwm part. - split DT patch in 2 version 5: - fix comments done on version 4 - rebased on kernel 4.9-rc8 - change nodes names and re-order then by addresses version 4: - fix comments done on version 3 - don't use interrupts anymore in IIO timer - detect hardware capabilities at probe time to simplify binding version 3: - no change on mfd and pwm divers patches - add cross reference between bindings - change compatible to "st,stm32-timer-trigger" - fix attributes access rights - use string instead of int for master_mode and slave_mode - document device attributes in sysfs-bus-iio-timer-stm32 - update DT with the new compatible version 2: - keep only one compatible per driver - use DT parameters to describe hardware block configuration: - pwm channels, complementary output, counter size, break input - triggers accepted and create by IIO timers - change DT to limite use of reference to the node - interrupt is now in IIO timer driver - rename stm32-mfd-timer to stm32-timers (for general purpose timer) The following patches enable PWM and IIO Timer features for STM32 platforms. Those two features are mixed into the registers of the same hardware block (named general purpose timer) which lead to introduce a multifunctions driver on the top of them to be able to share the registers. In STM32f4 14 instances of timer hardware block exist, even if they all have the same register mapping they could have a different number of pwm channels and/or different triggers capabilities. We use various parameters in DT to describe the differences between hardware blocks The MFD (stm32-timers.c) takes care of clock and register mapping by using regmap. stm32_timers structure is provided to its sub-node to share those information. PWM driver is implemented into pwm-stm32.c. Depending of the instance we may have up to 4 channels, sometime with complementary outputs or 32 bits counter instead of 16 bits. Some hardware blocks may also have a break input function which allows to stop pwm depending of a level, defined in devicetree, on an external pin. IIO timer driver (stm32-timer-trigger.c and stm32-timer-trigger.h) define a list of hardware triggers usable by hardware blocks like ADC, DAC or other timers. The matrix of possible connections between blocks is quite complex so we use trigger names and is_stm32_iio_timer_trigger() function to be sure that triggers are valid and configure the IPs. At run time IIO timer hardware blocks can configure (through "master_mode" IIO device attribute) which internal signal (counter enable, reset, comparison block, etc...) is used to generate the trigger. Benjamin Gaignard (8): MFD: add bindings for STM32 Timers driver MFD: add STM32 Timers driver dt-bindings: pwm: Add STM32 bindings pwm: add driver for STM32 plaftorm IIO: add bindings for STM32 timer trigger driver IIO: add STM32 timer trigger driver ARM: dts: stm32: add Timers driver for stm32f429 MCU ARM: dts: stm32: Enable pwm1 and pwm3 for stm32f469-disco .../ABI/testing/sysfs-bus-iio-timer-stm32 | 29 ++ .../bindings/iio/timer/stm32-timer-trigger.txt | 23 ++ .../devicetree/bindings/mfd/stm32-timers.txt | 46 +++ .../devicetree/bindings/pwm/pwm-stm32.txt | 35 ++ arch/arm/boot/dts/stm32f429.dtsi | 275 ++++++++++++++ arch/arm/boot/dts/stm32f469-disco.dts | 28 ++ drivers/iio/trigger/Kconfig | 9 + drivers/iio/trigger/Makefile | 1 + drivers/iio/trigger/stm32-timer-trigger.c | 342 ++++++++++++++++++ drivers/mfd/Kconfig | 11 + drivers/mfd/Makefile | 2 + drivers/mfd/stm32-timers.c | 80 +++++ drivers/pwm/Kconfig | 9 + drivers/pwm/Makefile | 1 + drivers/pwm/pwm-stm32.c | 398 +++++++++++++++++++++ include/linux/iio/timer/stm32-timer-trigger.h | 62 ++++ include/linux/mfd/stm32-timers.h | 71 ++++ 17 files changed, 1422 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 create mode 100644 Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt create mode 100644 Documentation/devicetree/bindings/mfd/stm32-timers.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-stm32.txt create mode 100644 drivers/iio/trigger/stm32-timer-trigger.c create mode 100644 drivers/mfd/stm32-timers.c create mode 100644 drivers/pwm/pwm-stm32.c create mode 100644 include/linux/iio/timer/stm32-timer-trigger.h create mode 100644 include/linux/mfd/stm32-timers.h -- 1.9.1

9 years, 4 months

6
19
0 0

[RFC simple allocator v1 0/2] Simple allocator

by Benjamin Gaignard

The goal of this RFC is to understand if a common ioctl for specific memory regions allocations is needed/welcome. Obviously it will not replace allocation done in linux kernel frameworks like v4l2, drm/kms or others, but offer an alternative when you don't want/need to use them for buffer allocation. To keep a compatibility with what already exist allocated buffers are exported in userland as dmabuf file descriptor (like ION is doing). "Unix Device Memory Allocator" project [1] wants to create a userland library which may allow to select, depending of the devices constraint, the best back-end for allocation. With this RFC I would to propose to have common ioctl for a maximum of allocators to avoid to duplicated back-ends for this library. One of the issues that lead me to propose this RFC it is that since the beginning it is a problem to allocate contiguous memory (CMA) without using v4l2 or drm/kms so the first allocator available in this RFC use CMA memory. An other question is: do we have others memory regions that could be interested by this new framework ? I have in mind that some title memory regions could use it or replace ION heaps (system, carveout, etc...). Maybe it only solve CMA allocation issue, in this case there is no need to create a new framework but only a dedicated ioctl. Maybe the first thing to do is to change the name and the location of this module, suggestions are welcome. I have testing this code with the following program: #include <errno.h> #include <fcntl.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <unistd.h> #include <sys/ioctl.h> #include <sys/mman.h> #include <sys/stat.h> #include <sys/types.h> #include "simple-allocator.h" #define LENGTH 1024*16 void main (void) { struct simple_allocate_data data; int fd = open("/dev/cma0", O_RDWR, 0); int ret; void *mem; if (fd < 0) { printf("Can't open /dev/cma0\n"); return; } memset(&data, 0, sizeof(data)); data.length = LENGTH; data.flags = O_RDWR | O_CLOEXEC; ret = ioctl(fd, SA_IOC_ALLOC, &data); if (ret) { printf("Buffer allocation failed\n"); goto end; } mem = mmap(0, LENGTH, PROT_READ | PROT_WRITE, MAP_SHARED, data.fd, 0); if (mem == MAP_FAILED) { printf("mmap failed\n"); } memset(mem, 0xFF, LENGTH); munmap(mem, LENGTH); printf("test simple allocator CMA OK\n"); end: close(fd); } [1] https://github.com/cubanismo/allocator Benjamin Gaignard (2): Create Simple Allocator module add CMA simple allocator module Documentation/simple-allocator.txt | 81 ++++++++++ drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/simpleallocator/Kconfig | 17 +++ drivers/simpleallocator/Makefile | 2 + drivers/simpleallocator/simple-allocator-cma.c | 187 ++++++++++++++++++++++++ drivers/simpleallocator/simple-allocator-priv.h | 33 +++++ drivers/simpleallocator/simple-allocator.c | 180 +++++++++++++++++++++++ include/uapi/linux/simple-allocator.h | 35 +++++ 9 files changed, 538 insertions(+) create mode 100644 Documentation/simple-allocator.txt create mode 100644 drivers/simpleallocator/Kconfig create mode 100644 drivers/simpleallocator/Makefile create mode 100644 drivers/simpleallocator/simple-allocator-cma.c create mode 100644 drivers/simpleallocator/simple-allocator-priv.h create mode 100644 drivers/simpleallocator/simple-allocator.c create mode 100644 include/uapi/linux/simple-allocator.h -- 1.9.1

9 years, 4 months

3
4
0 0

master build: 2 failures 0 warnings (v4.10-rc5-71-ga4685d2)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc5-71-ga4685d2 Commit: a4685d2f58 Merge branch 'stable' of git://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile Build Time: 88 min 58 sec Passed: 8 / 10 ( 80.00 %) Failed: 2 / 10 ( 20.00 %) Errors: 10 Warnings: 0 Section Mismatches: 0 Failed defconfigs: arm64-allmodconfig Errors: arm64-allmodconfig ../kernel/sysctl_binary.c:1483:1: fatal error: error writing to /tmp/ccdidgz2.s: No space left on device ../arch/arm64/kernel/cpu-reset.S:17:0: fatal error: closing dependency file arch/arm64/kernel/.cpu-reset.o.d: No space left on device ../mm/maccess.c:7:0: fatal error: closing dependency file mm/.maccess.o.d: No space left on device ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio.c:583:1: fatal error: error writing to /tmp/ccc0uo18.s: No space left on device ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio-v3.c:654:1: fatal error: error writing to /tmp/ccXgcjH4.s: No space left on device ../arch/arm64/kernel/probes/simulate-insn.c:215:1: fatal error: error writing to /tmp/ccYFBFWu.s: No space left on device ../kernel/sys.c:2425:1: fatal error: error writing to /tmp/ccapnTIC.s: No space left on device ../kernel/signal.c:3651:1: fatal error: error writing to /tmp/ccrv3xkg.s: No space left on device ../include/linux/export.h:63:22: fatal error: error writing to /tmp/cc91nLLK.s: No space left on device ../mm/page_alloc.c:7484:1: fatal error: error writing to /tmp/ccVHZCyw.s: No space left on device ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- Errors summary: 10 1 ../mm/page_alloc.c:7484:1: fatal error: error writing to /tmp/ccVHZCyw.s: No space left on device 1 ../mm/maccess.c:7:0: fatal error: closing dependency file mm/.maccess.o.d: No space left on device 1 ../kernel/sysctl_binary.c:1483:1: fatal error: error writing to /tmp/ccdidgz2.s: No space left on device 1 ../kernel/sys.c:2425:1: fatal error: error writing to /tmp/ccapnTIC.s: No space left on device 1 ../kernel/signal.c:3651:1: fatal error: error writing to /tmp/ccrv3xkg.s: No space left on device 1 ../include/linux/export.h:63:22: fatal error: error writing to /tmp/cc91nLLK.s: No space left on device 1 ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio.c:583:1: fatal error: error writing to /tmp/ccc0uo18.s: No space left on device 1 ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio-v3.c:654:1: fatal error: error writing to /tmp/ccXgcjH4.s: No space left on device 1 ../arch/arm64/kernel/probes/simulate-insn.c:215:1: fatal error: error writing to /tmp/ccYFBFWu.s: No space left on device 1 ../arch/arm64/kernel/cpu-reset.S:17:0: fatal error: closing dependency file arch/arm64/kernel/.cpu-reset.o.d: No space left on device =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : FAIL, 10 errors, 0 warnings, 0 section mismatches Errors: ../kernel/sysctl_binary.c:1483:1: fatal error: error writing to /tmp/ccdidgz2.s: No space left on device ../arch/arm64/kernel/cpu-reset.S:17:0: fatal error: closing dependency file arch/arm64/kernel/.cpu-reset.o.d: No space left on device ../mm/maccess.c:7:0: fatal error: closing dependency file mm/.maccess.o.d: No space left on device ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio.c:583:1: fatal error: error writing to /tmp/ccc0uo18.s: No space left on device ../arch/arm64/kvm/../../../virt/kvm/arm/vgic/vgic-mmio-v3.c:654:1: fatal error: error writing to /tmp/ccXgcjH4.s: No space left on device ../arch/arm64/kernel/probes/simulate-insn.c:215:1: fatal error: error writing to /tmp/ccYFBFWu.s: No space left on device ../kernel/sys.c:2425:1: fatal error: error writing to /tmp/ccapnTIC.s: No space left on device ../kernel/signal.c:3651:1: fatal error: error writing to /tmp/ccrv3xkg.s: No space left on device ../include/linux/export.h:63:22: fatal error: error writing to /tmp/cc91nLLK.s: No space left on device ../mm/page_alloc.c:7484:1: fatal error: error writing to /tmp/ccVHZCyw.s: No space left on device ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

[PATCH V2 00/12] PM / OPP: Use kref and move away from RCU locking

by Viresh Kumar

Hi Rafael, This series is based over the other OPP series [1] which is ready to be merged and is fully reviewed. In this series, 11 out of 12 patches have Reviewed-by from Stephen. Only the 7th patch hasn't got any of those. @Stephen: Can you see if you can do a generic review of it as well? Thanks for continuing to review this stuff. The RCU locking isn't well suited for the OPP core. The RCU locking fits better for reader heavy stuff, while the OPP core have at max one or two readers only at a time. Over that, it was getting very confusing the way RCU locking was used within the OPP core. The individual OPPs are mostly well handled, i.e. for an update a new structure was created and then that replaced the older one. But the OPP tables were updated directly all the time from various parts of the core. Though they were mostly used from within RCU locked region, they didn't had much to do with RCU and were governed by the mutex instead. And that mixed with the 'opp_table_lock' has made the core even more confusing. Similar concerns were shared by Stephen Boyd earlier [2]. This patchset simplifies the locking in OPP core to great extent using Kernel reference counting mechanism along with per OPP table mutex. And finally it gets rid of RCU locking as well. Each and every patch of this series is individually: - build tested - boot tested with cpufreq-dt.ko module. Insmod and rmmod to make sure the OPPs and the OPP tables are getting freed. More testing is also done by various build and boot bots for last few days. And they reported lots of issues (both build and boot time) that helped making this series more robust: - Kernel CI (Linaro) - Fengguang Wu's bot (Intel) V1->V2: - Minor documentation fixes pointed out by Stephen - dev_pm_opp_put() is called only if OPP is valid (in the 7th patch) -- viresh [1] https://marc.info/?l=linux-kernel&m=148334828916156&w=2 [2] https://marc.info/?l=linux-kernel&m=147742717527548&w=2 Viresh Kumar (12): PM / OPP: Add per OPP table mutex PM / OPP: Add 'struct kref' to OPP table PM / OPP: Return opp_table from dev_pm_opp_set_*() routines PM / OPP: Take reference of the OPP table while adding/removing OPPs PM / OPP: Use dev_pm_opp_get_opp_table() instead of _add_opp_table() PM / OPP: Add 'struct kref' to struct dev_pm_opp PM / OPP: Update OPP users to put reference PM / OPP: Take kref from _find_opp_table() PM / OPP: Move away from RCU locking PM / OPP: Simplify _opp_set_availability() PM / OPP: Simplify dev_pm_opp_get_max_volt_latency() PM / OPP: Update Documentation to remove RCU specific bits Documentation/power/opp.txt | 52 +- arch/arm/mach-omap2/pm.c | 5 +- drivers/base/power/opp/core.c | 888 +++++++++++------------------------ drivers/base/power/opp/cpu.c | 66 +-- drivers/base/power/opp/of.c | 94 +--- drivers/base/power/opp/opp.h | 31 +- drivers/clk/tegra/clk-dfll.c | 17 +- drivers/cpufreq/exynos5440-cpufreq.c | 5 +- drivers/cpufreq/imx6q-cpufreq.c | 10 +- drivers/cpufreq/mt8173-cpufreq.c | 8 +- drivers/cpufreq/omap-cpufreq.c | 4 +- drivers/cpufreq/sti-cpufreq.c | 13 +- drivers/devfreq/devfreq.c | 14 +- drivers/devfreq/exynos-bus.c | 14 +- drivers/devfreq/governor_passive.c | 4 +- drivers/devfreq/rk3399_dmc.c | 16 +- drivers/devfreq/tegra-devfreq.c | 4 +- drivers/thermal/cpu_cooling.c | 11 +- drivers/thermal/devfreq_cooling.c | 15 +- include/linux/pm_opp.h | 48 +- 20 files changed, 433 insertions(+), 886 deletions(-) -- 2.7.1.410.g6faf27b

9 years, 4 months

1
12
0 0

master build: 2 failures 0 warnings (v4.10-rc4-281-gc497f8d)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-281-gc497f8d Commit: c497f8d172 Merge tag 'usb-4.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb Build Time: 103 min 9 sec Passed: 8 / 10 ( 80.00 %) Failed: 2 / 10 ( 20.00 %) Errors: 1 Warnings: 0 Section Mismatches: 0 Failed defconfigs: arm64-allmodconfig Errors: arm64-allmodconfig cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- Errors summary: 1 5 cat: write error: No space left on device =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : FAIL, 5 errors, 0 warnings, 0 section mismatches Errors: cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device cat: write error: No space left on device ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 1 failures 0 warnings (v4.10-rc4-264-g455a70c)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-264-g455a70c Commit: 455a70cbe7 Merge tag 'arc-4.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc Build Time: 101 min 20 sec Passed: 9 / 10 ( 90.00 %) Failed: 1 / 10 ( 10.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 Failed defconfigs: Errors: ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

[PATCH 00/12] PM / OPP: Use kref and move away from RCU locking

by Viresh Kumar

Hi Rafael, You can pretty much ignore this series until all other OPP cleanup/fixes get merged. I am posting these to get early reviews from Stephen as these patches have been lying with me for almost a week now. And I am also _not_ pushing these for 4.10-rc1. It all depends on how the reviews go. The RCU locking isn't well suited for the OPP core. The RCU locking fits better for reader heavy stuff, while the OPP core have at max one or two readers only at a time. Over that, it was getting very confusing the way RCU locking was used within the OPP core. The individual OPPs are mostly well handled, i.e. for an update a new structure was created and then that replaced the older one. But the OPP tables were updated directly all the time from various parts of the core. Though they were mostly used from within RCU locked region, they didn't had much to do with RCU and were governed by the mutex instead. And that mixed with the 'opp_table_lock' has made the core even more confusing. Similar concerns were shared by Stephen Boyd earlier [1]. This patchset simplifies the locking in OPP core to great extent using Kernel reference counting mechanism along with per OPP table mutex. And finally it gets rid of RCU locking as well. Each and every patch of this series is individually: - build tested - boot tested with cpufreq-dt.ko module. Insmod and rmmod to make sure the OPPs and the OPP tables are getting freed. More testing is also done by various build and boot bots for last few days. And they reported lots of issues (both build and boot time) that helped making this series more robust: - Kernel CI (Linaro) - Fengguang Wu's bot (Intel) This series has few dependencies though. It is rebased over: pm/bleeding-edge + OPP cleanup series [2] + few devfreq fixes [3], [4], and [5]. + A recent revert [6] Though all of those shall get merged before we end up reviewing this series. -- viresh [1] https://marc.info/?l=linux-kernel&m=147742717527548&w=2 [2] https://marc.info/?l=linux-pm&m=148108573618896&w=2 [3] https://patchwork.kernel.org/patch/9455789/ [4] https://patchwork.kernel.org/patch/9455757/ [5] https://marc.info/?l=linux-pm&m=148090824301852&w=2 [6] https://marc.info/?l=linux-kernel&m=148110674223377&w=2 Viresh Kumar (12): PM / OPP: Add per OPP table mutex PM / OPP: Add 'struct kref' to OPP table PM / OPP: Return opp_table from dev_pm_opp_set_*() routines PM / OPP: Take reference of the OPP table while adding/removing OPPs PM / OPP: Use dev_pm_opp_get_opp_table() instead of _add_opp_table() PM / OPP: Add 'struct kref' to struct dev_pm_opp PM / OPP: Update OPP users to put reference PM / OPP: Take kref from _find_opp_table() PM / OPP: Move away from RCU locking PM / OPP: Simplify _opp_set_availability() PM / OPP: Simplify dev_pm_opp_get_max_volt_latency() PM / OPP: Update Documentation to remove RCU specific bits Documentation/power/opp.txt | 47 +- arch/arm/mach-omap2/pm.c | 5 +- drivers/base/power/opp/core.c | 888 +++++++++++------------------------ drivers/base/power/opp/cpu.c | 66 +-- drivers/base/power/opp/of.c | 94 +--- drivers/base/power/opp/opp.h | 31 +- drivers/clk/tegra/clk-dfll.c | 17 +- drivers/cpufreq/exynos5440-cpufreq.c | 5 +- drivers/cpufreq/imx6q-cpufreq.c | 10 +- drivers/cpufreq/mt8173-cpufreq.c | 8 +- drivers/cpufreq/omap-cpufreq.c | 4 +- drivers/cpufreq/sti-cpufreq.c | 13 +- drivers/devfreq/devfreq.c | 14 +- drivers/devfreq/exynos-bus.c | 14 +- drivers/devfreq/governor_passive.c | 4 +- drivers/devfreq/rk3399_dmc.c | 16 +- drivers/devfreq/tegra-devfreq.c | 4 +- drivers/thermal/cpu_cooling.c | 11 +- drivers/thermal/devfreq_cooling.c | 14 +- include/linux/pm_opp.h | 48 +- 20 files changed, 429 insertions(+), 884 deletions(-) -- 2.7.1.410.g6faf27b

9 years, 4 months

5
36
0 0

master build: 0 failures 0 warnings (v4.10-rc4-164-g44b4b46)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-164-g44b4b46 Commit: 44b4b461a0 Merge tag 'armsoc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc Build Time: 127 min 51 sec Passed: 8 / 9 ( 88.89 %) Failed: 0 / 9 ( 0.00 %) Unknown: 1 / 9 ( 11.11 %) Errors: 73 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- Errors summary: 73 1 /tmp/ccLTO4eP.s: Fatal error: can't write 64 bytes to section .text of net/core/.tmp_net_namespace.o because: 'No space left on device' 1 /tmp/ccLTO4eP.s: Fatal error: can't close net/core/.tmp_net_namespace.o: No space left on device 1 /tmp/ccBFtQW6.s: Fatal error: can't write 52 bytes to section .text of net/ceph/.tmp_armor.o because: 'No space left on device' 1 /tmp/ccBFtQW6.s: Fatal error: can't close net/ceph/.tmp_armor.o: No space left on device 1 ../sound/pci/echoaudio/gina20.c:105:0: fatal error: error writing to /tmp/ccJqjV92.s: No space left on device 1 ../sound/pci/echoaudio/darla20.c:101:0: fatal error: error writing to /tmp/cc7JDCnr.s: No space left on device 1 ../sound/pci/ctxfi/cttimer.c:442:1: fatal error: error writing to /tmp/ccZMY7e7.s: No space left on device 1 ../sound/pci/ctxfi/ctpcm.c:488:1: fatal error: error writing to /tmp/ccSTcejh.s: No space left on device 1 ../sound/pci/ctxfi/ctimap.c:111:1: fatal error: error writing to /tmp/ccyRwHAu.s: No space left on device 1 ../sound/pci/ctxfi/cthw20k2.c:2360:1: fatal error: error writing to /tmp/ccCacZcI.s: No space left on device 1 ../sound/pci/ctxfi/cthw20k1.c:2294:1: fatal error: error writing to /tmp/cczhbKBK.s: No space left on device 1 ../sound/pci/cs5535audio/cs5535audio.c:416:1: fatal error: error writing to /tmp/ccEHCHSs.s: No space left on device 1 ../sound/pci/cs46xx/dsp_spos.c:2049:1: fatal error: error writing to /tmp/cc9HVEn5.s: No space left on device 1 ../sound/pci/cs46xx/cs46xx_lib.c:4051:1: fatal error: error writing to /tmp/ccI6NMD6.s: No space left on device 1 ../sound/pci/ca0106/ca_midi.c:315:1: fatal error: error writing to /tmp/ccCbCHvb.s: No space left on device 1 ../sound/pci/ca0106/ca0106_proc.c:453:1: fatal error: error writing to /tmp/cc0hgTFW.s: No space left on device 1 ../sound/pci/ca0106/ca0106_mixer.c:931:1: fatal error: error writing to /tmp/ccRobsnv.s: No space left on device 1 ../sound/pci/ca0106/ca0106_main.c:1972:1: fatal error: error writing to /tmp/ccdYa3X8.s: No space left on device 1 ../net/dccp/timer.c:271:1: fatal error: error writing to /tmp/cc5lwnP6.s: No space left on device 1 ../net/dccp/sysctl.c:118:1: fatal error: opening dependency file net/dccp/.sysctl.o.d: No such file or directory 1 ../net/dccp/qpolicy.c:137:1: fatal error: error writing to /tmp/cctNXU4d.s: No space left on device 1 ../net/dccp/proto.c:1256:1: fatal error: opening dependency file net/dccp/.proto.o.d: No such file or directory 1 ../net/dccp/probe.c:203:1: fatal error: opening dependency file net/dccp/.probe.o.d: No such file or directory 1 ../net/dccp/output.c:703:1: fatal error: opening dependency file net/dccp/.output.o.d: No such file or directory 1 ../net/dccp/options.c:609:1: fatal error: opening dependency file net/dccp/.options.o.d: No such file or directory 1 ../net/dccp/ipv6.c:1132:1: fatal error: opening dependency file net/dccp/.ipv6.o.d: No such file or directory 1 ../net/dccp/ipv4.c:1072:1: fatal error: opening dependency file net/dccp/.ipv4.o.d: No such file or directory 1 ../net/dccp/input.c:732:1: fatal error: opening dependency file net/dccp/.input.o.d: No such file or directory 1 ../net/dccp/feat.c:1561:1: fatal error: opening dependency file net/dccp/.feat.o.d: No such file or directory 1 ../net/dccp/diag.c:88:1: fatal error: opening dependency file net/dccp/.diag.o.d: No such file or directory 1 ../net/dccp/ccids/lib/tfrc_equation.c:705:1: fatal error: error writing to /tmp/ccy4CcBS.s: No space left on device 1 ../net/dccp/ccids/lib/tfrc.c:45:1: fatal error: opening dependency file net/dccp/ccids/lib/.tfrc.o.d: No such file or directory 1 ../net/dccp/ccids/lib/packet_history.c:449:1: fatal error: opening dependency file net/dccp/ccids/lib/.packet_history.o.d: No such file or directory 1 ../net/dccp/ccids/lib/loss_interval.c:185:1: fatal error: opening dependency file net/dccp/ccids/lib/.loss_interval.o.d: No such file or directory 1 ../net/dccp/ccids/ccid3.c:869:1: fatal error: error writing to /tmp/ccvqAB6V.s: No space left on device 1 ../net/dccp/ccids/ccid2.c:783:1: fatal error: error writing to /tmp/ccBb8PfS.s: No space left on device 1 ../net/dccp/ccid.c:222:1: fatal error: opening dependency file net/dccp/.ccid.o.d: No such file or directory 1 ../net/dccp/ackvec.c:405:1: fatal error: opening dependency file net/dccp/.ackvec.o.d: No such file or directory 1 ../net/dcb/dcbnl.c:1945:1: fatal error: error writing to /tmp/ccFdhLmn.s: No space left on device 1 ../net/dcb/dcbevent.c:41:1: fatal error: error writing to /tmp/ccPjuLs1.s: No space left on device 1 ../net/core/rtnetlink.c:4147:1: fatal error: error writing to /tmp/cc1hijle.s: No space left on device 1 ../net/core/neighbour.c:3223:1: fatal error: error writing to /tmp/cc9syBEz.s: No space left on device 1 ../net/core/flow_dissector.c:1048:1: fatal error: error writing to /tmp/cc3WGO8d.s: No space left on device 1 ../net/core/ethtool.c:2796:1: fatal error: error writing to /tmp/cc6bIDFM.s: No space left on device 1 ../net/core/dev.c:8414:1: fatal error: error writing to /tmp/ccVveDbZ.s: No space left on device 1 ../net/ceph/auth_x.c:821:1: fatal error: error writing to /tmp/cc8EPxjH.s: No space left on device 1 ../net/ceph/auth_none.c:143:1: fatal error: error writing to /tmp/cc0qHpib.s: No space left on device 1 ../include/linux/export.h:63:22: fatal error: opening dependency file net/dccp/.minisocks.o.d: No such file or directory 1 ../include/linux/export.h:63:22: fatal error: error writing to /tmp/ccsX5XkG.s: No space left on device 1 ../include/linux/export.h:63:22: fatal error: error closing /tmp/cc1l4q6r.s: No space left on device 1 ../fs/f2fs/super.c:2246:1: fatal error: error writing to /tmp/cclvCDv1.s: No space left on device 1 ../fs/f2fs/segment.c:2806:1: fatal error: error writing to /tmp/ccvqV2P2.s: No space left on device 1 ../fs/f2fs/node.c:2462:1: fatal error: error writing to /tmp/ccTEJYcA.s: No space left on device 1 ../fs/f2fs/namei.c:1123:1: fatal error: error writing to /tmp/ccnggT4u.s: No space left on device 1 ../fs/f2fs/hash.c:103:1: fatal error: error writing to /tmp/cc5Fjb1Y.s: No space left on device 1 ../fs/f2fs/data.c:2021:1: fatal error: error writing to /tmp/ccdfN7hS.s: No space left on device 1 ../fs/f2fs/checkpoint.c:1335:1: fatal error: error writing to /tmp/ccDdzn6r.s: No space left on device 1 ../fs/ext4/symlink.c:101:1: fatal error: error writing to /tmp/ccfkeaMd.s: No space left on device 1 ../fs/ext4/super.c:5696:1: fatal error: error writing to /tmp/ccjE7fHG.s: No space left on device 1 ../fs/ext4/resize.c:2018:1: fatal error: error writing to /tmp/ccBkGmqO.s: No space left on device 1 ../fs/ext4/namei.c:3898:1: fatal error: error writing to /tmp/cc2Q79HI.s: No space left on device 1 ../fs/ext4/inode.c:5947:1: fatal error: error writing to /tmp/cckfiULj.s: No space left on device 1 ../fs/ext4/hash.c:207:1: fatal error: error writing to /tmp/ccw4LG5o.s: No space left on device 1 ../fs/ext4/extents.c:5941:1: fatal error: error writing to /tmp/ccosvK2q.s: No space left on device 1 ../drivers/atm/nicstar.c:2751:1: fatal error: error writing to /tmp/ccdQuD2B.s: No space left on device 1 ../drivers/atm/idt77252.c:3804:1: fatal error: error writing to /tmp/cczxaeWr.s: No space left on device 1 ../drivers/atm/fore200e.c:3177:1: fatal error: error writing to /tmp/ccpPMopa.s: No space left on device 1 ../drivers/atm/eni.c:2341:1: fatal error: error writing to /tmp/ccTHBoQp.s: No space left on device 1 ../drivers/ata/pata_triflex.c:248:1: fatal error: error writing to /tmp/ccTar8Ro.s: No space left on device 1 ../drivers/ata/pata_sl82c105.c:380:1: fatal error: error closing /tmp/ccGwtXdY.s: No space left on device 1 ../drivers/ata/pata_rz1000.c:148:1: fatal error: error writing to /tmp/cc72E6rN.s: No space left on device 1 ../drivers/ata/pata_opti.c:199:1: fatal error: error writing to /tmp/ccaz7mHj.s: No space left on device 1 ../drivers/ata/pata_legacy.c:1276:1: fatal error: error writing to /tmp/cclEdxAJ.s: No space left on device =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : UNKNOWN, 73 errors, 0 warnings, 0 section mismatches Errors: /tmp/ccLTO4eP.s: Fatal error: can't write 64 bytes to section .text of net/core/.tmp_net_namespace.o because: 'No space left on device' /tmp/ccLTO4eP.s: Fatal error: can't close net/core/.tmp_net_namespace.o: No space left on device ../include/linux/export.h:63:22: fatal error: error closing /tmp/cc1l4q6r.s: No space left on device ../drivers/ata/pata_triflex.c:248:1: fatal error: error writing to /tmp/ccTar8Ro.s: No space left on device ../sound/pci/ca0106/ca0106_main.c:1972:1: fatal error: error writing to /tmp/ccdYa3X8.s: No space left on device ../net/ceph/auth_none.c:143:1: fatal error: error writing to /tmp/cc0qHpib.s: No space left on device ../sound/pci/ca0106/ca0106_mixer.c:931:1: fatal error: error writing to /tmp/ccRobsnv.s: No space left on device /tmp/ccBFtQW6.s: Fatal error: can't write 52 bytes to section .text of net/ceph/.tmp_armor.o because: 'No space left on device' /tmp/ccBFtQW6.s: Fatal error: can't close net/ceph/.tmp_armor.o: No space left on device ../fs/f2fs/namei.c:1123:1: fatal error: error writing to /tmp/ccnggT4u.s: No space left on device ../sound/pci/ca0106/ca_midi.c:315:1: fatal error: error writing to /tmp/ccCbCHvb.s: No space left on device ../drivers/ata/pata_sl82c105.c:380:1: fatal error: error closing /tmp/ccGwtXdY.s: No space left on device ../fs/f2fs/hash.c:103:1: fatal error: error writing to /tmp/cc5Fjb1Y.s: No space left on device ../fs/ext4/inode.c:5947:1: fatal error: error writing to /tmp/cckfiULj.s: No space left on device ../sound/pci/ca0106/ca0106_proc.c:453:1: fatal error: error writing to /tmp/cc0hgTFW.s: No space left on device ../net/ceph/auth_x.c:821:1: fatal error: error writing to /tmp/cc8EPxjH.s: No space left on device ../net/core/flow_dissector.c:1048:1: fatal error: error writing to /tmp/cc3WGO8d.s: No space left on device ../drivers/ata/pata_opti.c:199:1: fatal error: error writing to /tmp/ccaz7mHj.s: No space left on device ../include/linux/export.h:63:22: fatal error: error writing to /tmp/ccsX5XkG.s: No space left on device ../sound/pci/cs46xx/cs46xx_lib.c:4051:1: fatal error: error writing to /tmp/ccI6NMD6.s: No space left on device ../fs/f2fs/super.c:2246:1: fatal error: error writing to /tmp/cclvCDv1.s: No space left on device ../drivers/ata/pata_rz1000.c:148:1: fatal error: error writing to /tmp/cc72E6rN.s: No space left on device ../sound/pci/cs46xx/dsp_spos.c:2049:1: fatal error: error writing to /tmp/cc9HVEn5.s: No space left on device ../fs/ext4/namei.c:3898:1: fatal error: error writing to /tmp/cc2Q79HI.s: No space left on device ../net/dcb/dcbnl.c:1945:1: fatal error: error writing to /tmp/ccFdhLmn.s: No space left on device ../sound/pci/cs5535audio/cs5535audio.c:416:1: fatal error: error writing to /tmp/ccEHCHSs.s: No space left on device ../net/dcb/dcbevent.c:41:1: fatal error: error writing to /tmp/ccPjuLs1.s: No space left on device ../drivers/ata/pata_legacy.c:1276:1: fatal error: error writing to /tmp/cclEdxAJ.s: No space left on device ../net/dccp/ccid.c:222:1: fatal error: opening dependency file net/dccp/.ccid.o.d: No such file or directory ../fs/f2fs/checkpoint.c:1335:1: fatal error: error writing to /tmp/ccDdzn6r.s: No space left on device ../net/core/dev.c:8414:1: fatal error: error writing to /tmp/ccVveDbZ.s: No space left on device ../net/dccp/feat.c:1561:1: fatal error: opening dependency file net/dccp/.feat.o.d: No such file or directory ../drivers/atm/nicstar.c:2751:1: fatal error: error writing to /tmp/ccdQuD2B.s: No space left on device ../net/dccp/input.c:732:1: fatal error: opening dependency file net/dccp/.input.o.d: No such file or directory ../sound/pci/ctxfi/ctpcm.c:488:1: fatal error: error writing to /tmp/ccSTcejh.s: No space left on device ../include/linux/export.h:63:22: fatal error: opening dependency file net/dccp/.minisocks.o.d: No such file or directory ../net/core/ethtool.c:2796:1: fatal error: error writing to /tmp/cc6bIDFM.s: No space left on device ../net/dccp/options.c:609:1: fatal error: opening dependency file net/dccp/.options.o.d: No such file or directory ../fs/f2fs/data.c:2021:1: fatal error: error writing to /tmp/ccdfN7hS.s: No space left on device ../net/dccp/output.c:703:1: fatal error: opening dependency file net/dccp/.output.o.d: No such file or directory ../net/dccp/proto.c:1256:1: fatal error: opening dependency file net/dccp/.proto.o.d: No such file or directory ../sound/pci/ctxfi/ctimap.c:111:1: fatal error: error writing to /tmp/ccyRwHAu.s: No space left on device ../fs/ext4/super.c:5696:1: fatal error: error writing to /tmp/ccjE7fHG.s: No space left on device ../net/dccp/timer.c:271:1: fatal error: error writing to /tmp/cc5lwnP6.s: No space left on device ../fs/ext4/symlink.c:101:1: fatal error: error writing to /tmp/ccfkeaMd.s: No space left on device ../sound/pci/ctxfi/cttimer.c:442:1: fatal error: error writing to /tmp/ccZMY7e7.s: No space left on device ../fs/ext4/hash.c:207:1: fatal error: error writing to /tmp/ccw4LG5o.s: No space left on device ../net/dccp/qpolicy.c:137:1: fatal error: error writing to /tmp/cctNXU4d.s: No space left on device ../fs/f2fs/node.c:2462:1: fatal error: error writing to /tmp/ccTEJYcA.s: No space left on device ../drivers/atm/fore200e.c:3177:1: fatal error: error writing to /tmp/ccpPMopa.s: No space left on device ../net/dccp/ccids/ccid2.c:783:1: fatal error: error writing to /tmp/ccBb8PfS.s: No space left on device ../sound/pci/ctxfi/cthw20k2.c:2360:1: fatal error: error writing to /tmp/ccCacZcI.s: No space left on device ../net/core/neighbour.c:3223:1: fatal error: error writing to /tmp/cc9syBEz.s: No space left on device ../fs/ext4/resize.c:2018:1: fatal error: error writing to /tmp/ccBkGmqO.s: No space left on device ../net/dccp/ackvec.c:405:1: fatal error: opening dependency file net/dccp/.ackvec.o.d: No such file or directory ../sound/pci/ctxfi/cthw20k1.c:2294:1: fatal error: error writing to /tmp/cczhbKBK.s: No space left on device ../net/dccp/ccids/ccid3.c:869:1: fatal error: error writing to /tmp/ccvqAB6V.s: No space left on device ../drivers/atm/eni.c:2341:1: fatal error: error writing to /tmp/ccTHBoQp.s: No space left on device ../fs/f2fs/segment.c:2806:1: fatal error: error writing to /tmp/ccvqV2P2.s: No space left on device ../net/dccp/ccids/lib/tfrc.c:45:1: fatal error: opening dependency file net/dccp/ccids/lib/.tfrc.o.d: No such file or directory ../sound/pci/echoaudio/darla20.c:101:0: fatal error: error writing to /tmp/cc7JDCnr.s: No space left on device ../net/dccp/ccids/lib/tfrc_equation.c:705:1: fatal error: error writing to /tmp/ccy4CcBS.s: No space left on device ../net/core/rtnetlink.c:4147:1: fatal error: error writing to /tmp/cc1hijle.s: No space left on device ../net/dccp/ccids/lib/packet_history.c:449:1: fatal error: opening dependency file net/dccp/ccids/lib/.packet_history.o.d: No such file or directory ../sound/pci/echoaudio/gina20.c:105:0: fatal error: error writing to /tmp/ccJqjV92.s: No space left on device ../drivers/atm/idt77252.c:3804:1: fatal error: error writing to /tmp/cczxaeWr.s: No space left on device ../net/dccp/ccids/lib/loss_interval.c:185:1: fatal error: opening dependency file net/dccp/ccids/lib/.loss_interval.o.d: No such file or directory ../fs/ext4/extents.c:5941:1: fatal error: error writing to /tmp/ccosvK2q.s: No space left on device ../net/dccp/sysctl.c:118:1: fatal error: opening dependency file net/dccp/.sysctl.o.d: No such file or directory ../net/dccp/ipv4.c:1072:1: fatal error: opening dependency file net/dccp/.ipv4.o.d: No such file or directory ../net/dccp/ipv6.c:1132:1: fatal error: opening dependency file net/dccp/.ipv6.o.d: No such file or directory ../net/dccp/diag.c:88:1: fatal error: opening dependency file net/dccp/.diag.o.d: No such file or directory ../net/dccp/probe.c:203:1: fatal error: opening dependency file net/dccp/.probe.o.d: No such file or directory ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-131-g6e0362b)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-131-g6e0362b Commit: 6e0362b3a8 Merge tag 'xfs-for-linux-4.10-rc5-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux Build Time: 101 min 11 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-122-g81aaeaa)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-122-g81aaeaa Commit: 81aaeaac46 Merge tag 'pci-v4.10-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci Build Time: 101 min 7 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

[PATCH v8 0/8] Add PWM and IIO timer drivers for STM32

by Benjamin Gaignard

version 8: - rebase on v4.10-rc4 - fix comments done by Thierry on PWM - reword "reg" parameter description - change kernel kernel in IIO ABI documentation version 7: - rebase on v4.10-rc2 - remove iio_device code from driver and keep only the trigger part version 6: - rename stm32-gptimer in stm32-timers. - change "st,stm32-gptimer" compatible to "st,stm32-timers". - modify "st,breakinput" parameter in pwm part. - split DT patch in 2 version 5: - fix comments done on version 4 - rebased on kernel 4.9-rc8 - change nodes names and re-order then by addresses version 4: - fix comments done on version 3 - don't use interrupts anymore in IIO timer - detect hardware capabilities at probe time to simplify binding version 3: - no change on mfd and pwm divers patches - add cross reference between bindings - change compatible to "st,stm32-timer-trigger" - fix attributes access rights - use string instead of int for master_mode and slave_mode - document device attributes in sysfs-bus-iio-timer-stm32 - update DT with the new compatible version 2: - keep only one compatible per driver - use DT parameters to describe hardware block configuration: - pwm channels, complementary output, counter size, break input - triggers accepted and create by IIO timers - change DT to limite use of reference to the node - interrupt is now in IIO timer driver - rename stm32-mfd-timer to stm32-timers (for general purpose timer) The following patches enable PWM and IIO Timer features for STM32 platforms. Those two features are mixed into the registers of the same hardware block (named general purpose timer) which lead to introduce a multifunctions driver on the top of them to be able to share the registers. In STM32f4 14 instances of timer hardware block exist, even if they all have the same register mapping they could have a different number of pwm channels and/or different triggers capabilities. We use various parameters in DT to describe the differences between hardware blocks The MFD (stm32-timers.c) takes care of clock and register mapping by using regmap. stm32_timers structure is provided to its sub-node to share those information. PWM driver is implemented into pwm-stm32.c. Depending of the instance we may have up to 4 channels, sometime with complementary outputs or 32 bits counter instead of 16 bits. Some hardware blocks may also have a break input function which allows to stop pwm depending of a level, defined in devicetree, on an external pin. IIO timer driver (stm32-timer-trigger.c and stm32-timer-trigger.h) define a list of hardware triggers usable by hardware blocks like ADC, DAC or other timers. The matrix of possible connections between blocks is quite complex so we use trigger names and is_stm32_iio_timer_trigger() function to be sure that triggers are valid and configure the IPs. At run time IIO timer hardware blocks can configure (through "master_mode" IIO device attribute) which internal signal (counter enable, reset, comparison block, etc...) is used to generate the trigger. Benjamin Gaignard (8): MFD: add bindings for STM32 Timers driver MFD: add STM32 Timers driver PWM: add pwm-stm32 DT bindings PWM: add PWM driver for STM32 plaftorm IIO: add bindings for STM32 timer trigger driver IIO: add STM32 timer trigger driver ARM: dts: stm32: add Timers driver for stm32f429 MCU ARM: dts: stm32: Enable pwm1 and pwm3 for stm32f469-disco .../ABI/testing/sysfs-bus-iio-timer-stm32 | 29 ++ .../bindings/iio/timer/stm32-timer-trigger.txt | 23 ++ .../devicetree/bindings/mfd/stm32-timers.txt | 46 +++ .../devicetree/bindings/pwm/pwm-stm32.txt | 35 ++ arch/arm/boot/dts/stm32f429.dtsi | 275 ++++++++++++++ arch/arm/boot/dts/stm32f469-disco.dts | 28 ++ drivers/iio/trigger/Kconfig | 9 + drivers/iio/trigger/Makefile | 1 + drivers/iio/trigger/stm32-timer-trigger.c | 342 ++++++++++++++++++ drivers/mfd/Kconfig | 11 + drivers/mfd/Makefile | 2 + drivers/mfd/stm32-timers.c | 80 +++++ drivers/pwm/Kconfig | 9 + drivers/pwm/Makefile | 1 + drivers/pwm/pwm-stm32.c | 398 +++++++++++++++++++++ include/linux/iio/timer/stm32-timer-trigger.h | 62 ++++ include/linux/mfd/stm32-timers.h | 71 ++++ 17 files changed, 1422 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 create mode 100644 Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt create mode 100644 Documentation/devicetree/bindings/mfd/stm32-timers.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-stm32.txt create mode 100644 drivers/iio/trigger/stm32-timer-trigger.c create mode 100644 drivers/mfd/stm32-timers.c create mode 100644 drivers/pwm/pwm-stm32.c create mode 100644 include/linux/iio/timer/stm32-timer-trigger.h create mode 100644 include/linux/mfd/stm32-timers.h -- 1.9.1

9 years, 4 months

4
14
0 0

[GIT PULL] [lsk-v3.18-android] linaro-android v3.18 topic branch updates

by Amit Pundir

Hi Alex, Mark, Please consider following linaro-android pull request for "linux-linaro-lsk-v3.18-android" LSK branch. Boot tested on Qemu + Android M. KernelCI build job: https://kernelci.org/build/linaro-android/kernel/v3.18-6360-g6bf100b6b6dc/ Regards, Amit Pundir The following changes since commit cb0774d2a88080ff191e8f2cfca7a53239d4fdc7: Merge branch 'linux-linaro-lsk-v3.18' into linux-linaro-lsk-v3.18-android (2017-01-11 09:59:22 +0800) are available in the git repository at: git://android.git.linaro.org/kernel/linaro-android lsk-v3.18-android for you to fetch changes up to 6bf100b6b6dc30730db6253239cd5bd6243f0461: DEBUG: sched/fair: Fix sched_load_avg_cpu events for task_groups (2017-01-16 16:11:00 +0530) ---------------------------------------------------------------- Brendan Jackman (2): DEBUG: sched/fair: Fix missing sched_load_avg_cpu events DEBUG: sched/fair: Fix sched_load_avg_cpu events for task_groups Catalin Marinas (6): BACKPORT: arm64: Factor out PAN enabling/disabling into separate uaccess_* macros BACKPORT: arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1 BACKPORT: arm64: Disable TTBR0_EL1 during normal kernel execution UPSTREAM: arm64: Handle faults caused by inadvertent user access with PAN enabled UPSTREAM: arm64: xen: Enable user access before a privcmd hvc call UPSTREAM: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN Daniel Rosenberg (1): ANDROID: mnt: remount should propagate to slaves of slaves Eric Biggers (1): net: socket: don't set sk_uid to garbage value in ->setattr() Eric Dumazet (1): UPSTREAM: net: avoid signed overflows for SO_{SND|RCV}BUFFORCE Guillaume Nault (1): UPSTREAM: l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind() Marc Zyngier (1): UPSTREAM: arm64: Disable PAN on uaccess_enable() Mark Rutland (1): UPSTREAM: arm64: alternative: add auto-nop infrastructure Sami Tolvanen (7): Revert "FROMLIST: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN" Revert "FROMLIST: arm64: xen: Enable user access before a privcmd hvc call" Revert "FROMLIST: arm64: Handle faults caused by inadvertent user access with PAN enabled" Revert "FROMLIST: arm64: Disable TTBR0_EL1 during normal kernel execution" Revert "FROMLIST: arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1" Revert "FROMLIST: arm64: Factor out PAN enabling/disabling into separate uaccess_* macros" ANDROID: configs: CONFIG_ARM64_SW_TTBR0_PAN=y Will Deacon (1): BACKPORT: arm64: barriers: introduce nops and __nops macros for NOP sequences android/configs/android-recommended.cfg | 1 + arch/arm64/Kconfig | 2 +- arch/arm64/include/asm/alternative.h | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++----------------- arch/arm64/include/asm/assembler.h | 9 +++++++++ arch/arm64/include/asm/barrier.h | 3 +++ arch/arm64/include/asm/efi.h | 1 + arch/arm64/include/asm/futex.h | 3 --- arch/arm64/include/asm/kernel-pgtable.h | 1 + arch/arm64/include/asm/mmu_context.h | 6 ++++-- arch/arm64/include/asm/ptrace.h | 2 -- arch/arm64/include/asm/thread_info.h | 4 ++-- arch/arm64/include/asm/uaccess.h | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------- arch/arm64/kernel/armv8_deprecated.c | 1 - arch/arm64/kernel/asm-offsets.c | 6 +++--- arch/arm64/kernel/efi.c | 1 - arch/arm64/kernel/entry.S | 19 +++++++------------ arch/arm64/lib/clear_user.S | 3 --- arch/arm64/lib/copy_from_user.S | 3 --- arch/arm64/lib/copy_in_user.S | 3 --- arch/arm64/lib/copy_to_user.S | 3 --- arch/arm64/mm/cache.S | 3 +++ arch/arm64/mm/fault.c | 8 ++++---- arch/arm64/xen/hypercall.S | 8 ++------ fs/pnode.c | 27 +++++++++++++++++++++------ fs/pnode.h | 2 +- kernel/sched/fair.c | 5 ++++- net/core/sock.c | 4 ++-- net/l2tp/l2tp_ip.c | 5 +++-- net/l2tp/l2tp_ip6.c | 5 +++-- net/socket.c | 2 +- 30 files changed, 187 insertions(+), 132 deletions(-)

9 years, 4 months

2
2
0 0

[GIT PULL] [lsk-v4.1-android] linaro-android v4.1 topic branch updates

by Amit Pundir

Hi Alex, Mark, Please consider following linaro-android pull request for "linux-linaro-lsk-v4.1-android" LSK branch. Boot tested on Qemu + Android M. KernelCI build job: https://kernelci.org/build/linaro-android/kernel/v4.1-5317-g65117109f634/ Backlog: Again, for the record, here is a list of aosp/android-4.1 patches dropped from lsk-4.1-android topic branch. "arm64: User Access Override" feature and dependent patches from aosp/android-4.1 are dropped due to non-trivial merge errors including a "#define" conflict in one of arm64:UAO patches which might have made that feature unusable. BACKPORT: arm64: kernel: Add support for User Access Override UPSTREAM: arm64: cpufeature: Test 'matches' pointer to find the end of the list BACKPORT: arm64: kernel: Don't toggle PAN on systems with UAO UPSTREAM: arm64: Remove the get_thread_info() function UPSTREAM: arm64: fix dump_instr when PAN and UAO are in use UPSTREAM: arm64: add macro to extract ESR_ELx.EC UPSTREAM: arm64: kill ESR_LNX_EXEC BACKPORT: arm64: kernel: Save and restore UAO and addr_limit on exception entry BACKPORT: arm64: Handle el1 synchronous instruction aborts cleanly BACKPORT: arm64: Factor out PAN enabling/disabling into separate uaccess_* macros BACKPORT: arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1 BACKPORT: arm64: Disable TTBR0_EL1 during normal kernel execution UPSTREAM: arm64: Handle faults caused by inadvertent user access with PAN enabled UPSTREAM: arm64: xen: Enable user access before a privcmd hvc call UPSTREAM: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN UPSTREAM: arm64: Disable PAN on uaccess_enable() ANDROID: configs: CONFIG_ARM64_SW_TTBR0_PAN=y Regards, Amit Pundir The following changes since commit 8b496701188f07a1c4821d833337e4a0998191b9: Merge branch 'lsk-v4.1-android' of git://android.git.linaro.org/kernel/linaro-android into linux-linaro-lsk-v4.1-android (2017-01-03 17:57:57 +0800) are available in the git repository at: git://android.git.linaro.org/kernel/linaro-android lsk-v4.1-android for you to fetch changes up to 65117109f6344fa46542f85844bc292842116192: ANDROID: sdcardfs: Propagate dentry down to inode_change_ok() (2017-01-16 15:54:02 +0530) ---------------------------------------------------------------- Amit Pundir (1): ANDROID: sdcardfs: Propagate dentry down to inode_change_ok() Eric Biggers (1): net: socket: don't set sk_uid to garbage value in ->setattr() Eric Dumazet (1): UPSTREAM: net: avoid signed overflows for SO_{SND|RCV}BUFFORCE Guillaume Nault (1): UPSTREAM: l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind() Mark Rutland (1): UPSTREAM: arm64: alternative: add auto-nop infrastructure Sami Tolvanen (2): Revert "FROMLIST: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN" Revert "FROMLIST: arm64: xen: Enable user access before a privcmd hvc call" Will Deacon (1): BACKPORT: arm64: barriers: introduce nops and __nops macros for NOP sequences arch/arm64/Kconfig | 8 -------- arch/arm64/include/asm/alternative.h | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------- arch/arm64/include/asm/assembler.h | 9 +++++++++ arch/arm64/include/asm/barrier.h | 3 +++ arch/arm64/xen/hypercall.S | 19 ------------------- fs/sdcardfs/inode.c | 4 ++-- net/core/sock.c | 4 ++-- net/l2tp/l2tp_ip.c | 5 +++-- net/l2tp/l2tp_ip6.c | 5 +++-- net/socket.c | 2 +- 10 files changed, 77 insertions(+), 53 deletions(-)

9 years, 4 months

2
1
0 0

[GIT PULL] [lsk-v4.4-android] linaro-android v4.4 topic branch updates

by Amit Pundir

Hi Alex, Mark, Please consider following linaro-android pull request for "linux-linaro-lsk-v4.4-android" LSK branch. Boot tested on Qemu + Android M. KernelCI build job: https://kernelci.org/build/linaro-android/kernel/v4.4-4991-gee620ddd6581/ Regards, Amit Pundir The following changes since commit 6e3f9088f8cc53fcd3e1fbdcbe5b8498c225f566: Merge branch 'linux-linaro-lsk-v4.4' into linux-linaro-lsk-v4.4-android (2017-01-16 12:01:30 +0800) are available in the git repository at: git://android.git.linaro.org/kernel/linaro-android lsk-v4.4-android for you to fetch changes up to ee620ddd6581cf9779d27677f6f0f11e3f939a8c: DEBUG: sched/fair: Fix sched_load_avg_cpu events for task_groups (2017-01-16 15:03:08 +0530) ---------------------------------------------------------------- Amit Pundir (2): ANDROID: sched/walt: fix build failure if FAIR_GROUP_SCHED=n Revert "FROMLIST: arm64: Handle faults caused by inadvertent user access with PAN enabled" Brendan Jackman (2): DEBUG: sched/fair: Fix missing sched_load_avg_cpu events DEBUG: sched/fair: Fix sched_load_avg_cpu events for task_groups Catalin Marinas (7): BACKPORT: arm64: Factor out PAN enabling/disabling into separate uaccess_* macros BACKPORT: arm64: Factor out TTBR0_EL1 post-update workaround into a specific asm macro BACKPORT: arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1 BACKPORT: arm64: Disable TTBR0_EL1 during normal kernel execution UPSTREAM: arm64: Handle faults caused by inadvertent user access with PAN enabled UPSTREAM: arm64: xen: Enable user access before a privcmd hvc call UPSTREAM: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN Eric Biggers (1): net: socket: don't set sk_uid to garbage value in ->setattr() Marc Zyngier (1): UPSTREAM: arm64: Disable PAN on uaccess_enable() Mark Rutland (1): UPSTREAM: arm64: alternative: add auto-nop infrastructure Sami Tolvanen (7): Revert "FROMLIST: arm64: Enable CONFIG_ARM64_SW_TTBR0_PAN" Revert "FROMLIST: arm64: xen: Enable user access before a privcmd hvc call" Revert "FROMLIST: arm64: Disable TTBR0_EL1 during normal kernel execution" Revert "FROMLIST: arm64: Introduce uaccess_{disable,enable} functionality based on TTBR0_EL1" Revert "FROMLIST: arm64: Factor out TTBR0_EL1 post-update workaround into a specific asm macro" Revert "FROMLIST: arm64: Factor out PAN enabling/disabling into separate uaccess_* macros" ANDROID: configs: CONFIG_ARM64_SW_TTBR0_PAN=y Will Deacon (1): UPSTREAM: arm64: barriers: introduce nops and __nops macros for NOP sequences android/configs/android-recommended.cfg | 1 + arch/arm64/Kconfig | 2 +- arch/arm64/include/asm/alternative.h | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++----------------- arch/arm64/include/asm/assembler.h | 17 +++++++++++------ arch/arm64/include/asm/barrier.h | 3 +++ arch/arm64/include/asm/futex.h | 3 --- arch/arm64/include/asm/mmu_context.h | 6 ++++-- arch/arm64/include/asm/ptrace.h | 2 -- arch/arm64/include/asm/thread_info.h | 2 +- arch/arm64/include/asm/uaccess.h | 108 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------- arch/arm64/kernel/armv8_deprecated.c | 1 - arch/arm64/kernel/asm-offsets.c | 6 +++--- arch/arm64/kernel/entry.S | 18 +++++++----------- arch/arm64/lib/clear_user.S | 3 --- arch/arm64/lib/copy_from_user.S | 3 --- arch/arm64/lib/copy_in_user.S | 3 --- arch/arm64/lib/copy_to_user.S | 3 --- arch/arm64/mm/cache.S | 6 +++++- arch/arm64/mm/fault.c | 8 ++++---- arch/arm64/xen/hypercall.S | 8 ++------ init/Kconfig | 1 + kernel/sched/fair.c | 5 ++++- net/socket.c | 2 +- 23 files changed, 159 insertions(+), 122 deletions(-)

9 years, 4 months

2
1
0 0

[RFC simple allocator v1 0/2] Simple allocator

by Benjamin Gaignard

Hi all, before sending this RFC to a larger audience I would like to get our opinion about it. Please feel very free to comment it, thanks ! The goal of this RFC is to understand if a common ioctl for specific memory regions allocations is needed/welcome. Obviously it will not replace allocation done in linux kernel frameworks like v4l2 or dmr/kms, but offer an alternative when you don't want/need to use them for buffer allocation. "Unix Device Memory Allocator" project [1] wants to create a userland library which may allow to select, depending of the devices constraint, the best back-end for allocation. With this RFC I would to propose to have common ioctl for a maximum of allocator to avoid to duplicated back-end for this library. Since the beginning it is a problem to allocate contiguous memory (CMA) without using v4l2 or drm/kms so the first allocator available in this RFC use CMA memory. An other question is: do we have others memory regions that could be interested by this new framework ? I have in mind that some title memory regions could use it or replace ION heaps (system, carveout etc...). Maybe it only solve CMA allocation issue, in this case no need to create a common ioctl, a custom should be enough. Maybe the first thing to do is to change the name and the location of this module, suggestions are welcome. [1] https://github.com/cubanismo/allocator Benjamin Gaignard (2): Create Simple Allocator module add CMA simple allocator module drivers/Kconfig | 2 + drivers/Makefile | 1 + drivers/simpleallocator/Kconfig | 17 +++ drivers/simpleallocator/Makefile | 2 + drivers/simpleallocator/simple-allocator-cma.c | 163 +++++++++++++++++++++++ drivers/simpleallocator/simple-allocator-priv.h | 27 ++++ drivers/simpleallocator/simple-allocator.c | 167 ++++++++++++++++++++++++ include/uapi/linux/simple-allocator.h | 35 +++++ 8 files changed, 414 insertions(+) create mode 100644 drivers/simpleallocator/Kconfig create mode 100644 drivers/simpleallocator/Makefile create mode 100644 drivers/simpleallocator/simple-allocator-cma.c create mode 100644 drivers/simpleallocator/simple-allocator-priv.h create mode 100644 drivers/simpleallocator/simple-allocator.c create mode 100644 include/uapi/linux/simple-allocator.h -- 1.9.1

9 years, 4 months

2
8
0 0

next-20170119 build: 0 failures 1 warnings (next-20170119)

by Build bot for Mark Brown

Tree/Branch: next-20170119 Git describe: next-20170119 Commit: fb6271277d Add linux-next specific files for 20170119 Build Time: 104 min 32 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm64-allmodconfig 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 2 ../drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c:546:6: warning: unused variable 'ncv' [-Wunused-variable] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c:546:6: warning: unused variable 'ncv' [-Wunused-variable] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c:546:6: warning: unused variable 'ncv' [-Wunused-variable] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-108-gfb1d8e0)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-108-gfb1d8e0 Commit: fb1d8e0e2c Merge tag 'upstream-4.10-rc5' of git://git.infradead.org/linux-ubifs Build Time: 101 min 35 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-101-gfa19a76)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-101-gfa19a76 Commit: fa19a769f8 Merge branch 'fixes' of git://git.armlinux.org.uk/~rmk/linux-arm Build Time: 108 min 12 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

[PATCH v7 0/8] Add PWM and IIO timer drivers for STM32

by Benjamin Gaignard

version 7: - rebase on v4.10-rc2 - remove iio_device code from driver and keep only the trigger part version 6: - rename stm32-gptimer in stm32-timers. - change "st,stm32-gptimer" compatible to "st,stm32-timers". - modify "st,breakinput" parameter in pwm part. - split DT patch in 2 version 5: - fix comments done on version 4 - rebased on kernel 4.9-rc8 - change nodes names and re-order then by addresses version 4: - fix comments done on version 3 - don't use interrupts anymore in IIO timer - detect hardware capabilities at probe time to simplify binding version 3: - no change on mfd and pwm divers patches - add cross reference between bindings - change compatible to "st,stm32-timer-trigger" - fix attributes access rights - use string instead of int for master_mode and slave_mode - document device attributes in sysfs-bus-iio-timer-stm32 - update DT with the new compatible version 2: - keep only one compatible per driver - use DT parameters to describe hardware block configuration: - pwm channels, complementary output, counter size, break input - triggers accepted and create by IIO timers - change DT to limite use of reference to the node - interrupt is now in IIO timer driver - rename stm32-mfd-timer to stm32-timers (for general purpose timer) The following patches enable PWM and IIO Timer features for STM32 platforms. Those two features are mixed into the registers of the same hardware block (named general purpose timer) which lead to introduce a multifunctions driver on the top of them to be able to share the registers. In STM32f4 14 instances of timer hardware block exist, even if they all have the same register mapping they could have a different number of pwm channels and/or different triggers capabilities. We use various parameters in DT to describe the differences between hardware blocks The MFD (stm32-timers.c) takes care of clock and register mapping by using regmap. stm32_timers structure is provided to its sub-node to share those information. PWM driver is implemented into pwm-stm32.c. Depending of the instance we may have up to 4 channels, sometime with complementary outputs or 32 bits counter instead of 16 bits. Some hardware blocks may also have a break input function which allows to stop pwm depending of a level, defined in devicetree, on an external pin. IIO timer driver (stm32-timer-trigger.c and stm32-timer-trigger.h) define a list of hardware triggers usable by hardware blocks like ADC, DAC or other timers. The matrix of possible connections between blocks is quite complex so we use trigger names and is_stm32_iio_timer_trigger() function to be sure that triggers are valid and configure the IPs. At run time IIO timer hardware blocks can configure (through "master_mode" IIO device attribute) which internal signal (counter enable, reset, comparison block, etc...) is used to generate the trigger. Benjamin Gaignard (8): MFD: add bindings for STM32 Timers driver MFD: add STM32 Timers driver PWM: add pwm-stm32 DT bindings PWM: add PWM driver for STM32 plaftorm IIO: add bindings for STM32 timer trigger driver IIO: add STM32 timer trigger driver ARM: dts: stm32: add Timers driver for stm32f429 MCU ARM: dts: stm32: Enable pwm1 and pwm3 for stm32f469-disco .../ABI/testing/sysfs-bus-iio-timer-stm32 | 29 ++ .../bindings/iio/timer/stm32-timer-trigger.txt | 23 ++ .../devicetree/bindings/mfd/stm32-timers.txt | 46 +++ .../devicetree/bindings/pwm/pwm-stm32.txt | 33 ++ arch/arm/boot/dts/stm32f429.dtsi | 275 +++++++++++++ arch/arm/boot/dts/stm32f469-disco.dts | 28 ++ drivers/iio/Kconfig | 1 - drivers/iio/trigger/Kconfig | 10 + drivers/iio/trigger/Makefile | 1 + drivers/iio/trigger/stm32-timer-trigger.c | 340 ++++++++++++++++ drivers/mfd/Kconfig | 11 + drivers/mfd/Makefile | 2 + drivers/mfd/stm32-timers.c | 80 ++++ drivers/pwm/Kconfig | 9 + drivers/pwm/Makefile | 1 + drivers/pwm/pwm-stm32.c | 434 +++++++++++++++++++++ include/linux/iio/timer/stm32-timer-trigger.h | 62 +++ include/linux/mfd/stm32-timers.h | 71 ++++ 18 files changed, 1455 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-timer-stm32 create mode 100644 Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt create mode 100644 Documentation/devicetree/bindings/mfd/stm32-timers.txt create mode 100644 Documentation/devicetree/bindings/pwm/pwm-stm32.txt create mode 100644 drivers/iio/trigger/stm32-timer-trigger.c create mode 100644 drivers/mfd/stm32-timers.c create mode 100644 drivers/pwm/pwm-stm32.c create mode 100644 include/linux/iio/timer/stm32-timer-trigger.h create mode 100644 include/linux/mfd/stm32-timers.h -- 1.9.1

9 years, 4 months

5
27
0 0

[RFC PATCH 0/3] Remove some dummy set_power callbacks

by Baolin Wang

In future we plan to introduce USB charger to set PMIC current drawn from USB configuration, instead of using set_power callback in phy driver. Moreover in these 3 phy drivers, the set_power callback did not implement anything to set PMIC current, thus we should remove them. Baolin Wang (3): usb: phy: ab8500: Remove the set_power callback usb: phy: msm: Remove the set_power callback usb: phy: fsl: Remove the set_power callback drivers/usb/phy/phy-ab8500-usb.c | 20 -------------------- drivers/usb/phy/phy-fsl-usb.c | 12 ------------ drivers/usb/phy/phy-msm-usb.c | 18 ------------------ 3 files changed, 50 deletions(-) -- 1.7.9.5

9 years, 4 months

1
3
0 0

next-20170118 build: 0 failures 0 warnings (next-20170118)

by Build bot for Mark Brown

Tree/Branch: next-20170118 Git describe: next-20170118 Commit: 8fd170ca36 Add linux-next specific files for 20170118 Build Time: 105 min 43 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-80-g0aa0313)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-80-g0aa0313 Commit: 0aa0313f9d Merge tag 'modules-for-v4.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux Build Time: 106 min 29 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 0 warnings (v4.10-rc4-78-g4b19a9e)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-78-g4b19a9e Commit: 4b19a9e20b Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Build Time: 102 min 3 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc4-25-g7e84b30)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-25-g7e84b30 Commit: 7e84b30355 Merge tag 'mmc-v4.10-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc Build Time: 105 min 13 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

next-20170117 build: 0 failures 3 warnings (next-20170117)

by Build bot for Mark Brown

Tree/Branch: next-20170117 Git describe: next-20170117 Commit: a65f0161f4 Add linux-next specific files for 20170117 Build Time: 101 min 43 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 2 warnings 0 mismatches : arm64-allmodconfig 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 3 1 ../drivers/rtc/rtc-stm32.c:673:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] 1 ../drivers/rtc/rtc-stm32.c:651:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] 1 ../drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../drivers/rtc/rtc-stm32.c:651:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] ../drivers/rtc/rtc-stm32.c:673:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc4-12-g5cf7a0f)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-12-g5cf7a0f Commit: 5cf7a0f344 Merge tag 'nfs-for-4.10-3' of git://git.linux-nfs.org/projects/trondmy/linux-nfs Build Time: 104 min 13 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc4-5-g2eabb8b)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc4-5-g2eabb8b Commit: 2eabb8b8d6 Merge tag 'nfsd-4.10-1' of git://linux-nfs.org/~bfields/linux Build Time: 105 min 6 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

next-20170116 build: 0 failures 4 warnings (next-20170116)

by Build bot for Mark Brown

Tree/Branch: next-20170116 Git describe: next-20170116 Commit: 38e4a8f0d6 Add linux-next specific files for 20170116 Build Time: 182 min 44 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 4 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 2 warnings 0 mismatches : arm64-allmodconfig 2 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 4 1 ../drivers/rtc/rtc-stm32.c:673:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] 1 ../drivers/rtc/rtc-stm32.c:651:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] 1 ../drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/net/ethernet/mellanox/mlx5/en/tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../drivers/rtc/rtc-stm32.c:651:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] ../drivers/rtc/rtc-stm32.c:673:51: warning: large integer implicitly truncated to unsigned type [-Woverflow] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/en/tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

v4.10-rc4 build: 0 failures 1 warnings (v4.10-rc4)

by Build bot for Mark Brown

Tree/Branch: v4.10-rc4 Git describe: v4.10-rc4 Commit: 49def18533 Linux 4.10-rc4 Build Time: 210 min 52 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

[PATCH v2 3/3] phy: rockchip-inno-usb2: Set EXTCON_USB when EXTCON_CHG_USB_SDP was set

by Baolin Wang

According to the documentation, we should set the EXTCON_USB when one SDP charger connector was reported. Signed-off-by: Baolin Wang <baolin.wang(a)linaro.org> Reviewed-by: Chanwoo Choi <cw00.choi(a)samsung.com> --- Changes since v1: - Change extcon_set_cable_state_() to extcon_set_state_sync(). - Add reviewed tag by Chanwoo Choi. --- drivers/phy/phy-rockchip-inno-usb2.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/phy/phy-rockchip-inno-usb2.c b/drivers/phy/phy-rockchip-inno-usb2.c index 2f99ec9..4ea95c2 100644 --- a/drivers/phy/phy-rockchip-inno-usb2.c +++ b/drivers/phy/phy-rockchip-inno-usb2.c @@ -595,9 +595,14 @@ static void rockchip_usb2phy_otg_sm_work(struct work_struct *work) if (rport->vbus_attached != vbus_attach) { rport->vbus_attached = vbus_attach; - if (notify_charger && rphy->edev) + if (notify_charger && rphy->edev) { extcon_set_cable_state_(rphy->edev, cable, vbus_attach); + if (cable == EXTCON_CHG_USB_SDP) + extcon_set_state_sync(rphy->edev, + EXTCON_USB, + vbus_attach); + } } break; case OTG_STATE_B_PERIPHERAL: -- 1.7.9.5

9 years, 4 months

2
5
0 0

master build: 0 failures 1 warnings (v4.10-rc3-349-gc928162)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc3-349-gc928162 Commit: c928162756 Merge tag 'char-misc-4.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc Build Time: 104 min 36 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc3-313-g83346fb)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc3-313-g83346fb Commit: 83346fbc07 Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Build Time: 101 min 3 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc3-269-gf4d3935)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc3-269-gf4d3935 Commit: f4d3935e4f Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs Build Time: 100 min 57 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc3-251-gf0ad177)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc3-251-gf0ad177 Commit: f0ad17712b Merge tag 'dmaengine-fix-4.10-rc4' of git://git.infradead.org/users/vkoul/slave-dma Build Time: 104 min 33 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

master build: 0 failures 1 warnings (v4.10-rc3-238-ge96f8f1)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.10-rc3-238-ge96f8f1 Commit: e96f8f18c8 Merge branch 'for-linus-4.10' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs Build Time: 106 min 59 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/net/ethernet/mellanox/mlx5/core/en_tc.c:716:40: warning: 'out_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 4 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel January 2017