linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/6] mfd: syscon: add a DT property to set value width
Date: Tue, 8 Dec 2015 14:18:56 +0000	[thread overview]
Message-ID: <20151208141856.GA14365@x1> (raw)
In-Reply-To: <20151208135040.GH3384@x1>

On Tue, 08 Dec 2015, Lee Jones wrote:

> On Mon, 07 Dec 2015, Damien Riegel wrote:
> 
> > On Mon, Dec 07, 2015 at 09:40:20AM +0000, Lee Jones wrote:
> > > On Mon, 30 Nov 2015, Damien Riegel wrote:
> > > 
> > > > Currently syscon has a fixed configuration of 32 bits for register and
> > > > values widths. In some cases, it would be desirable to be able to
> > > > customize the value width.
> > > > 
> > > > For example, certain boards (like the ones manufactured by Technologic
> > > > Systems) have a FPGA that is memory-mapped, but its registers are only
> > > > 16-bit wide.
> > > > 
> > > > This patch adds an optional "reg-io-width" DT binding for syscon that
> > > > allows to change the width for the data bus (i.e. val_bits). If this
> > > > property is provided, it will also set the register stride to
> > > > reg-io-width's value. If not provided, the default configuration is
> > > > used.
> > > > 
> > > > Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> > > > ---
> > > >  Documentation/devicetree/bindings/mfd/syscon.txt |  4 ++++
> > > >  drivers/mfd/syscon.c                             | 13 +++++++++++++
> > > >  2 files changed, 17 insertions(+)
> > > 
> > > Applied, thanks.
> > > 
> > Hi Lee,
> > 
> > Good to see this patch applied. What's going on now with the other
> > patches of this serie ? How should I handle them ?
> 
> Are there any build dependencies between them?

Looks like Arnd already replied.

I really should refresh my mail before replying. :)

> > > > diff --git a/Documentation/devicetree/bindings/mfd/syscon.txt b/Documentation/devicetree/bindings/mfd/syscon.txt
> > > > index fe8150b..408f768 100644
> > > > --- a/Documentation/devicetree/bindings/mfd/syscon.txt
> > > > +++ b/Documentation/devicetree/bindings/mfd/syscon.txt
> > > > @@ -13,6 +13,10 @@ Required properties:
> > > >  - compatible: Should contain "syscon".
> > > >  - reg: the register region can be accessed from syscon
> > > >  
> > > > +Optional property:
> > > > +- reg-io-width: the size (in bytes) of the IO accesses that should be
> > > > +  performed on the device.
> > > > +
> > > >  Examples:
> > > >  gpr: iomuxc-gpr at 020e0000 {
> > > >  	compatible = "fsl,imx6q-iomuxc-gpr", "syscon";
> > > > diff --git a/drivers/mfd/syscon.c b/drivers/mfd/syscon.c
> > > > index 176bf0f..b7aabee 100644
> > > > --- a/drivers/mfd/syscon.c
> > > > +++ b/drivers/mfd/syscon.c
> > > > @@ -47,6 +47,7 @@ static struct syscon *of_syscon_register(struct device_node *np)
> > > >  	struct syscon *syscon;
> > > >  	struct regmap *regmap;
> > > >  	void __iomem *base;
> > > > +	u32 reg_io_width;
> > > >  	int ret;
> > > >  	struct regmap_config syscon_config = syscon_regmap_config;
> > > >  
> > > > @@ -69,6 +70,18 @@ static struct syscon *of_syscon_register(struct device_node *np)
> > > >  	 else if (of_property_read_bool(np, "little-endian"))
> > > >  		syscon_config.val_format_endian = REGMAP_ENDIAN_LITTLE;
> > > >  
> > > > +	/*
> > > > +	 * search for reg-io-width property in DT. If it is not provided,
> > > > +	 * default to 4 bytes. regmap_init_mmio will return an error if values
> > > > +	 * are invalid so there is no need to check them here.
> > > > +	 */
> > > > +	ret = of_property_read_u32(np, "reg-io-width", &reg_io_width);
> > > > +	if (ret)
> > > > +		reg_io_width = 4;
> > > > +
> > > > +	syscon_config.reg_stride = reg_io_width;
> > > > +	syscon_config.val_bits = reg_io_width * 8;
> > > > +
> > > >  	regmap = regmap_init_mmio(NULL, base, &syscon_config);
> > > >  	if (IS_ERR(regmap)) {
> > > >  		pr_err("regmap init failed\n");
> > > 
> 

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2015-12-08 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 15:59 [PATCH v7 0/6] Add board support for TS-4800 Damien Riegel
2015-11-30 15:59 ` [PATCH v7 1/6] of: add vendor prefix for Technologic Systems Damien Riegel
2015-11-30 15:59 ` [PATCH v7 2/6] mfd: syscon: add a DT property to set value width Damien Riegel
2015-11-30 19:00   ` Rob Herring
2015-12-02 23:21     ` Damien Riegel
2015-12-04 16:02       ` Arnd Bergmann
2015-12-07  9:40   ` Lee Jones
2015-12-07 19:42     ` Damien Riegel
2015-12-08 10:02       ` Arnd Bergmann
2015-12-08 13:50       ` Lee Jones
2015-12-08 14:18         ` Lee Jones [this message]
2015-11-30 15:59 ` [PATCH v7 3/6] watchdog: ts4800: add driver for TS-4800 watchdog Damien Riegel
2015-11-30 16:14   ` Guenter Roeck
2015-12-04 18:49     ` Damien Riegel
2015-11-30 19:01   ` Rob Herring
2015-11-30 15:59 ` [PATCH v7 4/6] ARM: imx_v6_v7_defconfig: add " Damien Riegel
2015-11-30 15:59 ` [PATCH v7 5/6] of: documentation: add bindings documentation for TS-4800 Damien Riegel
2015-11-30 15:59 ` [PATCH v7 6/6] ARM: dts: TS-4800: add basic device tree Damien Riegel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151208141856.GA14365@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).