From: Scott Wood <oss@buserror.net>
To: "Nora Björklund" <Nora.Bjorklund@enea.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: GPIO expander for p2041
Date: Tue, 08 Mar 2016 18:26:16 -0600 [thread overview]
Message-ID: <1457483176.5360.121.camel@buserror.net> (raw)
In-Reply-To: <1456846859.1203.6.camel@enea.com>
On Tue, 2016-03-01 at 15:41 +0000, Nora Björklund wrote:
> Hi,
>
> 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 a 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, but it seems to be the same for the
> one I obtained from
> git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git).
>
> Would this patch be of any interest for the upstream powerpc kernel?
> 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.
In theory the device tree should completely describe the hardware, regardless
of what Linux looks for, but in practice some things get missed and then get
added as they're needed.
Yes, a patch would be welcome.
-Scott
prev parent reply other threads:[~2016-03-09 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 15:41 GPIO expander for p2041 Nora Björklund
2016-03-09 0:26 ` Scott Wood [this message]
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=1457483176.5360.121.camel@buserror.net \
--to=oss@buserror.net \
--cc=Nora.Bjorklund@enea.com \
--cc=linuxppc-dev@lists.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).