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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 520E5C433FE for ; Thu, 18 Nov 2021 10:35:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3754960F51 for ; Thu, 18 Nov 2021 10:35:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245672AbhKRKik (ORCPT ); Thu, 18 Nov 2021 05:38:40 -0500 Received: from esa3.mentor.iphmx.com ([68.232.137.180]:48291 "EHLO esa3.mentor.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245687AbhKRKiR (ORCPT ); Thu, 18 Nov 2021 05:38:17 -0500 IronPort-SDR: XRc2SeJvfvatwcyIZv1bptwbSuK8HS6MKhiMqGuWcfUg8KaZ9v6jGGaZoCh3o38LsG0q8FBBnz +ZmU/KwpJtuKU8rweNLpZWsqmo5gdpeYdjl313Vx+AyCYccOYlBZkKuOLqOiWTQqcnzIxkKllD Q5ca9y5TQlBYpKlYnVsO8zXLNnigannIaGqTG9WtkD2U5CB6BZMs5RKIXeBqYgXnYvONM+P/qk qrCBKO4GK+WKYpBii+t6I76mq+/Hl4aMnlrcWByWCpiBAjnMM8bAShxfkB1qyLH5wCHkWnvtJQ t77tS8kVlUPjQ+SbywGjftDJ X-IronPort-AV: E=Sophos;i="5.87,244,1631606400"; d="scan'208";a="68500610" Received: from orw-gwy-02-in.mentorg.com ([192.94.38.167]) by esa3.mentor.iphmx.com with ESMTP; 18 Nov 2021 02:35:16 -0800 IronPort-SDR: GNS320mbJC4QmFu1VPRCRHkweYFzarWcwiyi7hZNYXUtE6MbvKGUMuJ7KCLSGF1SMOI1dbTm1b vwRAFhYoeXuLJ4og6vzJhkWyeLygFH/pqMhYnoSUUL/W1MbmdJkiSz5skfQE3YoEiN/RXY44mt xuKSy0nCB6v1SwlQw3vD0N2p6y+sL8kEedtlqb9j/fDT0be3RF61ndKFiI5TNctQDnCIfiIR2u n/NDDP3FxoNaGa7T+48a07Zvicm+6F3Xr/HBbOH8/FAigHu1OhmZDowll11cLbNip3J+MuJXKE 3io= From: Andrew Gabbasov To: 'Geert Uytterhoeven' CC: 'Linux-Renesas' , 'Linux I2C' , 'Linux Kernel Mailing List' , 'Wolfram Sang' , "Surachari, Bhuvanesh" References: <20210922160649.28449-1-andrew_gabbasov@mentor.com> In-Reply-To: Subject: RE: [PATCH] i2c: rcar: add SMBus block read support Date: Thu, 18 Nov 2021 13:35:02 +0300 Organization: Mentor Graphics Corporation Message-ID: <000001d7dc67$f695e5c0$e3c1b140$@mentor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHXue1eCQdNXjaiK021FrevUeTu7qvGRbCQgEMVGxA= Content-Language: en-us X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org Hello Geert, Wolfram, Do you have any feedback on version 2 of this patch, that was submitted after your review comments below? https://lore.kernel.org/all/20211006182314.10585-1-andrew_gabbasov@mentor.com/ Thanks! Best regards, Andrew > -----Original Message----- > From: Andrew Gabbasov > Sent: Wednesday, October 06, 2021 9:12 PM > To: 'Geert Uytterhoeven' > Cc: Linux-Renesas ; Linux I2C ; Linux Kernel > Mailing List ; Wolfram Sang ; Surachari, > Bhuvanesh > Subject: RE: [PATCH] i2c: rcar: add SMBus block read support > > Hi Geert, > > Thank you for your review! > > > -----Original Message----- > > From: Geert Uytterhoeven > > Sent: Tuesday, October 05, 2021 4:32 PM > > To: Gabbasov, Andrew > > Cc: Linux-Renesas ; Linux I2C ; Linux Kernel > > Mailing List ; Wolfram Sang ; Surachari, > > Bhuvanesh > > Subject: Re: [PATCH] i2c: rcar: add SMBus block read support > > > > Hi Andrew, > > > > On Wed, Sep 22, 2021 at 6:14 PM Andrew Gabbasov > > wrote: > > > The smbus block read is not currently supported for rcar i2c devices. > > > This patchset adds the support to rcar i2c bus so that blocks of data > > > can be read using SMbus block reads.(using i2c_smbus_read_block_data() > > > function from the i2c-core-smbus.c). > > > > > > Inspired by commit 8e8782c71595 ("i2c: imx: add SMBus block read support") > > > > > > This patch (adapted) was tested with v4.14, but due to lack of real > > > hardware with SMBus block read operations support, using "simulation", > > > that is manual analysis of data, read from plain I2C devices with > > > SMBus block read request. > > > > > > Signed-off-by: Bhuvanesh Surachari > > > Signed-off-by: Andrew Gabbasov > > > > Thanks for your patch! > > > > > --- a/drivers/i2c/busses/i2c-rcar.c > > > +++ b/drivers/i2c/busses/i2c-rcar.c > > > @@ -429,9 +431,16 @@ static bool rcar_i2c_dma(struct rcar_i2c_priv *priv) > > > /* > > > * The last two bytes needs to be fetched using PIO in > > > * order for the STOP phase to work. > > > + * > > > + * For SMBus block read the first byte was received using PIO. > > > > So it might be easier to read, and more maintainable, to keep the > > old assignments: > > > > buf = priv->msg->buf; > > len = priv->msg->len - 2; > > > > and adjust them for SMBus afterwards: > > > > if (block_data) { > > /* For SMBus block read the first byte was received using PIO */ > > buf++; > > len--; > > } > > > > ? > > > > > */ > > > - buf = priv->msg->buf; > > > - len = priv->msg->len - 2; > > > + if (block_data) { > > > + buf = priv->msg->buf + 1; > > > + len = priv->msg->len - 3; > > > + } else { > > > + buf = priv->msg->buf; > > > + len = priv->msg->len - 2; > > > + } > > > } else { > > > /* > > > * First byte in message was sent using PIO. > > > > And below we have another case handling buf and len :-( > > > > So perhaps: > > > > buf = priv->msg->buf; > > len = priv->msg->len; > > > > if (read) { > > /* > > * The last two bytes needs to be fetched using PIO in > > * order for the STOP phase to work. > > */ > > len -= 2; > > } > > if (!read || block_data) { > > /* First byte in message was sent using PIO * > > buf++; > > len--; > > } > > Probably I was trying to minimize the changes ;-) > > However, I agree with you that the whole code fragment can be simplified > and your variant indeed looks more clean and understandable. > Thank you for your suggestion, I'll submit version 2 of the patch > with this fragment changed. > > Thanks! > > Best regards, > Andrew