From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1E060CD37B0 for ; Sat, 16 Sep 2023 02:30:47 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96) (envelope-from ) id 1qhL54-00043o-0W for kernelnewbies@archiver.kernel.org; Fri, 15 Sep 2023 22:30:46 -0400 Received: from mail-pl1-x629.google.com ([2607:f8b0:4864:20::629]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qeFBj-00048U-02 for kernelnewbies@kernelnewbies.org; Thu, 07 Sep 2023 09:36:56 -0400 Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1bee82fad0fso7976045ad.2 for ; Thu, 07 Sep 2023 06:36:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694093797; x=1694698597; darn=kernelnewbies.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=T2TY1zNPUiYdqBQO99FsEA07lmhG2zgPAGOBpSVqD2wSPwkb/2PWw8KbTgEFBTqbhj ZPLSlLEGrhUo+TU64C6R49+SWwfTNhh/sec3yaj/mPrmYzQIljWkjMU4tPLnijJ7T/wS 3A+nauh6B6C/wVbu1ND2mmXfa3T/LBO3h8oIU0KxiAJymkEwJg5GJ5KaEe5VS0UrcUPI ZgUvtPa6MIooTYUm3IiKbr5pTRgYYhv2FO++06Vf1scDkLYPuKqDd4huLXMynuSNgJC6 inNIVvXsiNm4b96pP4PJ7j+E74ClbCIy0J45EDSAQyuh9rhvSc2Qf99tUyAwLbyvy7R7 y9QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694093797; x=1694698597; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=aSpNvsL9Ja6OUkTSr+olZGhILhlnwxwCUSCvIjONFpawQZUwT3tic1GqNUMe05SSp5 WsDh6BYHO5Bo6mmILIJOMv3CR89yx0Y59xqI6PJ4oIYexsgdzGpfZc2weAw+OSXEszoc 2W4rpXEMfxDQVN7LcsLnxhcnptYYWAo1jxOYdYVdKezJILmQ3RG+glwFnJtVNbFMon7b UZ6gViJYzYILXpdE3F+bMMhj5xpDZGfwNWtfPy1HIIKKaL+W7ywW1hFNlQPd6j2SVZOx KwzvhQ1qKhEeBp31gZxkkPlkJJ8h8k4bRE6NpteIYdI8Mp80Wad5Pin5UC1DDEgBbZEB gGpg== X-Gm-Message-State: AOJu0Yx/DhJ/ixtabpDJ3bngbXLYkHA89w+gZAfG+iSzRg4MyZ44BuQd IisKrh44JGTV2g+89jih+eg= X-Google-Smtp-Source: AGHT+IEsTDjlEJFvmqN1jWfGRQV26ABBTlqdZtz+qVwfZnqDHmSJNz8WWRbKq21PTU6/3PBfwQkKYQ== X-Received: by 2002:a17:90a:49cd:b0:268:5431:f2a7 with SMTP id l13-20020a17090a49cd00b002685431f2a7mr16515868pjm.28.1694093797142; Thu, 07 Sep 2023 06:36:37 -0700 (PDT) Received: from debian.me ([103.124.138.83]) by smtp.gmail.com with ESMTPSA id 10-20020a17090a01ca00b00263dfe9b972sm1623144pjd.0.2023.09.07.06.36.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Sep 2023 06:36:36 -0700 (PDT) Received: by debian.me (Postfix, from userid 1000) id C775B8F4C13A; Thu, 7 Sep 2023 20:36:32 +0700 (WIB) Date: Thu, 7 Sep 2023 20:36:32 +0700 From: Bagas Sanjaya To: Raul Piper , , LKML , Linux ARM , Linux I2C , Linux Devicetree Subject: Re: Debugging i2c : i2cdetect cant detect a device on i2c line Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-Mailman-Approved-At: Fri, 15 Sep 2023 22:28:37 -0400 Cc: Conor Dooley , Linus Walleij , Rob Herring , Andi Shyti , Krzysztof Kozlowski X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5164106604416328798==" Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org --===============5164106604416328798== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="H1/cJnQLbHBLXKRp" Content-Disposition: inline --H1/cJnQLbHBLXKRp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [also Cc: devicetree and ARM folks] On Thu, Sep 07, 2023 at 08:21:44AM +0530, Raul Piper wrote: > Hello , > I am trying to detect an i2c device A on i2c1 line on one of the Arm > Cortex A7 platform but not able to see any device on a given address ( > 0x3d) . >=20 > Is there any parameters of i2c which i can change like rise/fall time > , timeout etc in a device tree or kernel source and re test it? > I have tried changing the i2c speed from 100KHz to 400 KHz but no succes= s. > I have even tried removing the 1.5K pull ups on the i2c lines but no resu= lt. >=20 > So I wanted to know on what factors i2cdetect may not probe the device > or show it on the hex dump. > What parameters of i2c driver i can tinker and where? Is Platform dts > is the only file i can modify and test with? > Kernel is 5.51 . Do you mean v5.15.y stable series? > There are other 2-3 devices on the same lines which responds to > i2cdetect with correct address but not this device (0x3D) . > Its i2c address is also different from the current devices. >=20 Specifically, what device do you have this issue with? Confused... --=20 An old man doll... just what I always wanted! - Clara --H1/cJnQLbHBLXKRp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZPnR3AAKCRD2uYlJVVFO oyWCAP9+/SOZwrNMjfRhCDMh3l0obDG00/bTTq/q77PhjjA7rgD+NsH4fEEZCONi 2HKCHPJtDXAGeViGmvQbTqhp/EFcsAw= =irVf -----END PGP SIGNATURE----- --H1/cJnQLbHBLXKRp-- --===============5164106604416328798== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies --===============5164106604416328798==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8D388EC873E for ; Thu, 7 Sep 2023 16:24:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241338AbjIGQYK (ORCPT ); Thu, 7 Sep 2023 12:24:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57276 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244055AbjIGQXW (ORCPT ); Thu, 7 Sep 2023 12:23:22 -0400 Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8ECEB1FCA; Thu, 7 Sep 2023 09:13:01 -0700 (PDT) Received: by mail-ua1-x92b.google.com with SMTP id a1e0cc1a2514c-791b8525b59so455780241.1; Thu, 07 Sep 2023 09:13:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694103096; x=1694707896; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=b0vQ4D1mQ3kgqLuEJrXWtcFCHI5Fab6K8w6MX+iTwP4/6dpOYnIbghxpErxgGXmfdm xdMABYv6ezxLVSLwGR1+/5cipYCr1fYqGF0zmM5OjfdVHFC9Q//fb+01Pw2gcN6ocuS3 EzgkLCBjWluobmjdFWYxy4slQYM7FmACRBhETD1QCEvW/wq4sn04c/lDOIYvkLvmKjlT u4iv2it/HImD+miwGl9oaRpUUv9SH7ZKJ5lU+lMk5ouu5B3Xm+uMV0NQeJ+kHZUQkK6f tyWIFzBqDcrJpZyBeRohhnIvPTSIeQeQoIuMkfrDfn9wqpiiGixCIel74rXxbX+QAEBG gDOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694103096; x=1694707896; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=OeGUGyat+QwIj46Hul/zlsY02WX3jUfBUyFhphz3EOY2w6gSKeoMCcb4ApzDJkUIZT Ew1lXhzdJJXXIk/I0bujhluRnM3vwxot0ur7f1HNDOl3WMhMTJUIA4fgTlcaKok+wqs6 sW6E+tM2G+Gcj36CaZN3chWTLhKbYs4f0RZXf7bxal41FNSdfqYuQpFw8vwkTqkuRRbi +NLkp8DfWZhq3Q5fgvMO9DxbBCbMW1WYvxtmAyvi/pXieiYLqLiATfAMjVqkLqCmAh14 yQzJhqq7YAxjZZfTznJpXGhGTIAZIZCJ0J1WX0vm2ivB1xShw8VNYo2n82RGgfiRUy2l YZAA== X-Gm-Message-State: AOJu0Yw7KDHEENFthOi39/fz4YBzaYfQxYbYghhjUK355onyA06cacvk YSqc9+LDOkDUqmc4lesX4joYnh0i8QM= X-Google-Smtp-Source: AGHT+IEsTDjlEJFvmqN1jWfGRQV26ABBTlqdZtz+qVwfZnqDHmSJNz8WWRbKq21PTU6/3PBfwQkKYQ== X-Received: by 2002:a17:90a:49cd:b0:268:5431:f2a7 with SMTP id l13-20020a17090a49cd00b002685431f2a7mr16515868pjm.28.1694093797142; Thu, 07 Sep 2023 06:36:37 -0700 (PDT) Received: from debian.me ([103.124.138.83]) by smtp.gmail.com with ESMTPSA id 10-20020a17090a01ca00b00263dfe9b972sm1623144pjd.0.2023.09.07.06.36.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Sep 2023 06:36:36 -0700 (PDT) Received: by debian.me (Postfix, from userid 1000) id C775B8F4C13A; Thu, 7 Sep 2023 20:36:32 +0700 (WIB) Date: Thu, 7 Sep 2023 20:36:32 +0700 From: Bagas Sanjaya To: Raul Piper , , LKML , Linux ARM , Linux I2C , Linux Devicetree Cc: Linus Walleij , Andi Shyti , Rob Herring , Krzysztof Kozlowski , Conor Dooley Subject: Re: Debugging i2c : i2cdetect cant detect a device on i2c line Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="H1/cJnQLbHBLXKRp" Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org --H1/cJnQLbHBLXKRp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [also Cc: devicetree and ARM folks] On Thu, Sep 07, 2023 at 08:21:44AM +0530, Raul Piper wrote: > Hello , > I am trying to detect an i2c device A on i2c1 line on one of the Arm > Cortex A7 platform but not able to see any device on a given address ( > 0x3d) . >=20 > Is there any parameters of i2c which i can change like rise/fall time > , timeout etc in a device tree or kernel source and re test it? > I have tried changing the i2c speed from 100KHz to 400 KHz but no succes= s. > I have even tried removing the 1.5K pull ups on the i2c lines but no resu= lt. >=20 > So I wanted to know on what factors i2cdetect may not probe the device > or show it on the hex dump. > What parameters of i2c driver i can tinker and where? Is Platform dts > is the only file i can modify and test with? > Kernel is 5.51 . Do you mean v5.15.y stable series? > There are other 2-3 devices on the same lines which responds to > i2cdetect with correct address but not this device (0x3D) . > Its i2c address is also different from the current devices. >=20 Specifically, what device do you have this issue with? Confused... --=20 An old man doll... just what I always wanted! - Clara --H1/cJnQLbHBLXKRp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZPnR3AAKCRD2uYlJVVFO oyWCAP9+/SOZwrNMjfRhCDMh3l0obDG00/bTTq/q77PhjjA7rgD+NsH4fEEZCONi 2HKCHPJtDXAGeViGmvQbTqhp/EFcsAw= =irVf -----END PGP SIGNATURE----- --H1/cJnQLbHBLXKRp-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 33B09EC8724 for ; Thu, 7 Sep 2023 13:37:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=7Ty5JDjidsQZ/RmN5XPwjM7Qpo7Hv7E4USuWwggdVHQ=; b=LNUxCE0ngGJrqvKnQxUMOtOF87 QnH3HYJNvI6YzSy/ZSYoADCsGdqA/vbeZbE9QjXkKcR7VhFjin35kz/RdXqJMyUJCs90Y83h2Z9w+ 4gas8U7/GTInAzMCC6AmpRC4bCW6Cu11tZD1Co13E0IgLM+45nExjYtg8LrEiY9GyBIQLzj9YLx1d 2iJufm/11gb6W2WAKfM+K5SX+NGB1KJAMy2YR4dYNeQHucK2BVmgHitTiWe+fGs8zY7ZdvALGVlIo qr/uKZVdY76X8oXa6j/DoNOPTZPYFvAupTsmJWU+C2J19N00QBbXrTFrkKFwNObQHRAYQzov+cm72 kD/k3mvQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qeFBZ-00C90I-2x; Thu, 07 Sep 2023 13:36:41 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qeFBX-00C8zt-0d for linux-arm-kernel@lists.infradead.org; Thu, 07 Sep 2023 13:36:40 +0000 Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-271c700efb2so682807a91.0 for ; Thu, 07 Sep 2023 06:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694093797; x=1694698597; darn=lists.infradead.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=alHJxJW2lZSaDAN8pltdYI2R3taDFXmG2mziM6+qTSqgq4pJiKquaGdnQ5B0PIBFr6 +GhF36UxFKKl1BeJ+dVtndeGh7zUphqY65HO9nkOkjHjFzFgFaJiBYDgeuFyQ6u2/QXh 3u/rFFlz63mo9FLXpKSnyHfx+4g/iQztUhwHIHS+NyFD6r/KTb1juIPvP/w6FIKQYE7N e8rQna1K38yVnM401qoYx9RJBQ/2y2FhWxVGkpYo8Ph4Ka+tByLG1vvqiMw1WuERtfy0 wfDcNHxyBrl4pk5TwwwKETNmk8i0MigalWMmzhcte7cOQ451Mka+NycETR7iKRxIikPU mr6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694093797; x=1694698597; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yBbG/89WwsARwO9cDG6ZrnKutfGNLaFwpYJJxWQTWZs=; b=OUmY3kbcil+loz4kwrLB6bNT0wYGuMfONkFas5V3L0WEXD+ea0AQP1ktZAeNfP1XlK v/0ZW4xaGg/E2m0BW5FApsXCefpP1XQMhPm5IMx7AI8kofcA7mPAk77JZi3y0wul3LeO DxHZQk/X/wJ9VMJyoBe4jvk0AZwbOt/p2wkOXmY2+oryOZrQXksAhFcAZ7TWQXoiuTPz 5++QO1rpURUbEv2mNRj98EUv242ZbCpiZS5aUNTH5/RYgj3UXpiQnVV4bmy7LbHF13wp Mfc1YjmLiTn7p3f+PmiurF1OWYYOkwcxhV68qeRABYs3BJnL8l37gbHDus2w0etnlPEw qkGQ== X-Gm-Message-State: AOJu0YwWDIL46kDI6H7BG6/X0bscvF8PZFT9pfSxlh81tfTGEq5JpOAt TfWLv6BatWxgns8pl+EHwfE= X-Google-Smtp-Source: AGHT+IEsTDjlEJFvmqN1jWfGRQV26ABBTlqdZtz+qVwfZnqDHmSJNz8WWRbKq21PTU6/3PBfwQkKYQ== X-Received: by 2002:a17:90a:49cd:b0:268:5431:f2a7 with SMTP id l13-20020a17090a49cd00b002685431f2a7mr16515868pjm.28.1694093797142; Thu, 07 Sep 2023 06:36:37 -0700 (PDT) Received: from debian.me ([103.124.138.83]) by smtp.gmail.com with ESMTPSA id 10-20020a17090a01ca00b00263dfe9b972sm1623144pjd.0.2023.09.07.06.36.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Sep 2023 06:36:36 -0700 (PDT) Received: by debian.me (Postfix, from userid 1000) id C775B8F4C13A; Thu, 7 Sep 2023 20:36:32 +0700 (WIB) Date: Thu, 7 Sep 2023 20:36:32 +0700 From: Bagas Sanjaya To: Raul Piper , , LKML , Linux ARM , Linux I2C , Linux Devicetree Cc: Linus Walleij , Andi Shyti , Rob Herring , Krzysztof Kozlowski , Conor Dooley Subject: Re: Debugging i2c : i2cdetect cant detect a device on i2c line Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230907_063639_241642_969FB9EE X-CRM114-Status: GOOD ( 23.43 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6242178395757042873==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============6242178395757042873== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="H1/cJnQLbHBLXKRp" Content-Disposition: inline --H1/cJnQLbHBLXKRp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [also Cc: devicetree and ARM folks] On Thu, Sep 07, 2023 at 08:21:44AM +0530, Raul Piper wrote: > Hello , > I am trying to detect an i2c device A on i2c1 line on one of the Arm > Cortex A7 platform but not able to see any device on a given address ( > 0x3d) . >=20 > Is there any parameters of i2c which i can change like rise/fall time > , timeout etc in a device tree or kernel source and re test it? > I have tried changing the i2c speed from 100KHz to 400 KHz but no succes= s. > I have even tried removing the 1.5K pull ups on the i2c lines but no resu= lt. >=20 > So I wanted to know on what factors i2cdetect may not probe the device > or show it on the hex dump. > What parameters of i2c driver i can tinker and where? Is Platform dts > is the only file i can modify and test with? > Kernel is 5.51 . Do you mean v5.15.y stable series? > There are other 2-3 devices on the same lines which responds to > i2cdetect with correct address but not this device (0x3D) . > Its i2c address is also different from the current devices. >=20 Specifically, what device do you have this issue with? Confused... --=20 An old man doll... just what I always wanted! - Clara --H1/cJnQLbHBLXKRp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZPnR3AAKCRD2uYlJVVFO oyWCAP9+/SOZwrNMjfRhCDMh3l0obDG00/bTTq/q77PhjjA7rgD+NsH4fEEZCONi 2HKCHPJtDXAGeViGmvQbTqhp/EFcsAw= =irVf -----END PGP SIGNATURE----- --H1/cJnQLbHBLXKRp-- --===============6242178395757042873== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============6242178395757042873==--