Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp5281115rwd; Mon, 5 Jun 2023 00:53:50 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ60q9wmmVaYfhEUl1gsFrddQsxm+DWIcxHja0bR4NsjHDKEzcgngaX4rsls83uq1fdUKs3y X-Received: by 2002:a05:6808:8ce:b0:38d:fdf2:962e with SMTP id k14-20020a05680808ce00b0038dfdf2962emr7005173oij.23.1685951630741; Mon, 05 Jun 2023 00:53:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685951630; cv=none; d=google.com; s=arc-20160816; b=NDONAufLXx6+0yS2pEz1T8ZbUVrBLxVMYQJqQJd3tiV5dGEcwC+Sb8l91op8Ntpr7s qwR0x331Xr/O+h7apQ5eap+nykYQ71ukfm4st3SIpktZzAR6do6vmzb0h6HNxQLNR1bN S21NrBvTDYqxTVQy6qNcZNKU5GXjh9HiQ3rYDka1/M5HEpgMuV07g4qC4Dya4kYMrWYZ lIGGleCK3E6vl38En7hiPSxEhKXYivHQDUOkJ2EE9V+ZRoWDEpWbUc8ZzUI8FPM9poEA h9/ogyX39Dp/k+btjpIaX0dc/hjDRFlxJqTqMPUf9yb93uAnd0qGpYvIkhosRLuSkCR8 EpQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=Yr0hmvEPh2VZxgECVieKDFUBj0eK8JIqZd0VDYdbNwY=; b=BwzqMH09q9QYq+2W1SETfgdItogBb+r8/ghuSAx7MhRcGe4EVYWZQX8Cp2tz2RnWjd Up5B0oorVJCivWIPjhMRanZgIGJ8KWP6EqwGXfkPwRoNzzlw7LLr2aEKGvc/NekC+0ra g/PWLyGmHENMV/8z1OzkQZyO5pdovUpHxdo34Wy/jBT027qGp4Ec6Nr+kQMrCshAmHEr BwUucgYIWM6kedQCWVfcwIaMXXx/pRrfBec2xz1Il1yT92uNqjvvykU7aFkCZTtGSLya gDwGQ/ggUCmibYziZTc7Gjv5ogr1WdYQwBrQzkhbkyNvMGym2KgxOgggc9kEK0JcMG4q e0+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fX4XvsU7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z1-20020aa79e41000000b0064a15fc65d5si4901030pfq.83.2023.06.05.00.53.39; Mon, 05 Jun 2023 00:53:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fX4XvsU7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230502AbjFEHlk (ORCPT + 99 others); Mon, 5 Jun 2023 03:41:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34986 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231128AbjFEHld (ORCPT ); Mon, 5 Jun 2023 03:41:33 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3E27DFA; Mon, 5 Jun 2023 00:41:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1685950882; x=1717486882; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=THnIhnZPgYcez7jiZz9YZMWlzcLZYSgGI08ZGYeA+O0=; b=fX4XvsU7O9K6aQ5b7CIW7syYAyrv6+nC/k4qRGmCQXGaODrcF3wE8lPZ lAoqD7IFrGMKsK9OxsPEe8/tdgmdaDBbJDojDKeP+08IvOAj3r3KiZrYc ChZkIcvoxmzRziNUJtFlgQ0woOmlqqvPSwWhmgiHrLhuAm8C+v3kXiiHu bRC/+32fxk7Q8p1FJDbGDZgiiIUJbGbR+tuOBnyVh65W1JP/TH6qmETrb jp1A9ORi8OTP7fiM6BhTUH2gla7EC/d8kk3sK5+ZFDbuWu5MjJeE1RbLu AGWsV+oj8MztEqDJMSwF6TRcXuSbIYNrcH3iyoS1UpP94q1d7PshZh3ck w==; X-IronPort-AV: E=McAfee;i="6600,9927,10731"; a="358753388" X-IronPort-AV: E=Sophos;i="6.00,217,1681196400"; d="scan'208";a="358753388" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jun 2023 00:41:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10731"; a="658979036" X-IronPort-AV: E=Sophos;i="6.00,217,1681196400"; d="scan'208";a="658979036" Received: from mylly.fi.intel.com (HELO [10.237.72.143]) ([10.237.72.143]) by orsmga003.jf.intel.com with ESMTP; 05 Jun 2023 00:41:19 -0700 Message-ID: Date: Mon, 5 Jun 2023 10:41:18 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.11.0 Subject: Re: [PATCH v1] i2c: designware: Handle invalid SMBus block data response length To: Tam Chi Nguyen , Tam Nguyen , linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org Cc: patches@amperecomputing.com, andriy.shevchenko@linux.intel.com, mika.westerberg@linux.intel.com, jsd@semihalf.com, chuong@os.amperecomputing.com, darren@os.amperecomputing.com, stable@vger.kernel.org References: <20230523082118.10935-1-tamnguyenchi@os.amperecomputing.com> <6def5691-2462-9707-f75a-09931d26d4af@amperemail.onmicrosoft.com> <95d838d5-ea27-ef75-4ac6-575ebd75111a@amperemail.onmicrosoft.com> Content-Language: en-US From: Jarkko Nikula In-Reply-To: <95d838d5-ea27-ef75-4ac6-575ebd75111a@amperemail.onmicrosoft.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On 6/2/23 07:30, Tam Chi Nguyen wrote: > Hi Jarkko, > > Before pushing the v2 patch, I have one more question to ask. > > The commit f53f15ba5a85 ("i2c: designware: Get right data length"), you > mentioned, > does not handle bit 11 set (on a HW where it's supported) correctly. > "tmp" was not marked with DW_IC_DATA_CMD_DAT when passing to > i2c_dw_recv_len function. > > So I plan to update it in the v2 patch by adding this >     regmap_read(dev->map, DW_IC_DATA_CMD, &tmp); >     tmp &= DW_IC_DATA_CMD_DAT; > > My question is: does it need a separate patch for this change? > I think for now bit 11 gets masked since tmp variable is assigned to u8 variables when calling i2c_dw_recv_len() and writing to *buf pointer but your proposal indeed makes code more robust both your patch point of view or any other future change. So separate patch makes sense in my opinion.