From: Martin Sperl <kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
To: "Mark Brown" <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Noralf Trønnes" <noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
Cc: "linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Re: spi: bcm2835: driver for "auxiliar" spi1/spi2
Date: Thu, 18 Jun 2015 13:37:11 +0200 [thread overview]
Message-ID: <5582AD67.9020503@martin.sperl.org> (raw)
In-Reply-To: <20150618105848.GE14071-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 2015-06-18 12:58, Mark Brown wrote:
> On Thu, Jun 18, 2015 at 12:19:04PM +0200, Noralf Trønnes wrote:
> Linux supports shared interrupts perfectly fine, though it sounds like
> this is actually a cascaded interrupt (the demux is another interrupt
> controller) which we also support just fine.
So we need to move the route of using a cascaded demux interrupt handler
for interrupt separation.
The other thing is: is there a "framework" to handle access to the
the "enable" register shared by all three devices (spi1/spi2/uart1),
or do we have to create a tiny module (aux-bcm2835 or similar) to
serialize access to this register?
For the moment I will start focusing on the implementation itself while
we can figure out the interrupt-controller configuration in DT in
parallel...
We also should look into upstreaming the configuration of uart1 - even
if only available on the compute board...
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-18 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 9:45 spi: bcm2835: driver for "auxiliar" spi1/spi2 Martin Sperl
[not found] ` <5582933E.1050500-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2015-06-18 10:19 ` Noralf Trønnes
[not found] ` <55829B18.4030609-L59+Z2yzLopAfugRpC6u6w@public.gmane.org>
2015-06-18 10:58 ` Mark Brown
[not found] ` <20150618105848.GE14071-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-06-18 11:37 ` Martin Sperl [this message]
2015-06-25 17:42 ` Jakub Kiciński
2015-07-07 13:51 ` Mark Brown
2015-06-18 10:38 ` 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=5582AD67.9020503@martin.sperl.org \
--to=kernel-tqfnsx0mhmxhksadf0wuew@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 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.