From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E262C433F5 for ; Sat, 16 Apr 2022 15:16:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231328AbiDPPTM (ORCPT ); Sat, 16 Apr 2022 11:19:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232406AbiDPPTG (ORCPT ); Sat, 16 Apr 2022 11:19:06 -0400 X-Greylist: delayed 341 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Sat, 16 Apr 2022 08:16:33 PDT Received: from eu-shark1.inbox.eu (eu-shark1.inbox.eu [195.216.236.81]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1725FDB9 for ; Sat, 16 Apr 2022 08:16:32 -0700 (PDT) Received: from eu-shark1.inbox.eu (localhost [127.0.0.1]) by eu-shark1-out.inbox.eu (Postfix) with ESMTP id 35DD06C006BD; Sat, 16 Apr 2022 18:10:48 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.ee; s=20150108; t=1650121848; x=1650123648; bh=KK9C41l79QaB3TJiC3RV4T0lUXme7J8u5KVG2q+8QHw=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: Content-Type:X-ESPOL:From:Date:To:Cc:Message-ID:Subject:Reply-To; b=xTU201XbBCuHBaMi53sGK3esB55DOtLIPvaHFo22pPPWz2qZSznD+rEVYMWNc+b7L Q83hIyigv8kkN4aQ9KGne/eiHNvXE9L3d61rQzI1fMrnCe3fWim4FU30ceXatdCK1h Plm6r52aJ7zINqDq7DfUPiYQoYqNMLmP8vn4HtQ0= Received: from localhost (localhost [127.0.0.1]) by eu-shark1-in.inbox.eu (Postfix) with ESMTP id 254D86C006BE; Sat, 16 Apr 2022 18:10:48 +0300 (EEST) Received: from eu-shark1.inbox.eu ([127.0.0.1]) by localhost (eu-shark1.inbox.eu [127.0.0.1]) (spamfilter, port 35) with ESMTP id DgtGkDb-qW45; Sat, 16 Apr 2022 18:10:48 +0300 (EEST) Received: from mail.inbox.eu (eu-pop1 [127.0.0.1]) by eu-shark1-in.inbox.eu (Postfix) with ESMTP id E05746C006BD; Sat, 16 Apr 2022 18:10:47 +0300 (EEST) Date: Sat, 16 Apr 2022 18:10:41 +0300 From: Boris Lysov To: Wolfram Sang 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 Message-ID: <20220416181041.31ec5f65@pc> In-Reply-To: References: <20220120185853.24266-1-arzamas-16@mail.ee> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: OK X-ESPOL: 885mlYNLBD+si0CgRH7ABAc3s1k3Ua26u/vYoxBcgBmOPC+Bd04PWBSzmW9qPg+1ykoX Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org On Fri, 18 Mar 2022 12:09:42 +0100 Wolfram Sang 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?