From: Matthias Brugger <matthias.bgg@gmail.com>
To: kewei.xu@mediatek.com, wsa@the-dreams.de
Cc: robh+dt@kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
leilk.liu@mediatek.com, qii.wang@mediatek.com,
liguo.zhang@mediatek.com, caiyu.chen@mediatek.com,
housong.zhang@mediatek.com, yuhan.wei@mediatek.com,
david-yh.chiu@mediatek.com, liju-clr.chen@mediatek.com
Subject: Re: [RESEND v4 2/2] i2c: mediatek: Add i2c compatible for Mediatek MT8188
Date: Fri, 8 Jul 2022 10:08:41 +0200 [thread overview]
Message-ID: <81af48c4-757c-384d-9a96-9cf16acb317c@gmail.com> (raw)
In-Reply-To: <20220708034758.22747-2-kewei.xu@mediatek.com>
On 08/07/2022 05:47, kewei.xu@mediatek.com wrote:
> From: Kewei Xu <kewei.xu@mediatek.com>
>
> Add i2c compatible for MT8188. Compare to MT8192 i2c controller,
> The MT8188 i2c OFFSET_SLAVE_ADDR register changed from 0x04 to 0x94.
>
Having a look at mt8192_compat there seem to be more changes. I suppose you
wanted to say, that in the register mapping the only difference is the
OFFSET_SLAVE_ADDR address, that changes.
Regards,
Matthias
> Signed-off-by: Kewei Xu <kewei.xu@mediatek.com>
> ---
> v4: no changes
> V3: no changes
> V2: added mt_i2c_regs_v3[] to replace slave_addr_version.
> ---
> drivers/i2c/busses/i2c-mt65xx.c | 43 +++++++++++++++++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drivers/i2c/busses/i2c-mt65xx.c
> index 8e6985354fd5..70aff42adf5d 100644
> --- a/drivers/i2c/busses/i2c-mt65xx.c
> +++ b/drivers/i2c/busses/i2c-mt65xx.c
> @@ -229,6 +229,35 @@ static const u16 mt_i2c_regs_v2[] = {
> [OFFSET_DCM_EN] = 0xf88,
> };
>
> +static const u16 mt_i2c_regs_v3[] = {
> + [OFFSET_DATA_PORT] = 0x0,
> + [OFFSET_SLAVE_ADDR] = 0x94,
> + [OFFSET_INTR_MASK] = 0x8,
> + [OFFSET_INTR_STAT] = 0xc,
> + [OFFSET_CONTROL] = 0x10,
> + [OFFSET_TRANSFER_LEN] = 0x14,
> + [OFFSET_TRANSAC_LEN] = 0x18,
> + [OFFSET_DELAY_LEN] = 0x1c,
> + [OFFSET_TIMING] = 0x20,
> + [OFFSET_START] = 0x24,
> + [OFFSET_EXT_CONF] = 0x28,
> + [OFFSET_LTIMING] = 0x2c,
> + [OFFSET_HS] = 0x30,
> + [OFFSET_IO_CONFIG] = 0x34,
> + [OFFSET_FIFO_ADDR_CLR] = 0x38,
> + [OFFSET_SDA_TIMING] = 0x3c,
> + [OFFSET_TRANSFER_LEN_AUX] = 0x44,
> + [OFFSET_CLOCK_DIV] = 0x48,
> + [OFFSET_SOFTRESET] = 0x50,
> + [OFFSET_MULTI_DMA] = 0x8c,
> + [OFFSET_SCL_MIS_COMP_POINT] = 0x90,
> + [OFFSET_DEBUGSTAT] = 0xe4,
> + [OFFSET_DEBUGCTRL] = 0xe8,
> + [OFFSET_FIFO_STAT] = 0xf4,
> + [OFFSET_FIFO_THRESH] = 0xf8,
> + [OFFSET_DCM_EN] = 0xf88,
> +};
> +
> struct mtk_i2c_compatible {
> const struct i2c_adapter_quirks *quirks;
> const u16 *regs;
> @@ -442,6 +471,19 @@ static const struct mtk_i2c_compatible mt8186_compat = {
> .max_dma_support = 36,
> };
>
> +static const struct mtk_i2c_compatible mt8188_compat = {
> + .regs = mt_i2c_regs_v3,
> + .pmic_i2c = 0,
> + .dcm = 0,
> + .auto_restart = 1,
> + .aux_len_reg = 1,
> + .timing_adjust = 1,
> + .dma_sync = 0,
> + .ltiming_adjust = 1,
> + .apdma_sync = 1,
> + .max_dma_support = 36,
> +};
> +
> static const struct mtk_i2c_compatible mt8192_compat = {
> .quirks = &mt8183_i2c_quirks,
> .regs = mt_i2c_regs_v2,
> @@ -465,6 +507,7 @@ static const struct of_device_id mtk_i2c_of_match[] = {
> { .compatible = "mediatek,mt8173-i2c", .data = &mt8173_compat },
> { .compatible = "mediatek,mt8183-i2c", .data = &mt8183_compat },
> { .compatible = "mediatek,mt8186-i2c", .data = &mt8186_compat },
> + { .compatible = "mediatek,mt8188-i2c", .data = &mt8188_compat },
> { .compatible = "mediatek,mt8192-i2c", .data = &mt8192_compat },
> {}
> };
next prev parent reply other threads:[~2022-07-08 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 3:47 [RESEND v4 1/2] dt-bindings: i2c: update bindings for MT8188 SoC kewei.xu
2022-07-08 3:47 ` [RESEND v4 2/2] i2c: mediatek: Add i2c compatible for Mediatek MT8188 kewei.xu
2022-07-08 8:08 ` Matthias Brugger [this message]
2022-07-08 8:13 ` AngeloGioacchino Del Regno
2022-07-08 8:09 ` [RESEND v4 1/2] dt-bindings: i2c: update bindings for MT8188 SoC Matthias Brugger
2022-07-11 22:51 ` Rob Herring
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=81af48c4-757c-384d-9a96-9cf16acb317c@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=caiyu.chen@mediatek.com \
--cc=david-yh.chiu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=housong.zhang@mediatek.com \
--cc=kewei.xu@mediatek.com \
--cc=leilk.liu@mediatek.com \
--cc=liguo.zhang@mediatek.com \
--cc=liju-clr.chen@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=qii.wang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
--cc=yuhan.wei@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).