From: stefan.schick@business-consulting.de (Stefan Schick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Pin configuration
Date: Fri, 11 Nov 2011 11:48:35 +0100 [thread overview]
Message-ID: <4EBCFD83.2040402@business-consulting.de> (raw)
Hey,
I am currently working on a TDM3730 in combination with a Blizzard Base
board (http://denx-cs.de/?q=tdm3730). It is my goal to connect a CAN-Bus
and get it up and running. As driver we use the SJA1000 OF platform
which is already in my Kernel. For that we have to build a little custom
board with the SJA1000 Chip and attach it to the GPIO's or in our case
the GPMC's.
The Pin configuration is stored in the u-boot source at
"u-boot.git/board/technexion/tdm3730". I also found the code to override
the Pin configuration in the architecture specific code in the Kernel.
What I don't get is what happens between the Architecture specific Pin
configuration and the SJA1000 Driver. How does the Driver know which
Pins to use?
Regards,
Stefan
reply other threads:[~2011-11-11 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EBCFD83.2040402@business-consulting.de \
--to=stefan.schick@business-consulting.de \
--cc=kernelnewbies@lists.kernelnewbies.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).