> -----Original Message----- > From: Michael Welling [mailto:mwelling79@xxxxxxxxx] On Behalf > Of Michael Welling > Sent: Thursday, August 27, 2015 1:42 PM > To: Greg Wilson-Lindberg > Cc: linux-iio@xxxxxxxxxxxxxxx > Subject: Re: Adding MAX1363 to BBB > > On Thu, Aug 27, 2015 at 01:40:24PM -0700, Greg Wilson-Lindberg wrote: > > > > > > > -----Original Message----- > > > From: Michael Welling [mailto:mwelling79@xxxxxxxxx] On Behalf Of > > > Michael Welling > > > Sent: Thursday, August 27, 2015 12:16 PM > > > To: Greg Wilson-Lindberg > > > Cc: linux-iio@xxxxxxxxxxxxxxx > > > Subject: Re: Adding MAX1363 to BBB > > > > > > On Thu, Aug 27, 2015 at 12:10:06PM -0700, Greg > Wilson-Lindberg wrote: > > > > > > > > > > > > > -----Original Message----- > > > > > From: Michael Welling [mailto:mwelling79@xxxxxxxxx] > On Behalf Of > > > > > Michael Welling > > > > > Sent: Monday, August 24, 2015 9:55 AM > > > > > To: Greg Wilson-Lindberg > > > > > Cc: linux-iio@xxxxxxxxxxxxxxx > > > > > 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>; > > > }; > > > }; > > > > I changed the dts to "max1363", but that didn't get it to > show up under iio devices. > > > > Is the driver compiled into the kernel or a module? Duh, surprisingly, it was not compiled in at all, that's what I get for thinking everything was enabled. I compiled it as a module and then I tested it both with the dts set to "max1363" and "maxim,max1363" and lsmod says the module isn't loaded. I think that I'll build the kernel with it compiled in. > > > > > > > > > > > > > > > > > > > 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@xxxxxxxxxxxxxxx More > > > > > majordomo > > > > > > info at http://vger.kernel.org/majordomo-info.html > > > > > > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
