From: "Henk Stegeman" <henk.stegeman@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Chipselect in SPI binding with mpc5200-psc-spi
Date: Wed, 29 Oct 2008 14:43:32 +0100 [thread overview]
Message-ID: <ae4f76fd0810290643o27c357d7k2ccde459d9e52a7b@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
..
..
In my dts
I have my chipselect defined as follows:
gpt4: timer@640 { // General Purpose Timer GPT4 in GPIO mode for
SMC4000IO chip select.
compatible = "fsl,mpc5200b-gpt-gpio","fsl,mpc5200-gpt-gpio";
cell-index = <4>;
reg = <0x640 0x10>;
interrupts = <1 13 0>;
interrupt-parent = <&mpc5200_pic>;
gpio-controller;
#gpio-cells = <2>;
};
I found the gpio in
# cat /sys/class/gpio/gpiochip215/label
/soc5200@f0000000/timer@640
The spi controller is defined like this:
spi@2400 {
device_type = "spi";
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,mpc5200-psc-spi","fsl,mpc5200b-psc-spi";
cell-index = <2>;
reg = <2400 100>;
interrupts = <2 3 0>;
interrupt-parent = <&mpc5200_pic>;
gpios = <&gpt4 0 0>;
io-controller@0 {
compatible = "microkey,smc4000io";
spi-max-frequency = <1000000>;
reg = <0>;
};
};
At bootup linux (2.6.27) reports:
mpc52xx-psc-spi f0000960.spi: probe called without platform data, no
(de)activate_cs function will be called.
Is my assumption wrong that the gpios property is the way to map chipselects
to the spi driver?
Thanks in advance.
Henk.
[-- Attachment #2: Type: text/html, Size: 2834 bytes --]
next reply other threads:[~2008-10-29 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 13:43 Henk Stegeman [this message]
2008-10-29 14:45 ` Chipselect in SPI binding with mpc5200-psc-spi Grant Likely
2009-02-13 10:40 ` Henk Stegeman
2009-02-13 15:19 ` Grant Likely
2009-02-13 15:52 ` Henk Stegeman
2009-06-15 16:36 ` Kári Davíðsson
2009-06-15 17:31 ` Grant Likely
2009-06-16 10:41 ` Kári Davíðsson
2009-07-07 14:31 ` Henk Stegeman
2009-07-07 15:57 ` Grant Likely
2009-07-08 13:07 ` Henk Stegeman
2009-03-27 21:14 Yann Pelletier
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=ae4f76fd0810290643o27c357d7k2ccde459d9e52a7b@mail.gmail.com \
--to=henk.stegeman@gmail.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).