* [PATCH 02/12] dt-bindings: document s3c24xx controller for external clock output
From: Tomasz Figa @ 2014-02-09 1:54 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <201312131359.00450.heiko@sntech.de>
Hi Heiko,
On 13.12.2013 13:59, Heiko St?bner wrote:
> The clock settings are distributed over a regular register and parts
> of the misccr register.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> .../bindings/clock/samsung,s3c2410-dclk.txt | 53 ++++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/samsung,s3c2410-dclk.txt
>
> diff --git a/Documentation/devicetree/bindings/clock/samsung,s3c2410-dclk.txt b/Documentation/devicetree/bindings/clock/samsung,s3c2410-dclk.txt
> new file mode 100644
> index 0000000..0a1f7b1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/samsung,s3c2410-dclk.txt
> @@ -0,0 +1,53 @@
> +* Samsung S3C24XX External Clock Output Controller
> +
> +The S3C24XX series can generate clock signals on two clock output pads.
> +The clock binding described here is applicable to all SoCs in
> +the s3c24x family.
> +
> +Required Properties:
> +
> +- compatible: should be one of the following.
> + - "samsung,s3c2410-dclk" - controller in S3C2410 SoCs.
> + - "samsung,s3c2412-dclk" - controller in S3C2412 SoCs.
> + - "samsung,s3c2440-dclk" - controller in S3C2440 and S3C2442 SoCs.
> + - "samsung,s3c2443-dclk" - controller in S3C2443 and later SoCs.
> +- reg: physical base address of the controller and length of memory mapped
> + region.
> +- #clock-cells: should be 1.
> +- samsung,misccr: phandle to the syscon managing the misccr register, which
> + holds configuration settings for different soc-components (clocks, usb, ...).
Hmm, looking at the datasheet, DCLK and CLKOUT registers seem to be part
of the pin controller. I wonder if there is really a need for different
driver and device node to handle them.
Could this be simply made a part of the s3c24xx pinctrl driver,
extending it to register also a clock provider under the same DT node?
Best regards,
Tomasz
^ permalink raw reply
* [PATCH 03/12] clk: samsung: add clock driver for external clock outputs
From: Tomasz Figa @ 2014-02-09 2:25 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <201312131359.36576.heiko@sntech.de>
Hi Heiko,
On 13.12.2013 13:59, Heiko St?bner wrote:
> This adds a driver for controlling the external clock outputs of
> s3c24xx architectures including the dclk muxes and dividers.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> drivers/clk/samsung/Makefile | 1 +
> drivers/clk/samsung/clk-s3c2410-dclk.c | 517 ++++++++++++++++++++++
> include/dt-bindings/clock/samsung,s3c2410-dclk.h | 28 ++
> 3 files changed, 546 insertions(+)
> create mode 100644 drivers/clk/samsung/clk-s3c2410-dclk.c
> create mode 100644 include/dt-bindings/clock/samsung,s3c2410-dclk.h
>
> diff --git a/drivers/clk/samsung/Makefile b/drivers/clk/samsung/Makefile
> index 4c892c6..568683c 100644
> --- a/drivers/clk/samsung/Makefile
> +++ b/drivers/clk/samsung/Makefile
> @@ -8,5 +8,6 @@ obj-$(CONFIG_SOC_EXYNOS5250) += clk-exynos5250.o
> obj-$(CONFIG_SOC_EXYNOS5420) += clk-exynos5420.o
> obj-$(CONFIG_SOC_EXYNOS5440) += clk-exynos5440.o
> obj-$(CONFIG_ARCH_EXYNOS) += clk-exynos-audss.o
> +obj-$(CONFIG_S3C2410_COMMON_DCLK)+= clk-s3c2410-dclk.o
> obj-$(CONFIG_S3C2443_COMMON_CLK)+= clk-s3c2443.o
> obj-$(CONFIG_ARCH_S3C64XX) += clk-s3c64xx.o
> diff --git a/drivers/clk/samsung/clk-s3c2410-dclk.c b/drivers/clk/samsung/clk-s3c2410-dclk.c
> new file mode 100644
> index 0000000..de10e5c
> --- /dev/null
> +++ b/drivers/clk/samsung/clk-s3c2410-dclk.c
> @@ -0,0 +1,517 @@
> +/*
> + * Copyright (c) 2013 Heiko Stuebner <heiko@sntech.de>
> + *
> + * 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.
> + *
> + * Common Clock Framework support for s3c24xx external clock output.
> + */
> +
> +#include <linux/platform_device.h>
> +#include <linux/module.h>
> +#include <linux/mfd/syscon.h>
> +#include <linux/clk-provider.h>
> +#include <linux/regmap.h>
> +#include <linux/of.h>
> +#include <dt-bindings/clock/samsung,s3c2410-dclk.h>
> +#include "clk.h"
> +
> +/* legacy access to misccr, until dt conversion is finished */
> +#include <mach/hardware.h>
> +#include <mach/regs-gpio.h>
> +
> +enum supported_socs {
> + S3C2410,
> + S3C2412,
> + S3C2440,
> + S3C2443,
> +};
> +
> +struct s3c24xx_dclk_drv_data {
> + int cpu_type;
> +};
> +
> +/*
> + * Clock for output-parent selection in misccr
> + */
> +
> +struct s3c24xx_clkout {
> + struct clk_hw hw;
> + struct regmap *misccr;
> + u32 mask;
> + u8 shift;
> +};
> +
> +#define to_s3c24xx_clkout(_hw) container_of(_hw, struct s3c24xx_clkout, hw)
> +
> +static u8 s3c24xx_clkout_get_parent(struct clk_hw *hw)
> +{
> + struct s3c24xx_clkout *clkout = to_s3c24xx_clkout(hw);
> + int num_parents = __clk_get_num_parents(hw->clk);
> + u32 val;
> + int ret = 0;
> +
> + if (clkout->misccr)
> + ret = regmap_read(clkout->misccr, 0, &val);
> + else
> + val = readl_relaxed(S3C24XX_MISCCR) >> clkout->shift;
I wonder if this couldn't be simplified by always providing a regmap.
> +
> + if (ret)
> + return ret;
> +
> + val >>= clkout->shift;
> + val &= clkout->mask;
> +
> + if (val >= num_parents)
> + return -EINVAL;
> +
> + return val;
> +}
[snip]
> +#define to_s3c24xx_dclk0(x) \
> + container_of(x, struct s3c24xx_dclk, dclk0_div_change_nb)
> +
> +#define to_s3c24xx_dclk1(x) \
> + container_of(x, struct s3c24xx_dclk, dclk1_div_change_nb)
> +
> +static const char dummy_nm[] __initconst = "dummy_name";
What's the advantage of having it defined this way instead of using
"dummy_name" (or probably "reserved" or "none", as in Samsung clock
drivers) directly in parent lists?
> +
> +PNAME(dclk_s3c2410_p) = { "pclk", "uclk" };
> +PNAME(clkout0_s3c2410_p) = { "mpll", "upll", "fclk", "hclk", "pclk",
> + "gate_dclk0" };
> +PNAME(clkout1_s3c2410_p) = { "mpll", "upll", "fclk", "hclk", "pclk",
> + "gate_dclk1" };
> +
> +PNAME(clkout0_s3c2412_p) = { "mpll", "upll", dummy_nm /* rtc clock output */,
> + "hclk", "pclk", "gate_dclk0" };
Hmm, this would suggest that instead of dummy_nm, a real name should be
used here, even if such clock doesn't exist yet. CCF will handle this fine.
> +PNAME(clkout1_s3c2412_p) = { "xti", "upll", "fclk", "hclk", "pclk",
> + "gate_dclk1" };
> +
> +PNAME(clkout0_s3c2440_p) = { "xti", "upll", "fclk", "hclk", "pclk",
> + "gate_dclk0" };
> +PNAME(clkout1_s3c2440_p) = { "mpll", "upll", dummy_nm /* rtc clock output */,
> + "hclk", "pclk", "gate_dclk1" };
[snip]
> +static int s3c24xx_dclk_probe(struct platform_device *pdev)
> +{
> + struct s3c24xx_dclk *s3c24xx_dclk;
> + struct device_node *np = pdev->dev.of_node;
> + struct regmap *misccr = NULL;
> + struct resource *mem;
> + struct clk **clk_table;
> + const char **clkout0_parent_names, **clkout1_parent_names;
> + u8 clkout0_num_parents, clkout1_num_parents;
> + int current_soc, ret, i;
> +
> + s3c24xx_dclk = devm_kzalloc(&pdev->dev, sizeof(*s3c24xx_dclk),
> + GFP_KERNEL);
> + if (!s3c24xx_dclk)
> + return -ENOMEM;
> +
> + s3c24xx_dclk->dev = &pdev->dev;
> + platform_set_drvdata(pdev, s3c24xx_dclk);
> + spin_lock_init(&s3c24xx_dclk->dclk_lock);
> +
> + clk_table = devm_kzalloc(&pdev->dev,
> + sizeof(struct clk *) * DCLK_MAX_CLKS,
> + GFP_KERNEL);
> + if (!clk_table)
> + return -ENOMEM;
> +
> + s3c24xx_dclk->clk_data.clks = clk_table;
> + s3c24xx_dclk->clk_data.clk_num = DCLK_MAX_CLKS;
> +
> + mem = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + s3c24xx_dclk->base = devm_ioremap_resource(&pdev->dev, mem);
> + if (IS_ERR(s3c24xx_dclk->base))
> + return PTR_ERR(s3c24xx_dclk->base);
> +
> + /* when run from devicetree, get the misccr through a syscon-regmap */
> + if (np) {
> + misccr = syscon_regmap_lookup_by_phandle(np, "samsung,misccr");
> + if (IS_ERR(misccr)) {
> + dev_err(&pdev->dev, "could not get misccr syscon, %ld\n",
> + PTR_ERR(misccr));
> + return PTR_ERR(misccr);
> + }
> + }
> +
> + current_soc = s3c24xx_dclk_get_driver_data(pdev);
> +
> + if (current_soc == S3C2443) {
> + clk_table[MUX_DCLK0] = clk_register_mux(&pdev->dev,
> + "mux_dclk0", dclk_s3c2443_p,
> + ARRAY_SIZE(dclk_s3c2443_p), 0,
> + s3c24xx_dclk->base, 1, 1, 0,
> + &s3c24xx_dclk->dclk_lock);
> + clk_table[MUX_DCLK1] = clk_register_mux(&pdev->dev,
> + "mux_dclk1", dclk_s3c2443_p,
> + ARRAY_SIZE(dclk_s3c2443_p), 0,
> + s3c24xx_dclk->base, 17, 1, 0,
> + &s3c24xx_dclk->dclk_lock);
> + } else {
> + clk_table[MUX_DCLK0] = clk_register_mux(&pdev->dev,
> + "mux_dclk0", dclk_s3c2410_p,
> + ARRAY_SIZE(dclk_s3c2410_p), 0,
> + s3c24xx_dclk->base, 1, 1, 0,
> + &s3c24xx_dclk->dclk_lock);
> + clk_table[MUX_DCLK1] = clk_register_mux(&pdev->dev,
> + "mux_dclk1", dclk_s3c2410_p,
> + ARRAY_SIZE(dclk_s3c2410_p), 0,
> + s3c24xx_dclk->base, 17, 1, 0,
> + &s3c24xx_dclk->dclk_lock);
> + }
What about using a variant struct instead? Match tables would simply
contain pointers to respective structs and here the code would refer to
appropriate fields in a struct returned by s3c24xx_dclk_get_driver_data().
> +
> + clk_table[DIV_DCLK0] = clk_register_divider(&pdev->dev, "div_dclk0",
> + "mux_dclk0", 0, s3c24xx_dclk->base,
> + 4, 4, 0, &s3c24xx_dclk->dclk_lock);
> + clk_table[DIV_DCLK1] = clk_register_divider(&pdev->dev, "div_dclk1",
> + "mux_dclk1", 0, s3c24xx_dclk->base,
> + 20, 4, 0, &s3c24xx_dclk->dclk_lock);
> +
> + clk_table[GATE_DCLK0] = clk_register_gate(&pdev->dev, "gate_dclk0",
> + "div_dclk0", CLK_SET_RATE_PARENT,
> + s3c24xx_dclk->base, 0, 0,
> + &s3c24xx_dclk->dclk_lock);
> + clk_table[GATE_DCLK1] = clk_register_gate(&pdev->dev, "gate_dclk1",
> + "div_dclk1", CLK_SET_RATE_PARENT,
> + s3c24xx_dclk->base, 16, 0,
> + &s3c24xx_dclk->dclk_lock);
> +
> + switch (current_soc) {
> + case S3C2410:
> + clkout0_parent_names = clkout0_s3c2410_p;
> + clkout0_num_parents = ARRAY_SIZE(clkout0_s3c2410_p);
> + clkout1_parent_names = clkout1_s3c2410_p;
> + clkout1_num_parents = ARRAY_SIZE(clkout1_s3c2410_p);
> + break;
> + case S3C2412:
> + clkout0_parent_names = clkout0_s3c2412_p;
> + clkout0_num_parents = ARRAY_SIZE(clkout0_s3c2412_p);
> + clkout1_parent_names = clkout1_s3c2412_p;
> + clkout1_num_parents = ARRAY_SIZE(clkout1_s3c2412_p);
> + break;
> + case S3C2440:
> + clkout0_parent_names = clkout0_s3c2440_p;
> + clkout0_num_parents = ARRAY_SIZE(clkout0_s3c2440_p);
> + clkout1_parent_names = clkout1_s3c2440_p;
> + clkout1_num_parents = ARRAY_SIZE(clkout1_s3c2440_p);
> + break;
> + case S3C2443:
> + clkout0_parent_names = clkout0_s3c2443_p;
> + clkout0_num_parents = ARRAY_SIZE(clkout0_s3c2443_p);
> + clkout1_parent_names = clkout1_s3c2443_p;
> + clkout1_num_parents = ARRAY_SIZE(clkout1_s3c2443_p);
> + break;
> + default:
> + dev_err(&pdev->dev, "unsupported soc %d\n", current_soc);
> + ret = -EINVAL;
> + goto err_clk_register;
> + }
Ditto.
> +
> + clk_table[MUX_CLKOUT0] = s3c24xx_register_clkout(&pdev->dev,
> + "clkout0", clkout0_parent_names,
> + clkout0_num_parents, misccr, 4, 7);
> + clk_table[MUX_CLKOUT1] = s3c24xx_register_clkout(&pdev->dev, "clkout1",
> + clkout1_parent_names,
> + clkout1_num_parents, misccr, 8, 7);
> +
> + for (i = 0; i < DCLK_MAX_CLKS; i++)
> + if (IS_ERR(clk_table[i])) {
> + dev_err(&pdev->dev, "clock %d failed to register\n", i);
> + ret = PTR_ERR(clk_table[i]);
> + goto err_clk_register;
> + }
> +
> + ret = clk_register_clkdev(clk_table[MUX_DCLK0], "dclk0", NULL);
> + ret |= clk_register_clkdev(clk_table[MUX_DCLK1], "dclk1", NULL);
> + ret |= clk_register_clkdev(clk_table[MUX_CLKOUT0], "clkout0", NULL);
> + ret |= clk_register_clkdev(clk_table[MUX_CLKOUT1], "clkout1", NULL);
Hmm, won't it break the error value if two calls return different error
codes?
I guess that
if (!ret)
ret = ...
if (!ret)
ret = ...
construct would be more appropriate here, if you don't want error
message per call.
> + if (ret) {
> + dev_err(&pdev->dev, "failed to register aliases\n");
> + goto err_clk_register;
> + }
> +
> + s3c24xx_dclk->dclk0_div_change_nb.notifier_call =
> + s3c24xx_dclk0_div_notify;
> + s3c24xx_dclk->dclk0_div_change_nb.next = NULL;
Do you need to set this field to NULL explicitly?
Best regards,
Tomasz
^ permalink raw reply
* [PATCH] arm: add DSB after icache flush in __flush_icache_all()
From: Dirk Behme @ 2014-02-09 6:09 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391592782-18576-1-git-send-email-vkale@apm.com>
Am 05.02.2014 10:33, schrieb Vinayak Kale:
> Add DSB after icache flush to complete the cache maintenance operation.
>
> Signed-off-by: Vinayak Kale <vkale@apm.com>
Should this go to -stable, too?
I haven't looked into the details, but at least it seems to apply
cleanly on a 3.8 kernel.
Best regards
Dirk
> ---
>
> PS:
> - This patch is tested for ARM-v7.
>
> arch/arm/include/asm/cacheflush.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/include/asm/cacheflush.h b/arch/arm/include/asm/cacheflush.h
> index ee753f1..ab91ebb 100644
> --- a/arch/arm/include/asm/cacheflush.h
> +++ b/arch/arm/include/asm/cacheflush.h
> @@ -212,6 +212,7 @@ extern void copy_to_user_page(struct vm_area_struct *, struct page *,
> static inline void __flush_icache_all(void)
> {
> __flush_icache_preferred();
> + dsb();
> }
>
> /*
>
^ permalink raw reply
* [PATCH 1/3] crypto: Fix the pointer voodoo in unaligned ahash
From: Marek Vasut @ 2014-02-09 6:15 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20140209011856.GB16905@gondor.apana.org.au>
On Sunday, February 09, 2014 at 02:18:56 AM, Herbert Xu wrote:
> On Tue, Jan 14, 2014 at 01:35:50PM -0600, Tom Lendacky wrote:
> > On Tuesday, January 14, 2014 06:33:47 PM Marek Vasut wrote:
> > > Add documentation for the pointer voodoo that is happening in
> > > crypto/ahash.c in ahash_op_unaligned(). This code is quite confusing,
> > > so add a beefy chunk of documentation.
> > >
> > > Moreover, make sure the mangled request is completely restored after
> > > finishing this unaligned operation. This means restoring all of
> > > .result, .priv, .base.data and .base.complete .
> > >
> > > Also, remove the crypto_completion_t complete = ... line present in the
> > > ahash_op_unaligned_done() function. This type actually declares a
> > > function pointer, which is very confusing.
> > >
> > > Finally, yet very important nonetheless, make sure the req->priv is
> > > free()'d only after the original request is restored in
> > > ahash_op_unaligned_done(). The req->priv data must not be free()'d
> > > before that in ahash_op_unaligned_finish(), since we would be
> > > accessing previously free()'d data in ahash_op_unaligned_done() and
> > > cause corruption.
> > >
> > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > Cc: David S. Miller <davem@davemloft.net>
> > > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > > Cc: Shawn Guo <shawn.guo@linaro.org>
> > > Cc: Tom Lendacky <thomas.lendacky@amd.com>
> > > ---
> > >
> > > crypto/ahash.c | 65
> > > ++++++++++++++++++++++++++++++++++++++++++++++++---------- 1 file
> > > changed, 54 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/crypto/ahash.c b/crypto/ahash.c
> > > index a92dc38..5ca8ede 100644
> > > --- a/crypto/ahash.c
> > > +++ b/crypto/ahash.c
> > > @@ -29,6 +29,7 @@
> > >
> > > struct ahash_request_priv {
> > >
> > > crypto_completion_t complete;
> > > void *data;
> > >
> > > + void *priv;
> > >
> > > u8 *result;
> > > void *ubuf[] CRYPTO_MINALIGN_ATTR;
> > >
> > > };
> > >
> > > @@ -200,23 +201,38 @@ static void ahash_op_unaligned_finish(struct
> > > ahash_request *req, int err)
> > >
> > > if (!err)
> > >
> > > memcpy(priv->result, req->result,
> > >
> > > crypto_ahash_digestsize(crypto_ahash_reqtfm(req)));
> > >
> > > -
> > > - kzfree(priv);
> >
> > You can't move/remove this kzfree since a synchronous operation will not
> > take the ahash_op_unaligned_done path. A synchronous operation will
> > never return -EINPROGRESS and the effect will be to never free the priv
> > structure.
>
> Marek, did you have a chance to address this?
Hi,
it's in the pipeline, I'm just overloaded. We missed a MW for this, right ? :-(
^ permalink raw reply
* irqchip: irq-dove: problem with the PMU interrupt controller.
From: Jean-Francois Moine @ 2014-02-09 8:10 UTC (permalink / raw)
To: linux-arm-kernel
Hi Andrew,
I have a WARN_ON at system startup time of the Cubox (Marvell Dove).
Sorry for I don't know enough about the IRQ subsystem to fix it.
irq: no irq domain found for /mbus/internal-regs/pmu-interrupt-ctrl at d0050 !
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at /home/jef/c-3.14/drivers/of/platform.c:171 of_device_alloc+0x190/0x194()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 3.14.0-rc1-dirty #45
Backtrace:
[<80011720>] (dump_backtrace) from [<800119fc>] (show_stack+0x18/0x1c)
r6:000000ab r5:00000009 r4:00000000 r3:00000000
[<800119e4>] (show_stack) from [<803c8fcc>] (dump_stack+0x24/0x28)
[<803c8fa8>] (dump_stack) from [<8001b5cc>] (warn_slowpath_common+0x74/0x8c)
[<8001b558>] (warn_slowpath_common) from [<8001b688>] (warn_slowpath_null+0x24/0x2c)
r8:00000000 r7:00000001 r6:bb075c40 r5:bb7d7cb4 r4:00000001
[<8001b664>] (warn_slowpath_null) from [<802dbf0c>] (of_device_alloc+0x190/0x194)
[<802dbd7c>] (of_device_alloc) from [<802dbf48>] (of_platform_device_create_pdata+0x38/0x90)
r10:00000000 r9:bb05d890 r8:803f28fc r7:00000000 r6:bb05d890 r5:00000000
r4:bb7d7cb4
[<802dbf10>] (of_platform_device_create_pdata) from [<802dc0ac>] (of_platform_bus_create+0xf0/0x174)
r7:00000001 r6:00000000 r5:bb7d7cb4 r4:00000000
[<802dbfbc>] (of_platform_bus_create) from [<802dc108>] (of_platform_bus_create+0x14c/0x174)
...
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
^ permalink raw reply
* irqchip: irq-dove: problem with the PMU interrupt controller.
From: Andrew Lunn @ 2014-02-09 8:22 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20140209091016.26a59d44@armhf>
On Sun, Feb 09, 2014 at 09:10:16AM +0100, Jean-Francois Moine wrote:
> Hi Andrew,
>
> I have a WARN_ON at system startup time of the Cubox (Marvell Dove).
> Sorry for I don't know enough about the IRQ subsystem to fix it.
Hi Jean-Francois
The DT node made it into -rc1, but the driver itself was forgotten by
the IRQ maintainer. It will hopefully appear in -rc2.
Andrew
>
> irq: no irq domain found for /mbus/internal-regs/pmu-interrupt-ctrl at d0050 !
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at /home/jef/c-3.14/drivers/of/platform.c:171 of_device_alloc+0x190/0x194()
> Modules linked in:
> CPU: 0 PID: 1 Comm: swapper Not tainted 3.14.0-rc1-dirty #45
> Backtrace:
> [<80011720>] (dump_backtrace) from [<800119fc>] (show_stack+0x18/0x1c)
> r6:000000ab r5:00000009 r4:00000000 r3:00000000
> [<800119e4>] (show_stack) from [<803c8fcc>] (dump_stack+0x24/0x28)
> [<803c8fa8>] (dump_stack) from [<8001b5cc>] (warn_slowpath_common+0x74/0x8c)
> [<8001b558>] (warn_slowpath_common) from [<8001b688>] (warn_slowpath_null+0x24/0x2c)
> r8:00000000 r7:00000001 r6:bb075c40 r5:bb7d7cb4 r4:00000001
> [<8001b664>] (warn_slowpath_null) from [<802dbf0c>] (of_device_alloc+0x190/0x194)
> [<802dbd7c>] (of_device_alloc) from [<802dbf48>] (of_platform_device_create_pdata+0x38/0x90)
> r10:00000000 r9:bb05d890 r8:803f28fc r7:00000000 r6:bb05d890 r5:00000000
> r4:bb7d7cb4
> [<802dbf10>] (of_platform_device_create_pdata) from [<802dc0ac>] (of_platform_bus_create+0xf0/0x174)
> r7:00000001 r6:00000000 r5:bb7d7cb4 r4:00000000
> [<802dbfbc>] (of_platform_bus_create) from [<802dc108>] (of_platform_bus_create+0x14c/0x174)
> ...
>
> --
> Ken ar c'henta? | ** Breizh ha Linux atav! **
> Jef | http://moinejf.free.fr/
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply
* [PATCH] dcp: aes: Move the AES operation type from actx to rctx
From: Herbert Xu @ 2014-02-09 9:19 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1389720661-5820-1-git-send-email-marex@denx.de>
On Tue, Jan 14, 2014 at 06:31:01PM +0100, Marek Vasut wrote:
> Move the AES operation type and mode from async crypto context to
> crypto request context. This allows for recycling of the async crypto
> context for different kinds of operations.
>
> I found this problem when I used dm-crypt, which uses the same async
> crypto context (actx) for both encryption and decryption requests.
> Since the requests are enqueued into the processing queue, immediatelly
> storing the type of operation into async crypto context (actx) caused
> corruption of this information when encryption and decryption operations
> followed imediatelly one after the other. When the first operation was
> dequeued, the second operation was already enqueued and overwritten the
> type of operation in actx, thus causing incorrect result of the first
> operation.
>
> Fix this problem by storing the type of operation into the crypto request
> context.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
Patch applied.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
^ permalink raw reply
* [PATCH RFC 0/2] drivers/base: simplify simple DT-based components
From: Jean-Francois Moine @ 2014-02-09 9:22 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20140207202351.GH26684@n2100.arm.linux.org.uk>
On Fri, 7 Feb 2014 20:23:51 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> Here's my changes to the TDA998x driver to add support for the component
> helper. The TDA998x driver retains support for the old way so that
> drivers can be transitioned. For any one DRM "card" the transition to
I rewrote the tda998x as a simple encoder+connector (i.e. not a
slave_encoder) with your component helper, and the code is much clearer
and simpler: the DRM driver has nothing to do except to know that the
tda998x is a component and to set the possible_crtcs.
AFAIK, only the tilcdc drm driver is using the tda998x as a
slave_encoder. It does a (encoder+connector) conversion to
(slave_encoder). Then, in your changes in the TDA998x, you do a
(slave_encoder) translation to (encoder+connector).
This seems rather complicated!
I think it would be easier to use your component helper and rewrite
(remove?) tilcdc_slave.c.
> And yes, I'm thinking that maybe moving compare_of() into the component
> support so that drivers can share this generic function may be a good
> idea.
This function exists already in drivers/of/platform.c as
of_dev_node_match(). It just needs to be exported.
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
^ permalink raw reply
* [PATCH RFC 0/2] drivers/base: simplify simple DT-based components
From: Russell King - ARM Linux @ 2014-02-09 10:04 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20140209102219.3ab40b5e@armhf>
On Sun, Feb 09, 2014 at 10:22:19AM +0100, Jean-Francois Moine wrote:
> On Fri, 7 Feb 2014 20:23:51 +0000
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> > Here's my changes to the TDA998x driver to add support for the component
> > helper. The TDA998x driver retains support for the old way so that
> > drivers can be transitioned. For any one DRM "card" the transition to
>
> I rewrote the tda998x as a simple encoder+connector (i.e. not a
> slave_encoder) with your component helper, and the code is much clearer
> and simpler: the DRM driver has nothing to do except to know that the
> tda998x is a component and to set the possible_crtcs.
That's exactly what I've done - the slave encoder veneer can be simply
deleted when tilcdc is converted.
> AFAIK, only the tilcdc drm driver is using the tda998x as a
> slave_encoder. It does a (encoder+connector) conversion to
> (slave_encoder). Then, in your changes in the TDA998x, you do a
> (slave_encoder) translation to (encoder+connector).
> This seems rather complicated!
No. I first split out the slave encoder functions to be a veneer onto
the tda998x backend, and then add the encoder & connector component
support. Later, the slave encoder veneer can be deleted.
The reason for this is that virtually all the tda998x backend is what's
required by the encoder & connector support - which is completely logical
when you realise that the generic slave encoder support is just a veneer
itself adapting the encoder & connector support to a slave encoder.
So, we're basically getting rid of two veneers, but we end up with exactly
the same functionality.
> > And yes, I'm thinking that maybe moving compare_of() into the component
> > support so that drivers can share this generic function may be a good
> > idea.
>
> This function exists already in drivers/of/platform.c as
> of_dev_node_match(). It just needs to be exported.
Good, thanks for pointing that out.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
^ permalink raw reply
* [RFC/PATCH v2] ARM: vDSO gettimeofday using generic timer architecture
From: Russell King - ARM Linux @ 2014-02-09 10:20 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391814349-10706-1-git-send-email-nathan_lynch@mentor.com>
On Fri, Feb 07, 2014 at 05:05:49PM -0600, Nathan Lynch wrote:
> + /* Grab the vDSO code pages. */
> + for (i = 0; i < vdso_pages; i++) {
> + pg = virt_to_page(&vdso_start + i*PAGE_SIZE);
> + ClearPageReserved(pg);
> + get_page(pg);
> + vdso_pagelist[i] = pg;
> + }
Why do we want to clear the reserved status? This looks over complicated
to me.
> +
> + /* Sanity check the shared object header. */
> + vbase = vmap(vdso_pagelist, 1, 0, PAGE_KERNEL);
> + if (vbase == NULL) {
> + pr_err("Failed to map vDSO pagelist!\n");
> + return -ENOMEM;
> + } else if (memcmp(vbase, "\177ELF", 4)) {
> + pr_err("vDSO is not a valid ELF object!\n");
> + ret = -EINVAL;
> + goto unmap;
> + }
Why do we need to vmap() pages which are already accessible - vdso_start
must be part of the kernel image, and therefore will be accessible via
standard mappings.
> +
> + /* Grab the vDSO data page. */
> + pg = virt_to_page(vdso_data);
> + get_page(pg);
> + vdso_pagelist[i] = pg;
Same goes for this.
> +static long clock_gettime_fallback(clockid_t _clkid, struct timespec *_ts)
> +{
> + register struct timespec *ts asm("r1") = _ts;
> + register clockid_t clkid asm("r0") = _clkid;
> + register long ret asm ("r0");
> + register long nr asm("r7") = __NR_clock_gettime;
> +
> + asm("swi #0" : "=r" (ret) : "r" (clkid), "r" (ts), "r" (nr) : "memory");
This isn't compatible with OABI, so either this must not be enabled when
AEABI is disabled, or this needs to be fixed.
> +static long clock_getres_fallback(clockid_t _clkid, struct timespec *_ts)
> +{
> + register struct timespec *ts asm("r1") = _ts;
> + register clockid_t clkid asm("r0") = _clkid;
> + register long ret asm ("r0");
> + register long nr asm("r7") = __NR_clock_getres;
> +
> + asm volatile(
> + "swi #0" :
> + "=r" (ret) :
> + "r" (clkid), "r" (ts), "r" (nr) :
> + "memory");
Same here.
> +static long gettimeofday_fallback(struct timeval *_tv, struct timezone *_tz)
> +{
> + register struct timezone *tz asm("r1") = _tz;
> + register struct timeval *tv asm("r0") = _tv;
> + register long ret asm ("r0");
> + register long nr asm("r7") = __NR_gettimeofday;
> +
> + asm("swi #0" : "=r" (ret) : "r" (tv), "r" (tz), "r" (nr) : "memory");
and here.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
^ permalink raw reply
* [PATCH 1/2] ARM: dts: N9/N950: fix boot hang with 3.14-rc1
From: Aaro Koskinen @ 2014-02-09 12:12 UTC (permalink / raw)
To: linux-arm-kernel
N9/N950 does not boot anymore with 3.14-rc1, because SoC compatible
property is missing. Fix that.
Signed-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>
---
arch/arm/boot/dts/omap3-n9.dts | 2 +-
arch/arm/boot/dts/omap3-n950.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-n9.dts b/arch/arm/boot/dts/omap3-n9.dts
index 39828ce464ee..9938b5dc1909 100644
--- a/arch/arm/boot/dts/omap3-n9.dts
+++ b/arch/arm/boot/dts/omap3-n9.dts
@@ -14,5 +14,5 @@
/ {
model = "Nokia N9";
- compatible = "nokia,omap3-n9", "ti,omap3";
+ compatible = "nokia,omap3-n9", "ti,omap36xx", "ti,omap3";
};
diff --git a/arch/arm/boot/dts/omap3-n950.dts b/arch/arm/boot/dts/omap3-n950.dts
index b076a526b999..261c5589bfa3 100644
--- a/arch/arm/boot/dts/omap3-n950.dts
+++ b/arch/arm/boot/dts/omap3-n950.dts
@@ -14,5 +14,5 @@
/ {
model = "Nokia N950";
- compatible = "nokia,omap3-n950", "ti,omap3";
+ compatible = "nokia,omap3-n950", "ti,omap36xx", "ti,omap3";
};
--
1.8.5.3
^ permalink raw reply related
* [PATCH 2/2] ARM: dts: N900: add missing compatible property
From: Aaro Koskinen @ 2014-02-09 12:12 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391947956-24462-1-git-send-email-aaro.koskinen@iki.fi>
Add missing compatible property to avoid problems in the future.
Signed-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>
---
arch/arm/boot/dts/omap3-n900.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index 6fc85f963530..0bf40c90faba 100644
--- a/arch/arm/boot/dts/omap3-n900.dts
+++ b/arch/arm/boot/dts/omap3-n900.dts
@@ -1,6 +1,6 @@
/*
* Copyright (C) 2013 Pavel Machek <pavel@ucw.cz>
- * Copyright 2013 Aaro Koskinen <aaro.koskinen@iki.fi>
+ * Copyright (C) 2013-2014 Aaro Koskinen <aaro.koskinen@iki.fi>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 (or later) as
@@ -13,7 +13,7 @@
/ {
model = "Nokia N900";
- compatible = "nokia,omap3-n900", "ti,omap3";
+ compatible = "nokia,omap3-n900", "ti,omap3430", "ti,omap3";
cpus {
cpu at 0 {
--
1.8.5.3
^ permalink raw reply related
* [GIT PULL] ARM: imx: device tree changes for 3.15, take 1
From: Shawn Guo @ 2014-02-09 12:16 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <201402061445.06234.arnd@arndb.de>
On Thu, Feb 06, 2014 at 02:45:05PM +0100, Arnd Bergmann wrote:
> On Wednesday 05 February 2014, Shawn Guo wrote:
> > Hi arm-soc folks,
> >
> > This is basically imx-dt-3.14 pull request that missed the 3.14 merge
> > window with the pingrp removal series applied on top of. It also
> > includes a few additional board support I collected since imx-dt-3.14.
> > There will be another round of IMX DT changes for 3.15 later, but this
> > one should be the majority. Please pull, thanks.
>
> Hi Shawn,
>
> no objections to the stuff you add here, but the way it's organized
> is not good. Instead of adding the controversial patches first and
> then reverting them, please redo the series so you don't actually
> have the patches in the history. I see that you have rebased the
> patches on 3.14-rc1 already so there really shouldn't be any cross-
> tree dependencies that make it necessary to keep them in.
Okay. I just spent the weekend to rebuild the branch and reworked quite
a lot of patches to wipe the pingrp stuff from the history.
>
> Also, because of the pure size of the pull request:
>
> 105 files changed, 14073 insertions(+), 3127 deletions(-)
>
> it would be nice to split it up into smaller units. A good
> separation would be to have new board support in one pull
> request and the changes to existing boards in another one.
Some new board support are built on top of the updates to the existing
files for purpose like sharing common part. And some updates are added
on top of new board support along time goes. So it's hard to make such
separation. Considering the amount of imx6 changes these days, I chose
to split the branch into two, one for imx6 changes and the other for all
the rest. Such separation does not involve too much interdependency.
I will send them as the updated pull request shortly.
Shawn
^ permalink raw reply
* [linux-sunxi] [PATCH v2] ARM: sunxi: Add driver for sunxi usb phy
From: Hans de Goede @ 2014-02-09 13:29 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAGb2v67L1X63Pp10H6MFApkLzCvwOokxSW+fH6KquDnqaRGRmQ@mail.gmail.com>
Hi,
On 02/08/2014 05:32 AM, Chen-Yu Tsai wrote:
> On Sat, Feb 8, 2014 at 12:33 AM, Hans de Goede <hdegoede@redhat.com> wrote:
>> The Allwinner A1x / A2x SoCs have 2 or 3 usb phys which are all accessed
>> through a single set of registers. Besides this there are also some other
>> phy related bits which need poking, which are per phy, but shared between the
>> ohci and ehci controllers, so these are also controlled from this new phy
>> driver.
>>
<snip>
>> + snprintf(name, sizeof(name), "usb%d_reset", i);
>> + reset = devm_reset_control_get(dev, name);
>> + if (IS_ERR(phy)) {
>> + dev_err(dev, "failed to get reset %s\n", name);
>> + return PTR_ERR(phy);
>> + }
>
> Wrong variable checked for error here that I pointed out before is still wrong.
Ah, yes my bad, I'll do a v3 fixing this, and switching to using register names as
Maxime requested. Don't know whether I'll be able to send v3 today as I'm currently
on the road. If not I'll try to get it out the door tomorrow.
Regards,
Hans
^ permalink raw reply
* [GIT PULL v2] ARM: imx: i.MX6 DT changes for 3.15, take 1
From: Shawn Guo @ 2014-02-09 13:47 UTC (permalink / raw)
To: linux-arm-kernel
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
git://git.linaro.org/people/shawnguo/linux-2.6.git tags/imx6-dt-3.15
for you to fetch changes up to 22030dea67461df3fefb360ed33c6e2fbd578c9e:
ARM: dts: imx6q: Add support for Zealz GK802 (2014-02-09 21:30:04 +0800)
----------------------------------------------------------------
i.MX6 device tree changes for 3.15:
- A good number of new i.MX6 boards support: cm-fx6, dmo-edmqmx6,
nitrogen6x, Gateworks Ventana gw5xxx family, DFI FS700-M60 and
Zealz GK802
- Update imx6q-sabrelite device tree and add Dual Lite/Solo support
- Move pins that are used by particular client device out of hog group
- Use GPIO_6 for FEC interrupt to workaround a hardware bug (ERR006687
ENET: Only the ENET wake-up interrupt request can wake the system
from Wait mode.)
- Make pinctrl nodes board specific to avoid floating board specific
device tree blob with so many unused pinctrl data
- Use generic node name for fixed regulator
- Update OPP table for cpufreq support
- Random updates on various board device tree sources, adding pinctrl
settings, device nodes, properties, etc.
----------------------------------------------------------------
Anson Huang (7):
ARM: dts: imx6q: update setting of VDDARM_CAP voltage
ARM: dts: imx6q: add vddsoc/pu setpoint info
ARM: dts: imx6dl: enable cpufreq support
ARM: dts: imx6qdl: add necessary thermal clk
ARM: dts: imx6qdl-sabresd: Add power key support
ARM: dts: imx6sl: add ocram device support
ARM: dts: imx6sl: add keypad support for i.mx6sl-evk board.
Fabio Estevam (6):
ARM: dts: imx6q-udoo: Add Ethernet support
ARM: dts: imx6q-sabrelite: Remove duplicate GPIO entry
ARM: dts: imx6q-sabrelite: Place 'status' as the last node
ARM: dts: imx6: Use 'vddarm' as the regulator name
ARM: dts: imx6qdl-sabresd: Add PFUZE100 support
ARM: dts: imx6qdl-sabreauto: Add LVDS support
Frank Li (1):
ARM: dts: imx6qdl: enable dma for spi
John Tobias (1):
ARM: dts: imx6sl: Adding cpu frequency and VDDSOC/PU table.
Lothar Wa?mann (1):
ARM: dts: imx6qdl: add aliases for can interfaces
Marek Vasut (1):
ARM: dts: imx6q-sabrelite: Enable PCI express
Markus Pargmann (1):
ARM: dts: imx6: use imx51-ssi
Nicolin Chen (2):
ARM: dts: imx: specify the value of audmux pinctrl instead of 0x80000000
ARM: dts: imx6qdl: add spdif support for sabreauto
Peter Chen (3):
ARM: dts: imx6q-arm2: enable USB OTG
ARM: dts: imx6: add anatop phandle for usbphy
ARM: dts: imx6: add mxs phy controller id
Philipp Zabel (1):
ARM: dts: imx6q-sabrelite: PHY reset is active-low
Sascha Hauer (4):
ARM: dts: imx6q: Add spi4 alias
ARM: dts: imx6qdl: Add mmc aliases
ARM: dts: imx6: Add DFI FS700-M60 board support
ARM: dts: imx6q: Add support for Zealz GK802
Shawn Guo (3):
ARM: dts: imx6qdl: make pinctrl nodes board specific
ARM: dts: imx6sl: make pinctrl nodes board specific
ARM: dts: imx6: use generic node name for fixed regulator
Silvio F (2):
DT: Add Data Modul vendor prefix
ARM: dts: imx6: Add support for imx6q dmo edmqmx6
Tim Harvey (2):
ARM: dts: disable flexcan by default
ARM: dts: add Gateworks Ventana support
Troy Kisky (26):
ARM: dts: imx: pinfunc: add MX6QDL_PAD_SD1_CLK__OSC32K_32K_OUT
ARM: dts: imx: imx6qdl.dtsi: add mipi_csi tag
ARM: dts: imx: imx6q.dtsi: use IRQ_TYPE_LEVEL_HIGH
ARM: dts: imx: imx6dl.dtsi: use IRQ_TYPE_LEVEL_HIGH
ARM: dts: imx: imx6sl.dtsi: use IRQ_TYPE_LEVEL_HIGH
ARM: dts: imx: imx6qdl.dtsi: use IRQ_TYPE_LEVEL_HIGH
ARM: dts: imx: sabrelite: add Dual Lite/Solo support
ARM: dts: imx6qdl-sabrelite: Add uart1 support
ARM: dts: imx6qdl-sabrelite: remove usdhc4 wp-gpio
ARM: dts: imx6qdl-sabrelite: move USDHC4 CD to pinctrl_usdhc4
ARM: dts: imx6qdl-sabrelite: move USDHC3 CD/WP to pinctrl_usdhc3
ARM: dts: imx6qdl-sabrelite: move spi-nor CS to pinctrl_ecspi1
ARM: dts: imx6qdl-sabrelite: move usbotg power enable to pinctrl_usbotg
ARM: dts: imx6qdl-sabrelite: move phy reset to pinctrl_enet
ARM: dts: imx6qdl-sabrelite: explicitly set pad for SGTL5000 sys_mclk
ARM: dts: imx6qdl-sabrelite: add pwms for backlights
ARM: dts: imx6qdl-sabrelite: add skews for Micrel phy
ARM: dts: imx6qdl-sabrelite: fix ENET group
ARM: dts: imx6qdl-sabrelite: Add over-current pin to usbotg
ARM: dts: imx: add nitrogen6x board
ARM: dts: imx6qdl-sabrelite: add gpio-keys
ARM: dts: imx: pinfunc: add MX6QDL_PAD_GPIO_6__ENET_IRQ
ARM: dts: imx6qdl: use interrupts-extended for fec
ARM: dts: imx6qdl-sabrelite: use GPIO_6 for FEC interrupt.
ARM: dts: imx6qdl-sabreauto: use GPIO_6 for FEC interrupt.
ARM: dts: imx6q-arm2: use GPIO_6 for FEC interrupt.
Valentin Raevsky (1):
ARM: dts: Add initial support for cm-fx6.
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/Makefile | 17 +
arch/arm/boot/dts/imx6dl-dfi-fs700-m60.dts | 23 +
arch/arm/boot/dts/imx6dl-gw51xx.dts | 19 +
arch/arm/boot/dts/imx6dl-gw52xx.dts | 19 +
arch/arm/boot/dts/imx6dl-gw53xx.dts | 19 +
arch/arm/boot/dts/imx6dl-gw54xx.dts | 19 +
arch/arm/boot/dts/imx6dl-nitrogen6x.dts | 21 +
arch/arm/boot/dts/imx6dl-pinfunc.h | 2 +
arch/arm/boot/dts/imx6dl-sabrelite.dts | 20 +
arch/arm/boot/dts/imx6dl.dtsi | 29 +-
arch/arm/boot/dts/imx6q-arm2.dts | 140 ++-
arch/arm/boot/dts/imx6q-cm-fx6.dts | 107 +++
arch/arm/boot/dts/imx6q-dfi-fs700-m60.dts | 23 +
arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts | 372 ++++++++
arch/arm/boot/dts/imx6q-gk802.dts | 171 ++++
arch/arm/boot/dts/imx6q-gw51xx.dts | 19 +
arch/arm/boot/dts/imx6q-gw52xx.dts | 23 +
arch/arm/boot/dts/imx6q-gw53xx.dts | 23 +
arch/arm/boot/dts/imx6q-gw5400-a.dts | 546 ++++++++++++
arch/arm/boot/dts/imx6q-gw54xx.dts | 23 +
arch/arm/boot/dts/imx6q-nitrogen6x.dts | 25 +
arch/arm/boot/dts/imx6q-phytec-pfla02.dtsi | 85 +-
arch/arm/boot/dts/imx6q-pinfunc.h | 2 +
arch/arm/boot/dts/imx6q-sabrelite.dts | 178 +---
arch/arm/boot/dts/imx6q-sbc6x.dts | 58 +-
arch/arm/boot/dts/imx6q-udoo.dts | 54 +-
arch/arm/boot/dts/imx6q.dtsi | 21 +-
arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi | 199 +++++
arch/arm/boot/dts/imx6qdl-gw51xx.dtsi | 374 ++++++++
arch/arm/boot/dts/imx6qdl-gw52xx.dtsi | 490 ++++++++++
arch/arm/boot/dts/imx6qdl-gw53xx.dtsi | 553 ++++++++++++
arch/arm/boot/dts/imx6qdl-gw54xx.dtsi | 580 ++++++++++++
arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi | 422 +++++++++
arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 246 ++++-
arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 423 +++++++++
arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 272 +++++-
arch/arm/boot/dts/imx6qdl-wandboard.dtsi | 128 ++-
arch/arm/boot/dts/imx6qdl.dtsi | 938 +++-----------------
arch/arm/boot/dts/imx6sl-evk.dts | 210 ++++-
arch/arm/boot/dts/imx6sl.dtsi | 385 +++-----
41 files changed, 5919 insertions(+), 1360 deletions(-)
create mode 100644 arch/arm/boot/dts/imx6dl-dfi-fs700-m60.dts
create mode 100644 arch/arm/boot/dts/imx6dl-gw51xx.dts
create mode 100644 arch/arm/boot/dts/imx6dl-gw52xx.dts
create mode 100644 arch/arm/boot/dts/imx6dl-gw53xx.dts
create mode 100644 arch/arm/boot/dts/imx6dl-gw54xx.dts
create mode 100644 arch/arm/boot/dts/imx6dl-nitrogen6x.dts
create mode 100644 arch/arm/boot/dts/imx6dl-sabrelite.dts
create mode 100644 arch/arm/boot/dts/imx6q-cm-fx6.dts
create mode 100644 arch/arm/boot/dts/imx6q-dfi-fs700-m60.dts
create mode 100644 arch/arm/boot/dts/imx6q-dmo-edmqmx6.dts
create mode 100644 arch/arm/boot/dts/imx6q-gk802.dts
create mode 100644 arch/arm/boot/dts/imx6q-gw51xx.dts
create mode 100644 arch/arm/boot/dts/imx6q-gw52xx.dts
create mode 100644 arch/arm/boot/dts/imx6q-gw53xx.dts
create mode 100644 arch/arm/boot/dts/imx6q-gw5400-a.dts
create mode 100644 arch/arm/boot/dts/imx6q-gw54xx.dts
create mode 100644 arch/arm/boot/dts/imx6q-nitrogen6x.dts
create mode 100644 arch/arm/boot/dts/imx6qdl-dfi-fs700-m60.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-gw51xx.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-gw52xx.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-gw53xx.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-gw54xx.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-sabrelite.dtsi
^ permalink raw reply
* [GIT PULL v2] ARM: imx: device tree changes for 3.15, take 1
From: Shawn Guo @ 2014-02-09 13:48 UTC (permalink / raw)
To: linux-arm-kernel
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
git://git.linaro.org/people/shawnguo/linux-2.6.git tags/imx-dt-3.15
for you to fetch changes up to ee97d154f0a81f87f0f88c99a3963da2ab5ad787:
ARM: dts: imx28-m28cu3: Remove 'reset-active-high' (2014-02-09 21:33:52 +0800)
----------------------------------------------------------------
i.MX device tree changes for 3.15:
- New SoC device tree support for imx35 and imx50
- A good number of new board support: imx25-eukrea, imx28-duckbill,
imx28-eukrea, Eukrea cpuimx35, imx50-evk, imx51-eukrea, imx53-voipac,
MCIMX53-START-R and Ka-Ro TX53.
- Quite some updates and tweaking on imx27 phycore and apf27dev boards
- Add pinfunc headers for imx25, imx27 and imx50
- Make pinctrl nodes board specific to avoid floating board specific
device tree blob with so many unused pinctrl data
- Use generic node name for fixed regulator
- Use clock defines in imx5 DTS files
- Use macros for interrupt and gpio flags
- A plenty of random updates on various SoC and board device tree
sources, adding pinctrl settings, device nodes, properties, aliases.
----------------------------------------------------------------
Aida Mynzhasova (1):
ARM: dts: mxs: add auart2 pinmux to imx28.dtsi
Alexander Shiyan (22):
ARM: dts: i.MX51: Update CPU node
ARM: dts: i.MX51: Add dummy clock to AUDMUX
ARM: dts: i.MX51: Switch to use standard IRQ flags definitions
ARM: dts: i.MX51: Move usbphy0 node from AIPS1
ARM: dts: i.MX51 boards: Switch to use standard GPIO flags definitions
ARM: dts: imx51-babbage: Fix chipselect level for dataflash on spi0.1
ARM: dts: imx51-babbage: Define FEC reset pin
ARM: dts: imx27-phytec-phycore-som: Add on-flash BBT support
ARM: dts: imx27-phytec-phycore-rdk: Add DT node for camera module
ARM: dts: imx27-phytec-phycore-som: Update FEC node
ARM: dts: i.MX27 boards: Switch to use standard GPIO and IRQ flags definitions
ARM: dts: i.MX27: Configure GPIOs as "input" by default
ARM: dts: imx27-phytec-phycore-som: Add pinctrl for CSPI1 and GPIOs used on module
ARM: dts: imx27-phytec-phycore-som: Rename file to .dtsi
ARM: dts: imx27-phytec-phycore-som: Add NFC pin group
ARM: dts: imx27-phytec-phycore-rdk: Enable 1-Wire module
ARM: dts: imx27-phytec-phycore-som: Add spi-cs-high property to PMIC
ARM: dts: imx27-phytec-phycore-rdk: Add pingrp for SDHC
ARM: dts: imx27-phytec-phycore-rdk: Add pinctrl definitions for WEIM
ARM: dts: i.MX27: Add SSI nodes
ARM: dts: imx53-evk: Remove board support
ARM: dts: i.MX51: Switch to use standard definitions for input subsystem
Alexandre Belloni (3):
ARM: dts: mxs: add #io-channel-cells to mx28 lradc
ARM: dts: mxs: Add iio-hwmon to mx28 soc
ARM: dts: mxs: Add iio-hwmon to mx23 soc
Denis Carikli (12):
of: add vendor prefix for Eukrea Electromatique.
ARM: dts: i.MX25: Add ssi clocks and DMA events.
ARM: dts: i.MX25: Add sdma script path.
ARM: dts: imx25.dtsi: Add a label for the Audio Multiplexer.
ARM: dts: Add support for the cpuimx51 board from Eukrea and its baseboard.
ARM: dts: imx25: Add pinctrl functions.
ARM: dts: imx25.dtsi: label the iomuxc.
ARM: dts: mxs: Add 18bit pin config for lcdif.
ARM: dts: mxs: Add a new pin config for the usb0 ID.
ARM: dts: Add support for the cpuimx25 board from Eukrea and its baseboard.
ARM: dts: imx53: Add gpio and input dt includes.
ARM: dts: Add support for the cpuimx35 board from Eukrea and its baseboard.
Eric B?nard (1):
ARM: mxs: Add support for the eukrea-cpuimx28.
Fabio Estevam (2):
ARM: dts: imx28-evk: Run I2C0 at 400kHz
ARM: dts: imx28-m28cu3: Remove 'reset-active-high'
Greg Ungerer (3):
ARM: dts: imx: add device tree pin definitions for the IMX50
ARM: dts: imx: add IMX50 SoC device tree
ARM: dts: imx: add device tree support for Freescale imx50evk board
Gwenhael Goavec-Merou (8):
ARM: imx27-apf27dev: Add sdhci support
ARM: dts: imx27-apf27dev: fix display size
ARM: dts: imx27: imx27-apf27: add pinctrl for fec and uart1
ARM: dts: imx27: imx27-apf27dev: add pinctrl for cspi, i2c, sdhc and framebuffer
ARM: dts: apf28dev: set gpio polarity for usb regulator and pinctrl for regulator gpio
ARM: imx28: add apf28 specific initialization (macaddr)
ARM: dts: apf27dev: Add pwm support
ARM: dts: imx27-apf27dev: Add pinctrl for cspi, sdhci, leds and keys
Huang Shijie (1):
ARM: dts: vf610: use the interrupt macros
Lothar Wa?mann (1):
ARM: dts: imx53: add support for Ka-Ro TX53 modules
Lucas Stach (3):
ARM: imx53: use clock defines in DTS files
ARM: imx51: use clock defines in DTS files
ARM: imx50: use clock defines in DTS files
Marek Vasut (5):
ARM: dts: imx53: Fix display pinmux for M53EVK
ARM: dts: imx53: Fix backlight for M53EVK
ARM: dts: imx53: Add USB support for M53EVK
ARM: dts: imx53: Add AHCI SATA DT node
ARM: dts: imx53: Enable AHCI SATA for M53EVK
Markus Pargmann (6):
ARM: dts: imx27 pin functions
ARM: dts: imx27 iomux device node
ARM: dts: imx27 phyCARD-S pinctrl
ARM: dts: imx27 phycore move uart1 to rdk
ARM: dts: imx27 phycore pinctrl
ARM: dts: imx5: use imx51-ssi
Maxime Ripard (2):
ARM: mxs: cfa10049: Add NAU7802 ADCs to the device tree
ARM: dts: cfa10036: Add dr_mode and phy_type properties to the DT
Michael Grzeschik (1):
ARM: i.MX28: dts: rename usbphy pin names
Michael Heimpold (1):
ARM: mxs: add support for I2SE's duckbill series
Peter Chen (1):
ARM: dts: mxs: add mxs phy controller id
Robert Nelson (1):
ARM: dts: imx53: Enable AHCI SATA for imx53-qsb
Rostislav Lisovy (4):
ARM: dts: i.MX53: Internal keyboard controller
ARM: dts: Add vendor prefix for Voipac Technologies s.r.o.
ARM: dts: i.MX53: dts for Voipac x53-dmm-668 module
ARM: dts: i.MX53: Devicetree for Voipac Baseboard using x53-dmm-668 module
Sascha Hauer (2):
ARM: dts: imx53: Add mmc aliases
ARM: dts: imx51: Add mmc aliases
Shawn Guo (5):
ARM: dts: imx53: make pinctrl nodes board specific
ARM: dts: imx51: make pinctrl nodes board specific
ARM: dts: vf610: make pinctrl nodes board specific
ARM: dts: imx53-mba53: create a container for fixed regulators
ARM: dts: imx: use generic node name for fixed regulator
Steffen Trumtrar (3):
ARM: dts: Add support for the i.MX35.
ARM: dts: i.MX53: move common QSB nodes to new file
ARM: dts: i.MX53: add support for MCIMX53-START-R
S?bastien Szymanski (1):
ARM: dts: imx28-apf28dev: add user button
.../devicetree/bindings/vendor-prefixes.txt | 2 +
arch/arm/boot/dts/Makefile | 13 +-
arch/arm/boot/dts/imx23-evk.dts | 8 +-
arch/arm/boot/dts/imx23-olinuxino.dts | 5 +-
arch/arm/boot/dts/imx23-stmp378x_devb.dts | 5 +-
arch/arm/boot/dts/imx23.dtsi | 8 +-
arch/arm/boot/dts/imx25-eukrea-cpuimx25.dtsi | 73 ++
.../boot/dts/imx25-eukrea-mbimxsd25-baseboard.dts | 174 ++++
arch/arm/boot/dts/imx25-pinfunc.h | 494 +++++++++++
arch/arm/boot/dts/imx25.dtsi | 18 +-
arch/arm/boot/dts/imx27-apf27.dts | 38 +
arch/arm/boot/dts/imx27-apf27dev.dts | 149 +++-
arch/arm/boot/dts/imx27-phytec-phycard-s-rdk.dts | 61 +-
arch/arm/boot/dts/imx27-phytec-phycard-s-som.dts | 42 +-
arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts | 97 +-
...ycore-som.dts => imx27-phytec-phycore-som.dtsi} | 95 +-
arch/arm/boot/dts/imx27-pinfunc.h | 526 +++++++++++
arch/arm/boot/dts/imx27.dtsi | 151 ++--
arch/arm/boot/dts/imx28-apf28dev.dts | 29 +-
arch/arm/boot/dts/imx28-apx4devkit.dts | 5 +-
arch/arm/boot/dts/imx28-cfa10036.dts | 2 +
arch/arm/boot/dts/imx28-cfa10037.dts | 7 +-
arch/arm/boot/dts/imx28-cfa10049.dts | 31 +-
arch/arm/boot/dts/imx28-cfa10057.dts | 7 +-
arch/arm/boot/dts/imx28-cfa10058.dts | 7 +-
arch/arm/boot/dts/imx28-duckbill.dts | 121 +++
arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dts | 71 ++
arch/arm/boot/dts/imx28-eukrea-mbmx287lc.dts | 50 ++
arch/arm/boot/dts/imx28-eukrea-mbmx28lc.dtsi | 326 +++++++
arch/arm/boot/dts/imx28-evk.dts | 24 +-
arch/arm/boot/dts/imx28-m28cu3.dts | 17 +-
arch/arm/boot/dts/imx28-m28evk.dts | 18 +-
arch/arm/boot/dts/imx28-sps1.dts | 7 +-
arch/arm/boot/dts/imx28-tx28.dts | 23 +-
arch/arm/boot/dts/imx28.dtsi | 65 +-
arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi | 81 ++
.../boot/dts/imx35-eukrea-mbimxsd35-baseboard.dts | 143 +++
arch/arm/boot/dts/imx35.dtsi | 359 ++++++++
arch/arm/boot/dts/imx50-evk.dts | 119 +++
arch/arm/boot/dts/imx50-pinfunc.h | 923 ++++++++++++++++++++
arch/arm/boot/dts/imx50.dtsi | 478 ++++++++++
arch/arm/boot/dts/imx51-apf51.dts | 40 +-
arch/arm/boot/dts/imx51-apf51dev.dts | 102 ++-
arch/arm/boot/dts/imx51-babbage.dts | 238 ++++-
arch/arm/boot/dts/imx51-eukrea-cpuimx51.dtsi | 93 ++
.../boot/dts/imx51-eukrea-mbimxsd51-baseboard.dts | 175 ++++
arch/arm/boot/dts/imx51.dtsi | 459 ++--------
arch/arm/boot/dts/imx53-ard.dts | 33 +-
arch/arm/boot/dts/imx53-evk.dts | 126 ---
arch/arm/boot/dts/imx53-m53evk.dts | 233 ++++-
arch/arm/boot/dts/imx53-mba53.dts | 40 +-
arch/arm/boot/dts/imx53-qsb-common.dtsi | 336 +++++++
arch/arm/boot/dts/imx53-qsb.dts | 210 +----
arch/arm/boot/dts/imx53-qsrb.dts | 158 ++++
arch/arm/boot/dts/imx53-smd.dts | 119 ++-
arch/arm/boot/dts/imx53-tqma53.dtsi | 175 +++-
arch/arm/boot/dts/imx53-tx53-x03x.dts | 315 +++++++
arch/arm/boot/dts/imx53-tx53-x13x.dts | 243 ++++++
arch/arm/boot/dts/imx53-tx53.dtsi | 511 ++++++++++-
arch/arm/boot/dts/imx53-voipac-bsb.dts | 159 ++++
arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi | 277 ++++++
arch/arm/boot/dts/imx53.dtsi | 663 +++-----------
arch/arm/boot/dts/vf610-cosmic.dts | 29 +-
arch/arm/boot/dts/vf610-twr.dts | 66 +-
arch/arm/boot/dts/vf610.dtsi | 207 +----
arch/arm/mach-mxs/mach-mxs.c | 33 +
66 files changed, 8145 insertions(+), 1767 deletions(-)
create mode 100644 arch/arm/boot/dts/imx25-eukrea-cpuimx25.dtsi
create mode 100644 arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard.dts
create mode 100644 arch/arm/boot/dts/imx25-pinfunc.h
rename arch/arm/boot/dts/{imx27-phytec-phycore-som.dts => imx27-phytec-phycore-som.dtsi} (61%)
create mode 100644 arch/arm/boot/dts/imx27-pinfunc.h
create mode 100644 arch/arm/boot/dts/imx28-duckbill.dts
create mode 100644 arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dts
create mode 100644 arch/arm/boot/dts/imx28-eukrea-mbmx287lc.dts
create mode 100644 arch/arm/boot/dts/imx28-eukrea-mbmx28lc.dtsi
create mode 100644 arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi
create mode 100644 arch/arm/boot/dts/imx35-eukrea-mbimxsd35-baseboard.dts
create mode 100644 arch/arm/boot/dts/imx35.dtsi
create mode 100644 arch/arm/boot/dts/imx50-evk.dts
create mode 100644 arch/arm/boot/dts/imx50-pinfunc.h
create mode 100644 arch/arm/boot/dts/imx50.dtsi
create mode 100644 arch/arm/boot/dts/imx51-eukrea-cpuimx51.dtsi
create mode 100644 arch/arm/boot/dts/imx51-eukrea-mbimxsd51-baseboard.dts
delete mode 100644 arch/arm/boot/dts/imx53-evk.dts
create mode 100644 arch/arm/boot/dts/imx53-qsb-common.dtsi
create mode 100644 arch/arm/boot/dts/imx53-qsrb.dts
create mode 100644 arch/arm/boot/dts/imx53-tx53-x03x.dts
create mode 100644 arch/arm/boot/dts/imx53-tx53-x13x.dts
create mode 100644 arch/arm/boot/dts/imx53-voipac-bsb.dts
create mode 100644 arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi
^ permalink raw reply
* [PATCH] ARM: s3c24xx: get rid of unneeded selects
From: Paul Bolle @ 2014-02-09 14:51 UTC (permalink / raw)
To: linux-arm-kernel
Commit c67d0f29262b ("ARM: s3c24xx: get rid of custom <mach/gpio.h>")
got rid of the Kconfig symbols S3C24XX_GPIO_EXTRA64 and
S3C24XX_GPIO_EXTRA128. It missed one select of both of these symbols, so
get rid of those now.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
---
Untested.
arch/arm/mach-s3c24xx/Kconfig | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/mach-s3c24xx/Kconfig b/arch/arm/mach-s3c24xx/Kconfig
index d876431..bb1fa603 100644
--- a/arch/arm/mach-s3c24xx/Kconfig
+++ b/arch/arm/mach-s3c24xx/Kconfig
@@ -521,7 +521,6 @@ config MACH_ANUBIS
select HAVE_PATA_PLATFORM
select S3C2440_XTAL_12000000
select S3C24XX_DCLK
- select S3C24XX_GPIO_EXTRA64
select S3C24XX_SIMTEC_PM if PM
select S3C_DEV_USB_HOST
help
@@ -562,7 +561,6 @@ config MACH_OSIRIS
select S3C2410_IOTIMING if ARM_S3C2440_CPUFREQ
select S3C2440_XTAL_12000000
select S3C24XX_DCLK
- select S3C24XX_GPIO_EXTRA128
select S3C24XX_SIMTEC_PM if PM
select S3C_DEV_NAND
select S3C_DEV_USB_HOST
--
1.8.5.3
^ permalink raw reply related
* [PATCH] ARM: OMAP2+: Remove MACH_NOKIA_N800
From: Paul Bolle @ 2014-02-09 15:01 UTC (permalink / raw)
To: linux-arm-kernel
The last caller of machine_is_nokia_n800() was removed in commit
5a87cde490e1 ("ARM: OMAP2+: Remove legacy booting support for n8x0").
That means that the Kconfig symbol MACH_NOKIA_N800 is now unused. It can
safely be removed.
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
---
Untested.
arch/arm/mach-omap2/Kconfig | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 653b489..66da3f5 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -268,9 +268,6 @@ config MACH_OMAP_3430SDP
default y
select OMAP_PACKAGE_CBB
-config MACH_NOKIA_N800
- bool
-
config MACH_NOKIA_N810
bool
@@ -281,7 +278,6 @@ config MACH_NOKIA_N8X0
bool "Nokia N800/N810"
depends on SOC_OMAP2420
default y
- select MACH_NOKIA_N800
select MACH_NOKIA_N810
select MACH_NOKIA_N810_WIMAX
select OMAP_PACKAGE_ZAC
--
1.8.5.3
^ permalink raw reply related
* [PATCH 12/28] Remove GENERIC_TIME
From: Richard Weinberger @ 2014-02-09 18:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/arm/mach-bcm/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-bcm/Kconfig b/arch/arm/mach-bcm/Kconfig
index b1aa6a9..8dd5fbf 100644
--- a/arch/arm/mach-bcm/Kconfig
+++ b/arch/arm/mach-bcm/Kconfig
@@ -19,7 +19,6 @@ config ARCH_BCM_MOBILE
select CPU_V7
select CLKSRC_OF
select GENERIC_CLOCKEVENTS
- select GENERIC_TIME
select GPIO_BCM_KONA
select SPARSE_IRQ
select TICK_ONESHOT
--
1.8.4.2
^ permalink raw reply related
* [PATCH 13/28] Remove S3C24XX_GPIO_EXTRA64
From: Richard Weinberger @ 2014-02-09 18:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/arm/mach-s3c24xx/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-s3c24xx/Kconfig b/arch/arm/mach-s3c24xx/Kconfig
index d876431..1c67f04 100644
--- a/arch/arm/mach-s3c24xx/Kconfig
+++ b/arch/arm/mach-s3c24xx/Kconfig
@@ -521,7 +521,6 @@ config MACH_ANUBIS
select HAVE_PATA_PLATFORM
select S3C2440_XTAL_12000000
select S3C24XX_DCLK
- select S3C24XX_GPIO_EXTRA64
select S3C24XX_SIMTEC_PM if PM
select S3C_DEV_USB_HOST
help
--
1.8.4.2
^ permalink raw reply related
* [PATCH 14/28] Remove MACH_SMDKC210
From: Richard Weinberger @ 2014-02-09 18:47 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
sound/soc/samsung/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/samsung/Kconfig b/sound/soc/samsung/Kconfig
index 454f41c..7ea576c 100644
--- a/sound/soc/samsung/Kconfig
+++ b/sound/soc/samsung/Kconfig
@@ -145,7 +145,7 @@ config SND_SOC_SAMSUNG_RX1950_UDA1380
config SND_SOC_SAMSUNG_SMDK_WM9713
tristate "SoC AC97 Audio support for SMDK with WM9713"
- depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || MACH_SMDKV310 || MACH_SMDKC210)
+ depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || MACH_SMDKV310)
select SND_SOC_WM9713
select SND_SAMSUNG_AC97
help
--
1.8.4.2
^ permalink raw reply related
* [PATCH 22/28] Remove S3C24XX_GPIO_EXTRA128
From: Richard Weinberger @ 2014-02-09 18:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/arm/mach-s3c24xx/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-s3c24xx/Kconfig b/arch/arm/mach-s3c24xx/Kconfig
index 1c67f04..bb1fa603 100644
--- a/arch/arm/mach-s3c24xx/Kconfig
+++ b/arch/arm/mach-s3c24xx/Kconfig
@@ -561,7 +561,6 @@ config MACH_OSIRIS
select S3C2410_IOTIMING if ARM_S3C2440_CPUFREQ
select S3C2440_XTAL_12000000
select S3C24XX_DCLK
- select S3C24XX_GPIO_EXTRA128
select S3C24XX_SIMTEC_PM if PM
select S3C_DEV_NAND
select S3C_DEV_USB_HOST
--
1.8.4.2
^ permalink raw reply related
* [PATCH 25/28] Remove MACH_SMDKV310
From: Richard Weinberger @ 2014-02-09 18:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
sound/soc/samsung/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/samsung/Kconfig b/sound/soc/samsung/Kconfig
index 7ea576c..33fd372 100644
--- a/sound/soc/samsung/Kconfig
+++ b/sound/soc/samsung/Kconfig
@@ -145,7 +145,7 @@ config SND_SOC_SAMSUNG_RX1950_UDA1380
config SND_SOC_SAMSUNG_SMDK_WM9713
tristate "SoC AC97 Audio support for SMDK with WM9713"
- depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110 || MACH_SMDKV310)
+ depends on SND_SOC_SAMSUNG && (MACH_SMDK6410 || MACH_SMDKC100 || MACH_SMDKV210 || MACH_SMDKC110)
select SND_SOC_WM9713
select SND_SAMSUNG_AC97
help
--
1.8.4.2
^ permalink raw reply related
* [PATCH 26/28] Remove LOCAL_TIMERS
From: Richard Weinberger @ 2014-02-09 18:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/arm/mach-shmobile/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig
index 3386406..c055388 100644
--- a/arch/arm/mach-shmobile/Kconfig
+++ b/arch/arm/mach-shmobile/Kconfig
@@ -8,7 +8,6 @@ config ARCH_SHMOBILE_MULTI
select CPU_V7
select GENERIC_CLOCKEVENTS
select HAVE_ARM_SCU if SMP
- select HAVE_ARM_TWD if LOCAL_TIMERS
select HAVE_SMP
select ARM_GIC
select MIGHT_HAVE_CACHE_L2X0
--
1.8.4.2
^ permalink raw reply related
* [PATCH 28/28] Remove LOCAL_TIMERS
From: Richard Weinberger @ 2014-02-09 18:48 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1391971686-9517-1-git-send-email-richard@nod.at>
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
arch/arm/mach-omap2/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
index 653b489..2817f1f 100644
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -54,7 +54,6 @@ config SOC_OMAP5
select ARM_GIC
select CPU_V7
select HAVE_ARM_SCU if SMP
- select HAVE_ARM_TWD if LOCAL_TIMERS
select HAVE_SMP
select HAVE_ARM_ARCH_TIMER
select ARM_ERRATA_798181 if SMP
--
1.8.4.2
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox