From: Qii Wang <qii.wang@mediatek.com>
To: <wsa@the-dreams.de>
Cc: <matthias.bgg@gmail.com>, <linux-i2c@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>, <leilk.liu@mediatek.com>
Subject: Re: [PATCH] i2c: mediatek: Get device clock-stretch time via dts
Date: Mon, 1 Mar 2021 20:22:01 +0800 [thread overview]
Message-ID: <1614601321.16737.5.camel@mhfsdcap03> (raw)
In-Reply-To: <1612348525-13364-1-git-send-email-qii.wang@mediatek.com>
Hi,
On Wed, 2021-02-03 at 18:35 +0800, qii.wang@mediatek.com wrote:
> From: Qii Wang <qii.wang@mediatek.com>
>
> tSU,STA/tHD,STA/tSU,STOP maybe out of spec due to device
> clock-stretching or circuit loss, we could get device
> clock-stretch time from dts to adjust these parameters
> to meet the spec via EXT_CONF register.
>
> Signed-off-by: Qii Wang <qii.wang@mediatek.com>
> ---
Can it merge into 5.12? or do I need to resend the patch?
Thanks,
Qii
WARNING: multiple messages have this Message-ID (diff)
From: Qii Wang <qii.wang@mediatek.com>
To: <wsa@the-dreams.de>
Cc: srv_heupstream@mediatek.com, leilk.liu@mediatek.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-i2c@vger.kernel.org, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: mediatek: Get device clock-stretch time via dts
Date: Mon, 1 Mar 2021 20:22:01 +0800 [thread overview]
Message-ID: <1614601321.16737.5.camel@mhfsdcap03> (raw)
In-Reply-To: <1612348525-13364-1-git-send-email-qii.wang@mediatek.com>
Hi,
On Wed, 2021-02-03 at 18:35 +0800, qii.wang@mediatek.com wrote:
> From: Qii Wang <qii.wang@mediatek.com>
>
> tSU,STA/tHD,STA/tSU,STOP maybe out of spec due to device
> clock-stretching or circuit loss, we could get device
> clock-stretch time from dts to adjust these parameters
> to meet the spec via EXT_CONF register.
>
> Signed-off-by: Qii Wang <qii.wang@mediatek.com>
> ---
Can it merge into 5.12? or do I need to resend the patch?
Thanks,
Qii
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Qii Wang <qii.wang@mediatek.com>
To: <wsa@the-dreams.de>
Cc: srv_heupstream@mediatek.com, leilk.liu@mediatek.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-i2c@vger.kernel.org, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c: mediatek: Get device clock-stretch time via dts
Date: Mon, 1 Mar 2021 20:22:01 +0800 [thread overview]
Message-ID: <1614601321.16737.5.camel@mhfsdcap03> (raw)
In-Reply-To: <1612348525-13364-1-git-send-email-qii.wang@mediatek.com>
Hi,
On Wed, 2021-02-03 at 18:35 +0800, qii.wang@mediatek.com wrote:
> From: Qii Wang <qii.wang@mediatek.com>
>
> tSU,STA/tHD,STA/tSU,STOP maybe out of spec due to device
> clock-stretching or circuit loss, we could get device
> clock-stretch time from dts to adjust these parameters
> to meet the spec via EXT_CONF register.
>
> Signed-off-by: Qii Wang <qii.wang@mediatek.com>
> ---
Can it merge into 5.12? or do I need to resend the patch?
Thanks,
Qii
_______________________________________________
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:[~2021-03-01 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 10:35 [PATCH] i2c: mediatek: Get device clock-stretch time via dts qii.wang
2021-02-03 10:35 ` qii.wang
2021-02-03 10:35 ` qii.wang
2021-03-01 12:22 ` Qii Wang [this message]
2021-03-01 12:22 ` Qii Wang
2021-03-01 12:22 ` Qii Wang
2021-03-02 11:30 ` Ikjoon Jang
2021-03-02 11:30 ` Ikjoon Jang
2021-03-02 11:30 ` Ikjoon Jang
2021-03-02 12:32 ` Qii Wang
2021-03-02 12:32 ` Qii Wang
2021-03-02 12:32 ` Qii Wang
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=1614601321.16737.5.camel@mhfsdcap03 \
--to=qii.wang@mediatek.com \
--cc=leilk.liu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=srv_heupstream@mediatek.com \
--cc=wsa@the-dreams.de \
/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.