From: Wolfram Sang <wsa@kernel.org>
To: "Ivan T. Ivanov" <iivanov@suse.de>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: [PATCH] i2c: bcm2835: Set clock-stretch timeout to 35ms
Date: Mon, 7 Feb 2022 16:15:24 +0100 [thread overview]
Message-ID: <YgE3jMkzisFZFHb5@shikoro> (raw)
In-Reply-To: <YfPHawUXJRPDHPmM@shikoro>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
> By default, busses are I2C and not SMBus, so it looks like we should
> finally apply this patch which disables CLKT:
>
> http://patchwork.ozlabs.org/project/linux-i2c/patch/1519422151-6218-1-git-send-email-stefan.wahren@i2se.com/
I applied this now to for-current and added stable. That should avoid
unwanted timeouts.
> If you really want the SMBus timeout applied, you can check for a
> "smbus" property in DT and then set CLKT accordingly in a seperate
> patch.
This still holds.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: "Ivan T. Ivanov" <iivanov@suse.de>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: [PATCH] i2c: bcm2835: Set clock-stretch timeout to 35ms
Date: Mon, 7 Feb 2022 16:15:24 +0100 [thread overview]
Message-ID: <YgE3jMkzisFZFHb5@shikoro> (raw)
In-Reply-To: <YfPHawUXJRPDHPmM@shikoro>
[-- Attachment #1.1: Type: text/plain, Size: 506 bytes --]
> By default, busses are I2C and not SMBus, so it looks like we should
> finally apply this patch which disables CLKT:
>
> http://patchwork.ozlabs.org/project/linux-i2c/patch/1519422151-6218-1-git-send-email-stefan.wahren@i2se.com/
I applied this now to for-current and added stable. That should avoid
unwanted timeouts.
> If you really want the SMBus timeout applied, you can check for a
> "smbus" property in DT and then set CLKT accordingly in a seperate
> patch.
This still holds.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-07 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 10:25 [PATCH] i2c: bcm2835: Set clock-stretch timeout to 35ms Ivan T. Ivanov
2022-01-17 10:25 ` Ivan T. Ivanov
2022-01-28 8:47 ` Ivan T . Ivanov
2022-01-28 8:47 ` Ivan T . Ivanov
2022-01-28 10:37 ` Wolfram Sang
2022-01-28 10:37 ` Wolfram Sang
2022-02-07 15:15 ` Wolfram Sang [this message]
2022-02-07 15:15 ` Wolfram Sang
2022-02-07 15:41 ` Ivan T. Ivanov
2022-02-07 15:41 ` Ivan T. Ivanov
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=YgE3jMkzisFZFHb5@shikoro \
--to=wsa@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=iivanov@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.