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, shawnguo@kernel.org,
kernel@pengutronix.de, wim@iguana.be, robh+dt@kernel.org,
sameo@linux.intel.com, dinh.linux@gmail.com, linux@roeck-us.net,
kernel@savoirfairelinux.com, arnd@arndb.de
Subject: Re: [PATCH v2 2/5] mfd: ts4800-syscon: add driver for TS-4800 syscon
Date: Mon, 2 Nov 2015 13:13:34 -0500 [thread overview]
Message-ID: <20151102181334.GA7200@localhost> (raw)
In-Reply-To: <20151102091253.GS4058@x1>
On Mon, Nov 02, 2015 at 09:12:53AM +0000, Lee Jones wrote:
> [Cc'ing Arnd]
>
> On Fri, 30 Oct 2015, Damien Riegel wrote:
> > On Fri, Oct 30, 2015 at 05:56:56PM +0000, Lee Jones wrote:
> > > On Thu, 29 Oct 2015, Damien Riegel wrote:
> > >
> > > > Driver for TS-4800 syscon. These registers belong to a FPGA that is
> > > > memory mapped and are used for counters, enable various IPs in the FPGA,
> > > > control LEDs, control IOs, etc.
> > > >
> > > > Currently, only the watchdog is handled.
> > >
> > > Why do you require your own syscon driver?
> > >
> > > What's wrong with the generic one?
> > >
> >
> > The generic one uses a regmap_config with reg_stride set to 4 and val_bits
> > to 32.
> >
> > TS-4800 syscon registers are 16-bit wide and must be accessed with 16
> > bit read and writes:
> > http://wiki.embeddedarm.com/wiki/TS-4800#Syscon
> >
> > I will address the other issues in the next version (split commit,
> > license issue, style, and superfluous remove).
>
> The Syscon driver was written to be generic so that each
> vendor/platform didn't require their own incarnation. How unique is
> the TS-4800?
>
> Perhaps it might be better to supply a generic 16 bit Syscon for
> devices akin to the TS-4800?
The TS-4800 syscon could use a generic 16-bit syscon. There is nothing
specific that requires a driver besides that.
We could add some optional properties to the generic syscon node to
configure reg_bits, val_bits, and reg_stride (and pad_bits ?). Would
that be a good solution ?
> Arnd, any opinion on this?
>
next prev parent reply other threads:[~2015-11-02 18:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:27 [PATCH v2 0/5] Add board support for TS-4800 Damien Riegel
2015-10-29 20:27 ` [PATCH v2 1/5] of: add vendor prefix for Technologic Systems Damien Riegel
2015-10-30 18:04 ` Lee Jones
2015-10-30 19:58 ` Damien Riegel
2015-11-02 9:13 ` Lee Jones
2015-10-29 20:27 ` [PATCH v2 2/5] mfd: ts4800-syscon: add driver for TS-4800 syscon Damien Riegel
2015-10-30 17:56 ` Lee Jones
2015-10-30 20:08 ` Damien Riegel
2015-11-02 9:12 ` Lee Jones
2015-11-02 18:13 ` Damien Riegel [this message]
2015-11-03 8:38 ` Lee Jones
2015-11-03 8:39 ` Lee Jones
2015-11-03 8:40 ` Arnd Bergmann
2015-11-03 10:12 ` Lee Jones
2015-11-03 10:48 ` Arnd Bergmann
2015-11-03 14:36 ` Damien Riegel
2015-10-29 20:27 ` [PATCH v2 3/5] watchdog: ts4800: add driver for TS-4800 watchdog Damien Riegel
2015-10-30 17:28 ` Lee Jones
2015-10-30 17:52 ` Lee Jones
2015-10-29 20:27 ` [PATCH v2 4/5] ARM: imx_v6_v7_defconfig: add TS-4800 watchdog and syscon Damien Riegel
2015-10-29 20:27 ` [PATCH v2 5/5] 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=20151102181334.GA7200@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox