From: Sebastian Reichel <sre@debian.org>
To: Tony Lindgren <tony@atomide.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Shubhrajyoti Datta" <omaplinuxkernel@gmail.com>,
"Carlos Chinea" <cch.devel@gmail.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Kevin Hilman" <khilman@deeprootsystems.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Grant Likely" <grant.likely@linaro.org>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Rob Landley" <rob@landley.net>,
"'Benoît Cousson'" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [RFCv2 3/3] ARM: dts: N900: Add SSI information
Date: Thu, 21 Nov 2013 03:21:27 +0100 [thread overview]
Message-ID: <20131121022125.GA2445@earth.universe> (raw)
In-Reply-To: <20131121013858.GK10317@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]
Hi Tony,
On Wed, Nov 20, 2013 at 05:38:59PM -0800, Tony Lindgren wrote:
> * Sebastian Reichel <sre@debian.org> [130915 13:56]:
> > +
> > +Example for Nokia N900:
> > +
> > +ssi-controller@48058000 {
> > + compatible = "ti,omap3-ssi";
> > + ti,hwmods = "ssi";
> > +
> > + reg = <0x48058000 0x1000>,
> > + <0x48059000 0x1000>;
> > + reg-names = "sys",
> > + "gdd";
> > +
> > + interrupts = <55>;
> > + interrupt-names = "gdd_mpu";
> > +
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + ranges;
> > +
> > + ssi-port@0 {
> > + compatible = "ti,omap3-ssi-port";
> > +
> > + reg = <0x4805a000 0x800>,
> > + <0x4805a800 0x800>;
> > + reg-names = "tx",
> > + "rx";
> > +
> > + interrupt-parent = <&intc>;
> > + interrupts = <51>,
> > + <52>;
> > + interrupt-names = "mpu_irq0",
> > + "mpu_irq1";
> > +
> > + ti,ssi-cawake-gpio = <&gpio5 23 GPIO_ACTIVE_HIGH>; /* 151 */
> > + }
> > +}
>
> These should be in the omap3.dtsi file and not nested but separate. I'm almost
> certain that these are completely independent hardware modules and this
> means they can live their own PM life independently.
>
> So can you please do a minimal patch for omap3.dtsi that just sets up
> the standard resources separately for both modules the same way we have
> for other hardware modules in omap3.dtsi do?
>
> One of them should be called ssi, no idea what the other module name should
> be as those register ranges show up as reserved in the docs I have.
In the public documentation of the omaps all SSI related stuff is
missing and memory areas are marked as reserved. I could not find
out how to receive the NDA version, so the following is purely
speculation based on the code.
If I understand it right the HW looks like this:
+-----------------+
| GDD (DMA) | <- this one is currently called ssi-controller
+--------+--------+
| Port 1 | Port 2 | <- these are currently called ssi-port
+--------+--------+
I think the GDD part must be enabled while Port 1 or Port 2 is
enabled. The last RFC driver from Carlos did not even split up the
irq/memory areas into different platform devices, but just requested
all of them in one ssi platform device.
> The other binding pieces can be added later on as they get are ready.
Sure. They are almost finished btw. I was able to get a gsm network
scan.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-21 2:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 20:44 [RFCv2 0/3] OMAP SSI driver Sebastian Reichel
[not found] ` <1379277856-24571-1-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-09-15 20:44 ` [RFCv2 1/3] ARM: OMAP2+: hwmod-data: Add SSI information Sebastian Reichel
2013-09-15 20:44 ` [RFCv2 3/3] ARM: dts: N900: " Sebastian Reichel
2013-09-16 13:05 ` Javier Martinez Canillas
2013-09-16 15:01 ` Sebastian Reichel
2013-09-16 17:25 ` Javier Martinez Canillas
[not found] ` <20130916150147.GA14047-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2013-09-16 18:10 ` Aaro Koskinen
[not found] ` <20130916181032.GB30568-R3WNPi76c83LsdW6vOPryG4HOFkwEHDbMR2xtNvyitY@public.gmane.org>
2013-09-16 19:27 ` Sebastian Reichel
2013-09-16 13:11 ` Nishanth Menon
2013-09-23 20:35 ` Stephen Warren
[not found] ` <5240A617.1010208-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-23 23:46 ` Sebastian Reichel
[not found] ` <20130923234656.GB24781-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2013-09-24 19:55 ` Stephen Warren
2013-09-24 20:10 ` Tony Lindgren
2013-11-21 1:38 ` Tony Lindgren
2013-11-21 2:21 ` Sebastian Reichel [this message]
2013-11-21 20:46 ` Tony Lindgren
2013-11-21 23:38 ` Sebastian Reichel
2013-09-15 20:44 ` [RFCv2 2/3] ARM: OMAP2+: HSI: Introduce OMAP SSI driver Sebastian Reichel
[not found] ` <1379277856-24571-3-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-09-18 19:23 ` Tony Lindgren
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=20131121022125.GA2445@earth.universe \
--to=sre@debian.org \
--cc=bcousson@baylibre.com \
--cc=cch.devel@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=omaplinuxkernel@gmail.com \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).