# Extra i2c-2 devices on humming-board pulse apart from dts mentioned **URL:** \ **Category:** NXP i.MX8M Plus\ **Created:** [October 3, 2023, 9:21am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734 "2023-10-03T09:21:21Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Kartheek](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kartheek](https://community.solid-run.com/u/Kartheek)\ **Post date:** [October 3, 2023, 9:21am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/1 "2023-10-03T09:21:21Z")
Hi Team, When i use i2cdetect command for bus 2. I see the devices attached in the below screenshot. But when i see the imx8mp-hummingboard-pulse.dts file in kernel-source folder there are some different devices. Can you please make me sure how i2cdetect is showing extra devices on board apart from dts file devices ![Screenshot from 2023-10-03 14-46-21](https://europe1.discourse-cdn.com/flex005/uploads/solid_run/original/1X/bbb93e33951a8161bcdc931e009857ed1878fc7f.png) . Thanks, Kartheek ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [October 3, 2023, 11:57am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/2 "2023-10-03T11:57:36Z")
Because of the way that I2C addressing works sometimes i2c-detect will detect “false” devices when a device has multiple interfaces it exposes on the i2c bus. This is the case with the adv7535 dsi to hdmi bridge. ---
**Author:** ![Kartheek](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kartheek](https://community.solid-run.com/u/Kartheek)\ **Post date:** [October 3, 2023, 12:57pm UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/3 "2023-10-03T12:57:53Z")
I need to communicate with my 0x38 slave address. But its already present on the board. May i know what is the slave device present on that already. If 0x38 is present on the board how to deactivate it. ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [October 3, 2023, 1:10pm UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/4 "2023-10-03T13:10:29Z")
If you do not need to use the micro-hdmi interface you can just disable the node in the device-tree. It is powered by the dsi\_en pin and that should default to off if the node does not enable it. If you run into any issues let me know. ---
**Author:** ![Kartheek](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kartheek](https://community.solid-run.com/u/Kartheek)\ **Post date:** [October 4, 2023, 5:36am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/5 "2023-10-04T05:36:02Z")
I tried to disabled the adv\_brige by making status= “disabled” in device-tree. But still i2cdetect on bus 2 showing 0x38. Is this that correct way of disabling device. May i know what to do next. Thanks in advance. ![Screenshot from 2023-10-04 12-28-33](https://europe1.discourse-cdn.com/flex005/uploads/solid_run/original/1X/86acb1363d51b96e517e1229acac5a9e3ef8d356.png) ---
**Author:** ![Kartheek](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kartheek](https://community.solid-run.com/u/Kartheek)\ **Post date:** [October 5, 2023, 5:49am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/6 "2023-10-05T05:49:43Z")
Hi jnettlet, I have commented the pinctrl-0 which has dsi\_en in device tree. But still showing the 0x38. Can you please tell how to solve the problem. Thanks in advance. ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [October 5, 2023, 8:04am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/7 "2023-10-05T08:04:30Z")
Is that device still bound to a driver? Does it show up as UU still? ---
**Author:** ![Kartheek](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kartheek](https://community.solid-run.com/u/Kartheek)\ **Post date:** [October 5, 2023, 9:10am UTC](https://community.solid-run.com/t/extra-i2c-2-devices-on-humming-board-pulse-apart-from-dts-mentioned/734/8 "2023-10-05T09:10:00Z")
No it doesn’t show UU now. But still 0x38 is present how to avoid that. Below is the screen shot for your reference. ![i2cdetect](https://europe1.discourse-cdn.com/flex005/uploads/solid_run/original/1X/93e86aeca0d36751cc7a0ee823a99f7de04a16b3.jpeg)