Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp190961pxf; Thu, 8 Apr 2021 00:18:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyspmpACrF5nsTIG+d9Emmj+5jqEwvFBPg4hHflS1DdYQkDWLAf8qN6GL59h/IVmvk+9a75 X-Received: by 2002:a17:90a:d902:: with SMTP id c2mr6712245pjv.152.1617866303602; Thu, 08 Apr 2021 00:18:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617866303; cv=none; d=google.com; s=arc-20160816; b=vibGIdM6wlS7y+VgD2JqWfVtzd9BaNPI+qDLwd0SwtnpfEClhoWYYEFKLP11rfvGeC haQU1Ri+1wflTXAdEDh9WDqc8OZPbn6BO7dxBrashMTOsNaGYwZNwN6uwlTf45Ym7U0P vyePZHdZ67oFVaW+4Rk0nsZk2JD1LEuOYfnUr3srww/OlFtJH0DkLBiziR0MKfv4uFz+ y9fEUT8yzy3egLfs3pKXZqtkg4k48TXLhM71yktF439jzmM3cbVSUT7xFuIIKwCr66bC Xm3688ItbK2aKiZKnyhgoaSZ9NmeFWyfbM6URdJQWQce0nVRlg8WyorxaBX8YQl10zvz GDJA== 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 :mime-version:user-agent:date:message-id:from:references:to:subject; bh=ex5g5YJ2uR4TbkBYZrf8kL12zaIV+ouI5lr1asNukFk=; b=HnwpZd35mJBpk29ajAhjD6roZvjeuwfpDdsoqwUUxaY59C3MCmaWDHMIk4fY1GthQJ A3P3rfpV5SMgvCiTf55s9NKFAKk6EDxt517ft/scZGe3p6p2bEIqKE6SaUxXOtCMIMxw X2zWlsa8azs86UK4Cs55Cfq83Ls2fVT/xmpbYUTl4Wc4TfSoCdoUUDxEZ4J2VQZGsuuT LQP0r7XZ81HeaJkGh3McosxMaCxzAs8roZTiC1kzqgcq8uKvpJ4YxDSKn7cbs06CjqPQ 76GKxo+Ygh5NcRGAFceHsdnqY3Kb8lupByh0OBSv6CcX6sCYCri3gtBhxR51j4Ajjlzj BVOg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hisilicon.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m17si26639187pgb.391.2021.04.08.00.18.10; Thu, 08 Apr 2021 00:18:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hisilicon.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229602AbhDHHR3 (ORCPT + 99 others); Thu, 8 Apr 2021 03:17:29 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:16079 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229510AbhDHHR3 (ORCPT ); Thu, 8 Apr 2021 03:17:29 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4FGCFj44JWz1BGL8; Thu, 8 Apr 2021 15:15:05 +0800 (CST) Received: from [127.0.0.1] (10.69.38.196) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.498.0; Thu, 8 Apr 2021 15:17:07 +0800 Subject: Re: [PATCH v6 3/5] i2c: add support for HiSilicon I2C controller To: Wolfram Sang , Jarkko Nikula , , , , , , , , , , , , References: <1617197790-30627-1-git-send-email-yangyicong@hisilicon.com> <1617197790-30627-4-git-send-email-yangyicong@hisilicon.com> <20210407230421.GB860@kunai> From: Yicong Yang Message-ID: <5c478c9b-fc2a-2dd7-6191-8f68e265c2f7@hisilicon.com> Date: Thu, 8 Apr 2021 15:17:07 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <20210407230421.GB860@kunai> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.69.38.196] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/4/8 7:04, Wolfram Sang wrote: > >> Reason for temp variable is for me it's confusing to see statement like >> "rate_khz = rate_khz / 1000". > > Yes. And with this clearer calculation, we can maybe skip the HZ_PER_KHZ > define completely and just use plain '1000' as a factor/divider because > it then becomes obvious. I still find the define more confusing than > helpful TBH. But I'll leave the final decision to Yicong Yang. > HZ_PER_KHZ macro are defined separately in other places of the kernel. Andy suggested to have this defined and used so that one day we can factor this macro out to the public. :)