From: Wolfram Sang <wsa@kernel.org>
To: Boris Lysov <arzamas-16@mail.ee>
Cc: linux-i2c@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, qii.wang@mediatek.com
Subject: Re: [PATCH 2/2] i2c: mediatek: remove mt6577 support
Date: Sun, 17 Apr 2022 04:21:00 +0200 [thread overview]
Message-ID: <Ylt5jNRmcuz3/rfc@shikoro> (raw)
In-Reply-To: <20220120185853.24266-3-arzamas-16@mail.ee>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Thu, Jan 20, 2022 at 09:58:53PM +0300, Boris Lysov wrote:
> The mt6577 compatibility was introduced back in 2014 in commit 8452c80d5b4b
> ("I2C: mediatek: Add driver for MediaTek I2C controller") by Xudong Chen.
>
> The i2c-mt65xx driver relies on DMA since it was first introduced. mt6577 does
> not support DMA [1] for I2C and doesn't have dedicated DMA engines for I2C.
> Moreover, the entire mt65xx Cortex-A9 SoC family (mt6515, mt6517, mt6575,
> and mt6577) which share the same I2C IP doesn't support I2C DMA at all which
> makes this particular driver incompatible with these SoCs.
>
> The existing code used mt6577 as a "generic" configuration to be used with
> other SoCs such as mt6589 (for quirks), and mt2701/mt6797/mt7623 (in general).
>
> This patch makes mt2701 (which is *actually* supported by this driver) a new
> placeholder for generic Mediatek I2C bus configuration.
>
> [1] see references in
> https://lists.infradead.org/pipermail/linux-mediatek/2021-October/030333.html
>
> Signed-off-by: Boris Lysov <arzamas-16@mail.ee>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-17 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:58 [PATCH 0/2] i2c: mediatek: remove mt6577 support Boris Lysov
2022-01-20 18:58 ` [PATCH 1/2] dt-bindings: i2c: i2c-mt65xx: " Boris Lysov
2022-04-17 2:20 ` Wolfram Sang
2022-01-20 18:58 ` [PATCH 2/2] i2c: mediatek: " Boris Lysov
2022-04-17 2:21 ` Wolfram Sang [this message]
2022-03-01 15:19 ` [PATCH 0/2] " Wolfram Sang
2022-03-18 11:09 ` Wolfram Sang
2022-04-16 15:10 ` Boris Lysov
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=Ylt5jNRmcuz3/rfc@shikoro \
--to=wsa@kernel.org \
--cc=arzamas-16@mail.ee \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=qii.wang@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).