From: Damien Riegel <damien.riegel@savoirfairelinux.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org, robh+dt@kernel.org,
shawnguo@kernel.org, kernel@pengutronix.de, wim@iguana.be,
sameo@linux.intel.com, dinh.linux@gmail.com, linux@roeck-us.net,
Arnd Bergmann <arnd@arndb.de>,
kernel@savoirfairelinux.com
Subject: Re: [PATCH v4 2/5] mfd: syscon: add a DT property to set value width
Date: Tue, 24 Nov 2015 11:24:39 -0500 [thread overview]
Message-ID: <20151124162439.GC4616@localhost> (raw)
In-Reply-To: <20151124082036.GE807@x1>
On Tue, Nov 24, 2015 at 08:20:36AM +0000, Lee Jones wrote:
> On Mon, 23 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 "bus-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 adjust the register stride to
> > bus-width / 8. If not provided, the default configuration is used.
> >
> > Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> > ---
> > Documentation/devicetree/bindings/mfd/syscon.txt | 3 +++
> > drivers/mfd/syscon.c | 13 +++++++++++++
> > 2 files changed, 16 insertions(+)
>
> Works for me.
>
> For my own reference:
> Acked-by: Lee Jones <lee.jones@linaro.org>
This pachset requires a new version to fix something in the watchdog,
I will add your Ack in the v5.
>
> How would you like this set to be handled?
>
Not sure what you mean. Actually, I don't know how it works for such
patchset with changes across multiple subsystems. What are the options?
Damien
WARNING: multiple messages have this Message-ID (diff)
From: damien.riegel@savoirfairelinux.com (Damien Riegel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/5] mfd: syscon: add a DT property to set value width
Date: Tue, 24 Nov 2015 11:24:39 -0500 [thread overview]
Message-ID: <20151124162439.GC4616@localhost> (raw)
In-Reply-To: <20151124082036.GE807@x1>
On Tue, Nov 24, 2015 at 08:20:36AM +0000, Lee Jones wrote:
> On Mon, 23 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 "bus-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 adjust the register stride to
> > bus-width / 8. If not provided, the default configuration is used.
> >
> > Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> > ---
> > Documentation/devicetree/bindings/mfd/syscon.txt | 3 +++
> > drivers/mfd/syscon.c | 13 +++++++++++++
> > 2 files changed, 16 insertions(+)
>
> Works for me.
>
> For my own reference:
> Acked-by: Lee Jones <lee.jones@linaro.org>
This pachset requires a new version to fix something in the watchdog,
I will add your Ack in the v5.
>
> How would you like this set to be handled?
>
Not sure what you mean. Actually, I don't know how it works for such
patchset with changes across multiple subsystems. What are the options?
Damien
next prev parent reply other threads:[~2015-11-24 16:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:17 [PATCH v4 0/5] Add board support for TS-4800 Damien Riegel
2015-11-23 15:17 ` Damien Riegel
2015-11-23 15:17 ` [PATCH v4 1/5] of: add vendor prefix for Technologic Systems Damien Riegel
2015-11-23 15:17 ` Damien Riegel
2015-11-23 15:17 ` [PATCH v4 2/5] mfd: syscon: add a DT property to set value width Damien Riegel
2015-11-23 15:17 ` Damien Riegel
2015-11-23 15:19 ` Arnd Bergmann
2015-11-23 15:19 ` Arnd Bergmann
2015-11-24 8:20 ` Lee Jones
2015-11-24 8:20 ` Lee Jones
2015-11-24 16:24 ` Damien Riegel [this message]
2015-11-24 16:24 ` Damien Riegel
2015-11-24 17:22 ` Lee Jones
2015-11-24 17:22 ` Lee Jones
2015-11-24 17:22 ` Lee Jones
2015-11-24 17:23 ` Lee Jones
2015-11-24 17:23 ` Lee Jones
2015-11-24 17:23 ` Lee Jones
2015-11-23 15:17 ` [PATCH v4 3/5] watchdog: ts4800: add driver for TS-4800 watchdog Damien Riegel
2015-11-23 15:17 ` Damien Riegel
2015-11-24 2:32 ` Guenter Roeck
2015-11-24 2:32 ` Guenter Roeck
2015-11-24 2:55 ` Damien Riegel
2015-11-24 2:55 ` Damien Riegel
2015-11-23 15:17 ` [PATCH v4 4/5] ARM: imx_v6_v7_defconfig: add " Damien Riegel
2015-11-23 15:17 ` Damien Riegel
2015-11-23 15:17 ` [PATCH v4 5/5] ARM: dts: TS-4800: add basic device tree Damien Riegel
2015-11-23 15:17 ` 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=20151124162439.GC4616@localhost \
--to=damien.riegel@savoirfairelinux.com \
--cc=arnd@arndb.de \
--cc=dinh.linux@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@savoirfairelinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
--cc=shawnguo@kernel.org \
--cc=wim@iguana.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.