From: Mark Brown <broonie@kernel.org>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: atull <atull@opensource.altera.com>,
jgunthorpe@obsidianresearch.com, hpa@zytor.com, monstr@monstr.eu,
michal.simek@xilinx.com, rdunlap@infradead.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, pantelis.antoniou@konsulko.com,
robh+dt@kernel.org, grant.likely@linaro.org,
iws@ovro.caltech.edu, linux-doc@vger.kernel.org, pavel@denx.de,
philip@balister.org, rubini@gnudd.com, jason@lakedaemon.net,
kyle.teske@ni.com, nico@linaro.org, balbi@ti.com,
m.chehab@samsung.com, davidb@codeaurora.org, rob@landley.net,
davem@davemloft.net, cesarb@cesarb.net, sameo@linux.intel.com,
akpm@linux-foundation.org, linus.walleij@linaro.org,
mgerlach@opensource.altera.com, delicious.quinoa@gmail.com,
dinguyen@opensource.altera.com, yvanderv@opensource.altera.com
Subject: Re: [PATCH v2 2/3] ARM: dts: socfpga: fpga bridges bindings docs
Date: Wed, 29 Oct 2014 10:16:32 +0000 [thread overview]
Message-ID: <20141029101632.GU18557@sirena.org.uk> (raw)
In-Reply-To: <20141029075701.GA10262@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Wed, Oct 29, 2014 at 08:57:01AM +0100, Steffen Trumtrar wrote:
> So, that shouldn't be a problem though, as I already cooked up a driver for
> the L3 with all the ranges specified. The only thing I need to figure out
> before I will post it, is how to nicely handle the WO remap register.
> I think regmap might be able to handle this itself, but am not sure yet.
It's supposed to be able to, not sure if anyone really tests that or not
though so it's possible bugs crept in. Most write only registers can
physically be read so actually come out as volatile rather than write
only even if functionally there is no reason to read.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-29 10:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 23:51 [PATCH v2 0/3] fpga bridge framework atull
2014-10-23 23:51 ` [PATCH v2 1/3] add sysfs document for fpga bridges atull
2014-10-24 10:54 ` Pavel Machek
2014-10-24 15:11 ` atull
2014-10-29 8:25 ` Pavel Machek
2014-10-23 23:51 ` [PATCH v2 2/3] ARM: dts: socfpga: fpga bridges bindings docs atull
2014-10-24 7:00 ` Steffen Trumtrar
2014-10-24 9:20 ` Pantelis Antoniou
2014-10-25 14:42 ` Steffen Trumtrar
2014-10-27 11:54 ` Pantelis Antoniou
2014-10-27 15:23 ` Steffen Trumtrar
2014-10-27 15:52 ` Pantelis Antoniou
2014-10-27 17:47 ` Steffen Trumtrar
2014-10-28 21:19 ` atull
2014-10-28 21:53 ` atull
2014-10-29 7:57 ` Steffen Trumtrar
2014-10-29 10:16 ` Mark Brown [this message]
2014-10-29 10:31 ` Steffen Trumtrar
2014-10-29 14:30 ` atull
2014-10-29 20:49 ` atull
2014-10-29 8:24 ` Pavel Machek
2014-10-29 20:39 ` atull
2014-10-24 10:57 ` Pavel Machek
2014-10-27 11:48 ` Pantelis Antoniou
2014-10-27 15:01 ` Mark Brown
2014-10-27 15:05 ` Pantelis Antoniou
2014-10-27 15:32 ` Steffen Trumtrar
2014-10-27 15:45 ` Pantelis Antoniou
2014-10-27 17:17 ` Mark Brown
2014-10-27 17:21 ` Pantelis Antoniou
2014-10-27 18:00 ` Steffen Trumtrar
2014-10-27 18:03 ` Pantelis Antoniou
2014-10-23 23:51 ` [PATCH v2 3/3] fpga bridge driver atull
2014-10-27 11:37 ` Pantelis Antoniou
2014-10-23 23:57 ` [PATCH v2 0/3] fpga bridge framework atull
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=20141029101632.GU18557@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=atull@opensource.altera.com \
--cc=balbi@ti.com \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=iws@ovro.caltech.edu \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kyle.teske@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mgerlach@opensource.altera.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=nico@linaro.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=pavel@denx.de \
--cc=philip@balister.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=rubini@gnudd.com \
--cc=s.trumtrar@pengutronix.de \
--cc=sameo@linux.intel.com \
--cc=yvanderv@opensource.altera.com \
/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
all inboxes | Powered by JetHome®