Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp318452ybj; Mon, 4 May 2020 22:23:33 -0700 (PDT) X-Google-Smtp-Source: APiQypIcqReukBaVCsP1sIFmqZNd5nSY5kPUFjXutJT5NqALMgbqoDj34UtD8s8IY5CZ5upa5UfN X-Received: by 2002:a50:ba83:: with SMTP id x3mr1015490ede.193.1588656212773; Mon, 04 May 2020 22:23:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588656212; cv=none; d=google.com; s=arc-20160816; b=gB8GRkoaZeGAvHSAn4jx89oEnAVDihPyfee2216xCiIkSOjkCqhp0jx3KVBTC96Woa 68VxBDyHg46gF3wKlnOUzWInYCjlbMM6CB3ndqHNBQ3aQdLVwrspmSpnCWl4vhPDdfmC ycjHCIah5iTQm9pFK/bJt0dXg8eMiG6k/hurEFh1YrLhaMkIabgwXjlWAWLGbPOFFj62 0jKJSbP7hwCzk1OknZee9Z+QNft7p6ciWVFVykPva0x0Xwz8y4DgoptBQngwYyg5jr73 RAm1S9LdhdKHXSat7zvsIOkdgTCIgkka2Q34ZKkZh22ZDUHGojDdekEgczjeiEK6xLOr 4gBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=Up7pR6ShVMZWc8PGwIAYc5a/u4u5pyLlL5XTs+vNbds=; b=RnmshfxFgIvuTnch+Ue3maJFTuHz4ZCAKjO30tolig2i5UqJe/OMJw85nHKbiPzWpZ 3xughkOmK4WU2bFBx9K0R+6SXkK4X/C1izv7HVTy4Z/WXGcOOwJ/Sqr4Z0bBdHcZiJ9+ hBk1arRMjP7N51w3k1jz19L6NKE3wVM/9gjprMBovaUSl1KsjO2O2i4BFMu5e9KWwqX2 V8Zn/ZDomvYZgWqwvULeOCtg0lcICbrCm73++R1TI+2Xnf3KG5YVh51OUeDBzBXridB/ iWZFfXnrZzRi4D4q8f8CE/+iqA/WPOsA8Fj5tWmClBldnXLI4K0YATHS9MnIr4S/+jhp 0Ffw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=sDbWqchG; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a19si418296ejt.117.2020.05.04.22.23.09; Mon, 04 May 2020 22:23:32 -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; dkim=pass header.i=@kernel.org header.s=default header.b=sDbWqchG; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726568AbgEEFV1 (ORCPT + 99 others); Tue, 5 May 2020 01:21:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:42932 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725320AbgEEFV1 (ORCPT ); Tue, 5 May 2020 01:21:27 -0400 Received: from localhost (unknown [171.61.99.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 880C4206FA; Tue, 5 May 2020 05:21:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588656086; bh=Y2jL3pSvPWYflkCioX814L9QG12+dvqUxYSa5B3DQp8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sDbWqchGcvTFtjPTOVNucbIEpIesP5OdB7LGUFpSLW7FxtiCA8gY83OzmTfKXw0PT p/qCIPshq5bbEWbHKDN08JXowaeclj+PH7R+h6HkBSOA0vTTwV9fBf7JYaG1PJ7qbO 2CHeCmY1+Td2N6K3rx/hCsQAumHFe7tnI5b9yVyM= Date: Tue, 5 May 2020 10:51:22 +0530 From: Vinod Koul To: Dilip Kota Cc: linux-kernel@vger.kernel.org, kishon@ti.com, devicetree@vger.kernel.org, lee.jones@linaro.org, arnd@arndb.de, robh@kernel.org, andriy.shevchenko@intel.com, cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com, yixin.zhu@intel.com Subject: Re: [PATCH v7 3/3] phy: intel: Add driver support for ComboPhy Message-ID: <20200505052122.GW1375924@vkoul-mobl> References: <20200504072923.GN1375924@vkoul-mobl> <20200504092034.GS1375924@vkoul-mobl> <0de7ba47-bc98-9267-46b4-230a86151c2d@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0de7ba47-bc98-9267-46b4-230a86151c2d@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04-05-20, 17:32, Dilip Kota wrote: > > On 5/4/2020 5:20 PM, Vinod Koul wrote: > > On 04-05-20, 16:26, Dilip Kota wrote: > > > On 5/4/2020 3:29 PM, Vinod Koul wrote: > > > > On 30-04-20, 15:15, Dilip Kota wrote: > > > > > > > > > + u32 mask, u32 val) > > > > > +{ > > > > > + u32 reg_val; > > > > > + > > > > > + reg_val = readl(base + reg); > > > > > + reg_val &= ~mask; > > > > > + reg_val |= FIELD_PREP(mask, val); > > > > > + writel(reg_val, base + reg); > > > > bypassing regmap here... why? > > > It is not regmap address, one of the below two addresses are passed to this > > > function. > > okay, perhaps add a comment somewhere that regmap is not used for this > > base? > I dont see a need of adding a comment, describing don't do regmap here. Driver uses regmap except here, which seems odd hence explanation required for this. > > > > > struct intel_combo_phy { > > > ... > > > ??????? void __iomem??????????? *app_base; > > > ??????? void __iomem??????????? *cr_base; > > > ... > > > } > > > > > > > +static int intel_cbphy_calibrate(struct phy *phy) > > > > > +{ > > > > > + struct intel_cbphy_iphy *iphy = phy_get_drvdata(phy); > > > > > + struct intel_combo_phy *cbphy = iphy->parent; > > > > > + void __iomem *cr_base = cbphy->cr_base; > > > > > + int val, ret, id; > > > > > + > > > > > + if (cbphy->phy_mode != PHY_XPCS_MODE) > > > > > + return 0; > > > > > + > > > > > + id = PHY_ID(iphy); > > > > > + > > > > > + /* trigger auto RX adaptation */ > > > > > + combo_phy_w32_off_mask(cr_base, CR_ADDR(PCS_XF_ATE_OVRD_IN_2, id), > > > > > + ADAPT_REQ_MSK, 3); > > > > > + /* Wait RX adaptation to finish */ > > > > > + ret = readl_poll_timeout(cr_base + CR_ADDR(PCS_XF_RX_ADAPT_ACK, id), > > > > > + val, val & RX_ADAPT_ACK_BIT, 10, 5000); > > > > > + if (ret) > > > > > + dev_err(cbphy->dev, "RX Adaptation failed!\n"); > > > > you want to continue her and not return error? > > > Next step is stopping the Adaptation, it should be done in both error and > > > success case. > > Again documenting this helps, pls add some comments on this behaviour > Comments are already in place, mentioning Start and Stop of Rx Adaptation. > And Stop is being is done as Start is triggered, so not needed to mention > error and success. Ok -- ~Vinod