From: Boris Lysov <arzamas-16@mail.ee>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, qii.wang@mediatek.com
Subject: Re: [PATCH 0/2] i2c: mediatek: remove mt6577 support
Date: Sat, 16 Apr 2022 18:10:41 +0300 [thread overview]
Message-ID: <20220416181041.31ec5f65@pc> (raw)
In-Reply-To: <YjRodtoWRhlNUg14@shikoro>
On Fri, 18 Mar 2022 12:09:42 +0100
Wolfram Sang <wsa@kernel.org> wrote:
> On Tue, Mar 01, 2022 at 04:19:56PM +0100, Wolfram Sang wrote:
> > On Thu, Jan 20, 2022 at 09:58:51PM +0300, Boris Lysov wrote:
> > > This small patch series removes mt6577 support from the i2c-mt65xx driver
> > > and devicectree binding documentation.
> > >
> > > The existing i2c-mt65xx driver relies on DMA since it was first
> > > introduced. mt6577 does not support DMA [1] for I2C and SoC's Generic DMA
> > > engine cannot be used for this purpose, too, which makes this particular
> > > driver incompatible with mt6577 and other similar SoCs with same I2C IP.
> >
> > Qii Wang, what do you think about this series?
>
> This series makes sense to me. If you do not disagree, Qii Wang, I will
> apply it soon. All the best, everyone.
Hello! I'm kindly pinging you on this series. Has it been applied?
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Boris Lysov <arzamas-16@mail.ee>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, qii.wang@mediatek.com
Subject: Re: [PATCH 0/2] i2c: mediatek: remove mt6577 support
Date: Sat, 16 Apr 2022 18:10:41 +0300 [thread overview]
Message-ID: <20220416181041.31ec5f65@pc> (raw)
In-Reply-To: <YjRodtoWRhlNUg14@shikoro>
On Fri, 18 Mar 2022 12:09:42 +0100
Wolfram Sang <wsa@kernel.org> wrote:
> On Tue, Mar 01, 2022 at 04:19:56PM +0100, Wolfram Sang wrote:
> > On Thu, Jan 20, 2022 at 09:58:51PM +0300, Boris Lysov wrote:
> > > This small patch series removes mt6577 support from the i2c-mt65xx driver
> > > and devicectree binding documentation.
> > >
> > > The existing i2c-mt65xx driver relies on DMA since it was first
> > > introduced. mt6577 does not support DMA [1] for I2C and SoC's Generic DMA
> > > engine cannot be used for this purpose, too, which makes this particular
> > > driver incompatible with mt6577 and other similar SoCs with same I2C IP.
> >
> > Qii Wang, what do you think about this series?
>
> This series makes sense to me. If you do not disagree, Qii Wang, I will
> apply it soon. All the best, everyone.
Hello! I'm kindly pinging you on this series. Has it been applied?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Boris Lysov <arzamas-16@mail.ee>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, qii.wang@mediatek.com
Subject: Re: [PATCH 0/2] i2c: mediatek: remove mt6577 support
Date: Sat, 16 Apr 2022 18:10:41 +0300 [thread overview]
Message-ID: <20220416181041.31ec5f65@pc> (raw)
In-Reply-To: <YjRodtoWRhlNUg14@shikoro>
On Fri, 18 Mar 2022 12:09:42 +0100
Wolfram Sang <wsa@kernel.org> wrote:
> On Tue, Mar 01, 2022 at 04:19:56PM +0100, Wolfram Sang wrote:
> > On Thu, Jan 20, 2022 at 09:58:51PM +0300, Boris Lysov wrote:
> > > This small patch series removes mt6577 support from the i2c-mt65xx driver
> > > and devicectree binding documentation.
> > >
> > > The existing i2c-mt65xx driver relies on DMA since it was first
> > > introduced. mt6577 does not support DMA [1] for I2C and SoC's Generic DMA
> > > engine cannot be used for this purpose, too, which makes this particular
> > > driver incompatible with mt6577 and other similar SoCs with same I2C IP.
> >
> > Qii Wang, what do you think about this series?
>
> This series makes sense to me. If you do not disagree, Qii Wang, I will
> apply it soon. All the best, everyone.
Hello! I'm kindly pinging you on this series. Has it been applied?
next prev parent reply other threads:[~2022-04-16 15:11 UTC|newest]
Thread overview: 24+ 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 ` Boris Lysov
2022-01-20 18:58 ` Boris Lysov
2022-01-20 18:58 ` [PATCH 1/2] dt-bindings: i2c: i2c-mt65xx: " Boris Lysov
2022-01-20 18:58 ` Boris Lysov
2022-01-20 18:58 ` Boris Lysov
2022-04-17 2:20 ` Wolfram Sang
2022-04-17 2:20 ` Wolfram Sang
2022-04-17 2:20 ` Wolfram Sang
2022-01-20 18:58 ` [PATCH 2/2] i2c: mediatek: " Boris Lysov
2022-01-20 18:58 ` Boris Lysov
2022-01-20 18:58 ` Boris Lysov
2022-04-17 2:21 ` Wolfram Sang
2022-04-17 2:21 ` Wolfram Sang
2022-04-17 2:21 ` Wolfram Sang
2022-03-01 15:19 ` [PATCH 0/2] " Wolfram Sang
2022-03-01 15:19 ` Wolfram Sang
2022-03-01 15:19 ` Wolfram Sang
2022-03-18 11:09 ` Wolfram Sang
2022-03-18 11:09 ` Wolfram Sang
2022-03-18 11:09 ` Wolfram Sang
2022-04-16 15:10 ` Boris Lysov [this message]
2022-04-16 15:10 ` Boris Lysov
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=20220416181041.31ec5f65@pc \
--to=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 \
--cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.