devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Raul Piper <raulpblooper@gmail.com>,
	<kernelnewbies@kernelnewbies.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	Linux Devicetree <devicetree@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Andi Shyti <andi.shyti@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: Debugging i2c : i2cdetect cant detect a device on i2c line
Date: Thu, 7 Sep 2023 20:36:32 +0700	[thread overview]
Message-ID: <ZPnR4Cx6_Hh3weEl@debian.me> (raw)
In-Reply-To: <CAEwN+MCorDCS7EhN40Qgja_nY+SFc3G61Zd6yntqAS+w26YO9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

[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) .
> 
> 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 success.
> I have even tried removing the 1.5K pull ups on the i2c lines but no result.
> 
> 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.
> 

Specifically, what device do you have this issue with?

Confused...

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

       reply	other threads:[~2023-09-07 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEwN+MCorDCS7EhN40Qgja_nY+SFc3G61Zd6yntqAS+w26YO9Q@mail.gmail.com>
2023-09-07 13:36 ` Bagas Sanjaya [this message]
2023-09-07 13:55   ` Debugging i2c : i2cdetect cant detect a device on i2c line Russell King (Oracle)
     [not found]     ` <CAJX_Q+0-v=oadJ697VDawyEhDSPBAS_oqakZFHWVUfsnbCanMA@mail.gmail.com>
2023-09-07 17:08       ` Raul Piper
2023-09-07 18:00         ` Russell King (Oracle)
2023-09-07 17:28       ` Russell King (Oracle)

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=ZPnR4Cx6_Hh3weEl@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raulpblooper@gmail.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).