From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Daniel Golle <daniel@makrotopia.org>,
linux-i2c@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Qii Wang <qii.wang@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH 1/2] i2c: mediatek: add support for MT7981 SoC
Date: Tue, 14 Mar 2023 10:26:56 +0100 [thread overview]
Message-ID: <5f219379-cccb-d8ca-ed23-4106ca3ecf3a@collabora.com> (raw)
In-Reply-To: <fdbd18ab71693b2b0dcbe1094bcfd1060bf21200.1678756608.git.daniel@makrotopia.org>
Il 14/03/23 02:18, Daniel Golle ha scritto:
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
> ---
> drivers/i2c/busses/i2c-mt65xx.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drivers/i2c/busses/i2c-mt65xx.c
> index 43dd966d5ef5..54cabd366403 100644
> --- a/drivers/i2c/busses/i2c-mt65xx.c
> +++ b/drivers/i2c/busses/i2c-mt65xx.c
> @@ -431,6 +431,18 @@ static const struct mtk_i2c_compatible mt8168_compat = {
> .max_dma_support = 33,
> };
>
> +static const struct mtk_i2c_compatible mt7981_compat = {
> + .regs = mt_i2c_regs_v3,
I've found a downstream kernel saying that MT7981 uses `mt_i2c_regs_v2`,
hence the question:
Are you sure that this is supposed to be v3?
Regards,
Angelo
> + .pmic_i2c = 0,
> + .dcm = 0,
> + .auto_restart = 1,
> + .aux_len_reg = 1,
> + .timing_adjust = 1,
> + .dma_sync = 1,
> + .ltiming_adjust = 1,
> + .max_dma_support = 33
> +};
> +
> static const struct mtk_i2c_compatible mt7986_compat = {
> .quirks = &mt7622_i2c_quirks,
> .regs = mt_i2c_regs_v1,
> @@ -516,6 +528,7 @@ static const struct of_device_id mtk_i2c_of_match[] = {
> { .compatible = "mediatek,mt6577-i2c", .data = &mt6577_compat },
> { .compatible = "mediatek,mt6589-i2c", .data = &mt6589_compat },
> { .compatible = "mediatek,mt7622-i2c", .data = &mt7622_compat },
> + { .compatible = "mediatek,mt7981-i2c", .data = &mt7981_compat },
> { .compatible = "mediatek,mt7986-i2c", .data = &mt7986_compat },
> { .compatible = "mediatek,mt8168-i2c", .data = &mt8168_compat },
> { .compatible = "mediatek,mt8173-i2c", .data = &mt8173_compat },
next prev parent reply other threads:[~2023-03-14 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 1:18 [PATCH 0/2] i2c: i2c-mt65xx: add support for MT7981 Daniel Golle
2023-03-14 1:18 ` [PATCH 1/2] i2c: mediatek: add support for MT7981 SoC Daniel Golle
2023-03-14 9:26 ` AngeloGioacchino Del Regno [this message]
2023-03-14 12:32 ` Daniel Golle
2023-03-14 1:18 ` [PATCH 2/2] dt-bindings: i2c: i2c-mt65xx: add binding " Daniel Golle
2023-03-14 9:28 ` AngeloGioacchino Del Regno
2023-04-06 21:41 [PATCH 0/2] i2c: i2c-mt65xx: add support for MT7981 Daniel Golle
2023-04-06 21:41 ` [PATCH 1/2] i2c: mediatek: add support for MT7981 SoC Daniel Golle
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=5f219379-cccb-d8ca-ed23-4106ca3ecf3a@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=qii.wang@mediatek.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
all inboxes | Powered by JetHome®