From: Tzung-Bi Shih <tzungbi@google.com>
To: kewei.xu@mediatek.com
Cc: bbrezillon@kernel.org, matthias.bgg@gmail.com,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-i3c@lists.infradead.org, devicetree@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, qii.wang@mediatek.com,
liguo.zhang@mediatek.com, xinping.qian@mediatek.com
Subject: Re: [PATCH V2 3/3] i2c: mediatek: Isolate speed setting via dts for special devices
Date: Mon, 21 Jun 2021 17:44:38 +0800 [thread overview]
Message-ID: <CA+Px+wXx8eyh2QFRHbkf3ESdXzBw8LNqP=jMihju+jV0TpQvhw@mail.gmail.com> (raw)
In-Reply-To: <1624266114-21539-4-git-send-email-kewei.xu@mediatek.com>
On Mon, Jun 21, 2021 at 5:03 PM <kewei.xu@mediatek.com> wrote:
> @@ -1293,8 +1355,8 @@ static int mtk_i2c_parse_dt(struct device_node *np, struct mtk_i2c *i2c)
> i2c->have_pmic = of_property_read_bool(np, "mediatek,have-pmic");
> i2c->use_push_pull =
> of_property_read_bool(np, "mediatek,use-push-pull");
> -
> - i2c_parse_fw_timings(i2c->dev, &i2c->timing_info, true);
Looks like the patch removes the line accidentally.
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2021-06-22 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 9:01 [PATCH V2 0/3] Introduce an attribute to choose timing setting kewei.xu
2021-06-21 9:01 ` [PATCH V2 1/3] i2c: mediatek: Add OFFSET_EXT_CONF setting back kewei.xu
2021-06-21 9:01 ` [PATCH V2 2/3] dt-bindings: i2c: add attribute default-timing-adjust kewei.xu
2021-06-21 9:01 ` [PATCH V2 3/3] i2c: mediatek: Isolate speed setting via dts for special devices kewei.xu
2021-06-21 9:44 ` Tzung-Bi Shih [this message]
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='CA+Px+wXx8eyh2QFRHbkf3ESdXzBw8LNqP=jMihju+jV0TpQvhw@mail.gmail.com' \
--to=tzungbi@google.com \
--cc=bbrezillon@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kewei.xu@mediatek.com \
--cc=leilk.liu@mediatek.com \
--cc=liguo.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=xinping.qian@mediatek.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 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).