From: Chen-Yu Tsai <wenst@chromium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Hsin-Te Yuan <yuanhsinte@chromium.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Enric Balletbo i Serra <eballetbo@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Daolong Zhu <jg_daolongzhu@mediatek.corp-partner.google.com>
Subject: Re: [PATCH 0/4] arm64: dts: mt8183: Add i2c-scl-internal-delay-ns
Date: Tue, 8 Oct 2024 16:14:45 +0800 [thread overview]
Message-ID: <20241008081445.GA3999626@google.com> (raw)
In-Reply-To: <01020191d6992288-f834e61d-ad1d-4de7-90b4-77525530532c-000000@eu-west-1.amazonses.com>
On Mon, Sep 09, 2024 at 11:44:05AM +0000, AngeloGioacchino Del Regno wrote:
> Il 09/09/24 09:29, Hsin-Te Yuan ha scritto:
> > Add i2c-scl-internal-delay-ns for each device.
> >
> > Signed-off-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
> > ---
> > Daolong Zhu (4):
> > arm64: dts: mt8183: fennel: add i2c2's i2c-scl-internal-delay-ns
> > arm64: dts: mt8183: burnet: add i2c2's i2c-scl-internal-delay-ns
> > arm64: dts: mt8183: cozmo: add i2c2's i2c-scl-internal-delay-ns
> > arm64: dts: mt8183: Damu: add i2c2's i2c-scl-internal-delay-ns
> >
> > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-burnet.dts | 3 +++
> > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-cozmo.dts | 2 ++
> > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-damu.dts | 3 +++
> > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-fennel.dtsi | 3 +++
> > 4 files changed, 11 insertions(+)
> > ---
> > base-commit: ee9a43b7cfe2d8a3520335fea7d8ce71b8cabd9d
> > change-id: 20240909-i2c-delay-6d202918ee0f
> >
> > Best regards,
>
>
> For the entire series:
>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>
I guess this can be applied now?
ChenYu
next prev parent reply other threads:[~2024-10-08 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:29 [PATCH 0/4] arm64: dts: mt8183: Add i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-09-09 7:29 ` [PATCH 1/4] arm64: dts: mt8183: fennel: add i2c2's i2c-scl-internal-delay-ns Hsin-Te Yuan
2024-09-09 11:17 ` Matthias Brugger
2024-09-09 7:29 ` [PATCH 2/4] arm64: dts: mt8183: burnet: " Hsin-Te Yuan
2024-09-09 11:18 ` Matthias Brugger
2024-09-09 7:29 ` [PATCH 3/4] arm64: dts: mt8183: cozmo: " Hsin-Te Yuan
2024-09-09 11:18 ` Matthias Brugger
2024-09-09 7:29 ` [PATCH 4/4] arm64: dts: mt8183: Damu: " Hsin-Te Yuan
2024-09-09 11:18 ` Matthias Brugger
2024-09-09 11:44 ` [PATCH 0/4] arm64: dts: mt8183: Add i2c-scl-internal-delay-ns AngeloGioacchino Del Regno
2024-10-08 8:14 ` Chen-Yu Tsai [this message]
2024-10-08 8:54 ` AngeloGioacchino Del Regno
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 12:59 Hsin-Te Yuan
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=20241008081445.GA3999626@google.com \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@kernel.org \
--cc=hsinyi@chromium.org \
--cc=jg_daolongzhu@mediatek.corp-partner.google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=yuanhsinte@chromium.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).