From: "Nora Björklund" <Nora.Bjorklund@enea.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: [meta-fsl-ppc]: Enable gpio expander for p2041?
Date: Mon, 7 Mar 2016 13:24:31 +0000 [thread overview]
Message-ID: <1457357041.1382.17.camel@enea.com> (raw)
Hi all,
I was working on a p2041rdb target not so long ago and needed to use
the gpio pins (described in detail in the p2041 reference manual),
these are visible on the p2041 fact sheet [1]. The pins are connected
to a gpio expander, PCA9672 [2], which is connected to an i2c-bus.
The expander was not available in the device-tree for p2041rdb so I
patched it locally to include it. The gpio-expander does not seem to be
available in any upstream repository either (at this time I was working
on a version of the 3.12 kernel).
Would this patch be of any interest for meta-fsl-ppc?
The gpio pins are there on all p2041rdb targets (at least since they
are mentioned as such in the reference guide), so I could not come up
with a reason to why it is excluded from the device tree.
Best Regards,
Nora Björklund
-----------------------------
[1] http://cache.nxp.com/files/32bit/doc/fact_sheet/P2041RDBFS.pdf?fpsp
=1&WT_TYPE=Fact%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSE
T=Documentation&fileExt=.pdf (login might be required)
[2] http://www.nxp.com/products/interface-and-connectivity/interface-an
d-system-management/i2c/i2c-general-purpose-i-o/remote-8-bit-i-o-
expander-for-fm-plus-ic-bus-with-interrupt-and-reset:PCA9672
next reply other threads:[~2016-03-07 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 13:24 Nora Björklund [this message]
2016-03-09 9:52 ` [meta-fsl-ppc]: Enable gpio expander for p2041? Zhenhua Luo
2016-03-09 12:34 ` Nora Björklund
2016-03-10 8:26 ` Zhenhua Luo
2016-03-10 9:29 ` Zhenhua Luo
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=1457357041.1382.17.camel@enea.com \
--to=nora.bjorklund@enea.com \
--cc=meta-freescale@yoctoproject.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.