Hello Graham,
Thanks for tour quick reply, I am using Debian 8 Jessie indeed.

*I have modified my dts as following and it is working fine expect the
expander at adress 0x20 I don't know why?*

&i2c2 {

    clock-frequency = <400000>;
    status = "okay";




*pca953x_0:gpio@20 {        compatible = "nxp, pca9535";        reg =
<0x20>;          }*;
    pca953x_1:gpio@21 {
        compatible = "nxp,pca9535";
        reg = <0x21>;
    };

    pca953x_2:gpio@22 {
        compatible = "nxp,pca9535";
        reg = <0x22>;
    };

    pca953x_3gpio@24 {
        compatible = "nxp,pca9535";
        reg = <0x24>;
    };
*It looks like the gpio adress from 1024 to gpio1040 are forbidden? see my
log below:*

GPIOs 976-991, i2c/1-0024, pca9535, can sleep:
 gpio-976 (sysfs               ) in  lo
 gpio-977 (sysfs               ) in  lo
 gpio-978 (sysfs               ) in  lo
 gpio-979 (sysfs               ) in  lo
 gpio-980 (sysfs               ) in  lo
 gpio-981 (sysfs               ) in  lo
 gpio-982 (sysfs               ) in  lo
 gpio-983 (sysfs               ) in  lo
 gpio-984 (sysfs               ) in  lo
 gpio-985 (sysfs               ) in  lo
 gpio-986 (sysfs               ) in  lo
 gpio-987 (sysfs               ) in  lo
 gpio-989 (sysfs               ) in  lo
 gpio-990 (sysfs               ) in  hi
 gpio-991 (sysfs               ) in  lo

GPIOs 992-1007, i2c/1-0022, pca9535, can sleep:
 gpio-992 (sysfs               ) in  lo
 gpio-993 (sysfs               ) in  lo
 gpio-994 (sysfs               ) in  lo
 gpio-995 (sysfs               ) in  lo
 gpio-996 (sysfs               ) in  lo
 gpio-997 (sysfs               ) in  lo
 gpio-998 (sysfs               ) in  lo
 gpio-999 (sysfs               ) in  lo
 gpio-1000 (sysfs               ) in  lo
 gpio-1001 (sysfs               ) in  lo
 gpio-1002 (sysfs               ) in  lo
 gpio-1003 (sysfs               ) in  lo
 gpio-1004 (sysfs               ) in  lo
 gpio-1005 (sysfs               ) in  lo
 gpio-1006 (sysfs               ) in  lo
 gpio-1007 (sysfs               ) in  lo

GPIOs 1008-1023, i2c/1-0021, pca9535, can sleep:
 gpio-1008 (sysfs               ) in  lo
 gpio-1009 (sysfs               ) in  lo
 gpio-1010 (sysfs               ) in  lo
 gpio-1011 (sysfs               ) in  lo
 gpio-1012 (sysfs               ) in  lo
 gpio-1013 (sysfs               ) in  lo
 gpio-1014 (sysfs               ) in  lo
 gpio-1015 (sysfs               ) in  lo
 gpio-1016 (sysfs               ) in  lo
 gpio-1017 (sysfs               ) in  lo
 gpio-1018 (sysfs               ) in  lo
 gpio-1019 (sysfs               ) in  lo
 gpio-1020 (sysfs               ) in  lo
 gpio-1021 (sysfs               ) in  lo
 gpio-1022 (sysfs               ) in  lo
 gpio-1023 (sysfs               ) out hi


2016-02-02 22:32 GMT+01:00 Graham <[email protected]>:

> You didn't say which version of OS you were running.
> The I2C busses were renumbered in later OS.
> Since you mentioned kernel 4.1.15, I will assume that you are running
> Debian 8
>
> In Debian 8, I2C2 is pinned out to P9-19 and P9-20 by default. (No device
> tree changes necessary.)
> Hook your expander there and see if you can see it with i2cdetect.
>
> --- Graham
>
> ==
>
>
> On Tuesday, February 2, 2016 at 4:54:55 AM UTC-6, malkowki_belgium wrote:
>>
>> Hello all,
>>
>> I am trying to add the PCA 9535 expander on the i2c2 bus on P9. 23 and
>> P9.24 using the device tree but I cannot detect it when booting the board
>> with the kernel 4.1.15.
>> below the way I declare the device on the DTS.
>>
>> Do you know what I am doing wrong?
>>
>> &omap3_pmx_core {
>>     pinctrl-names = "default";
>>     pinctrl-0 = <
>>             &hsusb2_pins
>>     >;
>>              i2c2_pins: pinmux_i2c_pins {
>>                 pinctrl-single,pins = <
>>                         0x18E (PIN_INPUT_PULLUP | MUX_MODE0) /*
>> i2c2_scl.gpio_168 */
>>                         0x190 (PIN_INPUT_PULLUP | MUX_MODE0) /*
>> i2c2_sda.gpio_136 */
>>
>>        >;
>> };
>>
>> &i2c2 {
>>
>>     clock-frequency = <400000>;
>>
>>     pca9535: gpio@20 {
>>         compatible = "nxp, pca9535";
>>         gpio-controller;
>>         #gpio-cell = <2>;
>>         reg = <0x20>;
>>         status = "okay";
>>
>>             };
>>
>>                    gpio@21 {
>>                         compatible = "nxp, pca9535";
>>                         gpio-controller;
>>                         #gpio-cell = <2>;
>>                         reg = <0x21>;
>>                         status = "okay";
>>
>>                  };
>>                              gpio@22 {
>>                             compatible = "nxp, pca9535";
>>                             gpio-controller;
>>                             status = "okay";
>>                             #gpio-cell = <2>;
>>                             reg = <0x22>;
>>
>>                                      };
>>                                  gpio@24 {
>>                             compatible = "nxp, pca9535";
>>                             gpio-controller;
>>                             status = "okay";
>>                             #gpio-cell = <2>;
>>                             reg = <0x24>;
>>
>>                                      };
>> };
>>
>> &gpio5 {
>>     pinctrl-names = "defaults";
>>     pinctrl-0 = <
>>                 &gpio_pins
>>                 &i2c2_pins
>>
>>         >;
>> };
>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/QsC0kgXXYw4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Beninio Mbila

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to