From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] spi: orion.c: Add direct access mode
Date: Tue, 29 Mar 2016 22:04:59 +0200 [thread overview]
Message-ID: <7339827.UeYZLZET5g@wuerfel> (raw)
In-Reply-To: <20160329195230.GK2350@sirena.org.uk>
On Tuesday 29 March 2016 12:52:30 Mark Brown wrote:
> On Tue, Mar 29, 2016 at 09:49:09PM +0200, Arnd Bergmann wrote:
> > On Tuesday 29 March 2016 09:47:58 Mark Brown wrote:
>
> > > Well, in the cases where we have one device on the bus then it's not a
> > > big deal since we can check what the last thing we set was. The direct
> > > access stuff is going to have trouble if we have multiple devices on the
> > > bus since we try to mix it with non-MMIO access we run the risk of
> > > conflicting simultaneous use unless we continue to route everything
> > > through the SPI subsystem (like we do with the current flash read
> > > support).
>
> > Maybe we can avoid that if we enforce at the driver level that we
> > use the same mode for all slaves? The way I read the manual, I think
> > that's how it is intended at least.
>
> Well, we currently don't have any XIP or whatever support at all, it's
> still only in the SPI operations so it's academic - that'd be a future
> issue if we did start doing things that accessed the memory map outside
> of the SPI flow.
Isn't this just about implementing .point()/.unpoint() in the spi-nor
driver?
> > Also, as mentioned we don't have any machine with more than one SPI
> > slave so far, so we don't really need to overengineer it and can
> > go for the simplest implementation in the SPI master driver.
>
> For me the simplest thing seems like just using one window for all the
> devices, it seems more likely to deliver useful results without the
> system integrator having to think about how to configure this for
> optimisation.
Do you mean single-window mode? I don't see the difference to the other
modes, but that's certainly fine with me if it helps.
Arnd
next prev parent reply other threads:[~2016-03-29 20:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 16:24 [PATCH v2] spi: orion.c: Add direct access mode Stefan Roese
2016-03-22 16:35 ` Thomas Petazzoni
2016-03-22 16:44 ` Stefan Roese
2016-03-23 11:33 ` Mark Brown
2016-03-23 11:59 ` Stefan Roese
2016-03-23 12:54 ` Mark Brown
2016-03-23 13:10 ` Stefan Roese
2016-03-23 13:26 ` Andrew Lunn
2016-03-23 13:36 ` Mark Brown
2016-03-23 13:56 ` Andrew Lunn
2016-03-23 19:51 ` Arnd Bergmann
2016-03-24 7:22 ` Stefan Roese
2016-03-24 12:42 ` Arnd Bergmann
2016-03-24 16:15 ` Stefan Roese
2016-03-24 16:42 ` Arnd Bergmann
2016-03-24 17:30 ` Stefan Roese
2016-03-24 16:48 ` Arnd Bergmann
2016-03-24 17:51 ` Stefan Roese
2016-03-24 20:07 ` Arnd Bergmann
2016-03-25 10:32 ` Mark Brown
2016-03-25 15:11 ` Arnd Bergmann
2016-03-25 15:50 ` Mark Brown
2016-03-25 20:58 ` Arnd Bergmann
2016-03-25 22:39 ` Mark Brown
2016-03-29 12:39 ` Arnd Bergmann
2016-03-29 16:47 ` Mark Brown
2016-03-29 19:49 ` Arnd Bergmann
2016-03-29 19:52 ` Mark Brown
2016-03-29 20:04 ` Arnd Bergmann [this message]
2016-03-29 21:00 ` Mark Brown
2016-03-29 21:08 ` Arnd Bergmann
2016-03-29 21:28 ` Mark Brown
2016-03-29 22:04 ` Arnd Bergmann
2016-04-05 7:11 ` Stefan Roese
2016-04-05 13:15 ` Andrew Lunn
2016-04-05 13:20 ` Stefan Roese
2016-04-05 13:31 ` Andrew Lunn
2016-03-23 13:27 ` Mark Brown
2016-03-23 17:25 ` Stefan Roese
2016-03-23 18:29 ` Mark Brown
2016-03-23 18:39 ` Andrew Lunn
2016-03-24 5:45 ` Stefan Roese
2016-03-24 11:23 ` Mark Brown
2016-03-24 12:05 ` Stefan Roese
2016-03-22 17:39 ` Mark Brown
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=7339827.UeYZLZET5g@wuerfel \
--to=arnd@arndb.de \
--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