From: Tim Sander <tim@krieglstein.org>
To: linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Pinmuxing with devicetree (beaglebone)
Date: Sun, 21 Apr 2013 11:43:50 +0200 [thread overview]
Message-ID: <201304211143.50961.tim@krieglstein.org> (raw)
Hi
I am currently trying to get pinmuxing working on a beaglebone board with an
offtree driver. This is for a custom handbuild hardware so i guess there is no
point in bringing this mainline.
While this is havyly patched 3.8.4 version running over here i think the
pinmux infrastructure is the new standard way. At least there is a
pinctrl/44e10800.pinmux directory in debugfs?
My last aproach was using the devicetree but beeing new to this devicetree
stuff i just got stuck:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/231204
Now i tried use the way it is described in Documentation/pinctrl.txt but still
there are the includes missing: #include <linux/pinctrl/consumer.h>.
Also while there is a /sys/kernel/debug/pinctrl/44e10800.pinmux in debugfs i
found that not so intuitive as the omap_mux which disappeared. Also i didn't
find any documentation for this debugfs stuff.
So what is the recommended way to get this stupid pinmuxing going. In pre
devicetree days one would just pick the mux.h include of the platform and
initialized the muxers which was pretty straight forward. Now with device tree
its much more complicated. No proper syntax checking as with the c definitions
and no documentation how to get this magic stuff working :-(.
The whole stuff is build by a ptxdist (a embedded buildsystem) and can be
found over here:
https://gitorious.org/ptxdist-beaglebone/ptxdist-beaglebone
Best regards
Tim
next reply other threads:[~2013-04-21 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 9:43 Tim Sander [this message]
2013-04-22 15:33 ` Haojian Zhuang
2013-05-01 22:24 ` Tim Sander
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=201304211143.50961.tim@krieglstein.org \
--to=tim@krieglstein.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®