From: Michael Welling <mwelling@ieee.org>
To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Adding MAX1363 to BBB
Date: Thu, 27 Aug 2015 14:16:17 -0500 [thread overview]
Message-ID: <20150827191616.GA8285@deathstar> (raw)
In-Reply-To: <782E3A02C2EB2347BEA6DEA69DC7AB86021D3CBD498E@sfamail.SAKURAUS.LOCAL>
On Thu, Aug 27, 2015 at 12:10:06PM -0700, Greg Wilson-Lindberg wrote:
>
>
> > -----Original Message-----
> > From: Michael Welling [mailto:mwelling79@gmail.com] On Behalf
> > Of Michael Welling
> > Sent: Monday, August 24, 2015 9:55 AM
> > To: Greg Wilson-Lindberg
> > Cc: linux-iio@vger.kernel.org
> > Subject: Re: Adding MAX1363 to BBB
> >
> > On Mon, Aug 24, 2015 at 09:26:53AM -0700, Greg Wilson-Lindberg wrote:
> > > I don't know if anybody on this list can answer this, we
> > are going to add an IIO compatible Maxim MAX1363 4 channel
> > ADC to our BBB cape and I am not sure how to specify in the
> > dts file that it is connected to the I2C channel.
> > > If anyone can give me suggestions, it would be greatly appreciated.
> > >
> >
> > Give this a try:
> >
> > &i2c1 {
> > status = "okay";
> >
> > adc@34 {
> > compatible = "maxim,max1363";
> > vcc-supply = <®_3v3>;
> > reg = <0x34>;
> > };
> > };
> >
> > This assume you have an i2c1 and reg_3v3 defined.
> >
> > Here is a real example that looks like it uses the same driver:
> > http://lxr.free-electrons.com/source/arch/arm/boot/dts/imx27-p
> > hytec-phycard-s-rdk.dts?v=3.14#L56
> >
>
> I've got the max1363 installed on a board and it is showing up as an I2C device, but not as an IIO device. I used your example above for the dts file.
>
> Any thoughts?
Try using the following instead:
&i2c1 {
status = "okay";
adc@34 {
compatible = "max1363";
vcc-supply = <®_3v3>;
reg = <0x34>;
};
};
>
> >
> > > Greg Wilson-Lindberg
> > > Sakura Finetek
> > > 310-783-5075
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe
> > linux-iio"
> > > in the body of a message to majordomo@vger.kernel.org More
> > majordomo
> > > info at http://vger.kernel.org/majordomo-info.html
> >
next prev parent reply other threads:[~2015-08-27 19:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 16:26 Adding MAX1363 to BBB Greg Wilson-Lindberg
2015-08-24 16:54 ` Michael Welling
2015-08-24 17:09 ` Greg Wilson-Lindberg
2015-08-27 19:10 ` Greg Wilson-Lindberg
2015-08-27 19:16 ` Michael Welling [this message]
2015-08-27 20:40 ` Greg Wilson-Lindberg
2015-08-27 20:42 ` Michael Welling
2015-08-27 21:06 ` Greg Wilson-Lindberg
2015-08-27 21:44 ` Greg Wilson-Lindberg
2015-08-28 23:56 ` Greg Wilson-Lindberg
2015-08-29 0:32 ` Michael Welling
2015-08-31 16:01 ` Greg Wilson-Lindberg
2015-08-31 16:24 ` Jonathan Cameron
2015-08-31 16:52 ` Michael Welling
2015-08-31 16:56 ` Jonathan Cameron
2015-08-31 16:59 ` Greg Wilson-Lindberg
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=20150827191616.GA8285@deathstar \
--to=mwelling@ieee.org \
--cc=GWilson@sakuraus.com \
--cc=linux-iio@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