Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp747532pxu; Fri, 23 Oct 2020 12:13:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw8KQd1WTEmtesd9uS5MQwz39WoWOGALYLDGSUwlL5B7LUqUJt1BK9tUvsawLIASSp84ToT X-Received: by 2002:a17:906:f6d8:: with SMTP id jo24mr1091791ejb.173.1603480425556; Fri, 23 Oct 2020 12:13:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603480425; cv=none; d=google.com; s=arc-20160816; b=nOh9Yh80mEBPaDcs1XbfH7MNVsc/WU+sxJLC03YprtZfoBsx6VkFBDm9GbvpwbZdhn kuFfBOVXCUoar9UT4fi4PHlkj+ZhM6xuodQpkqzfOXmiX/Qa0W0WZaU5Gifq6Wu8/arn T+hB0X+M1NQgD5nTcWMprliva3C8eTAHNIAmaWza9KUdam2b6cacv1qfrE6J3UvmM9cE j2luJ4uEgk1VsOOsJREUZN2uYcHmdHQtqWwHRvppXSF/sfDiFsSHjRP3OEbqhsO8yMOS muTNmhsik6Gq3XnCRS+WmussVHksAXqPf8/6tThT3fwf2vUq8BfRsf+7gcQGPMGWGgVk pk5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=J4Eh2qaJksTCTY1k45teLXaWXNH/ycvD9ltpm944k0Q=; b=Jq/AkX0MbM5Z7nOfzqNg84q8xoeyw109HEP3jw2R6MUpig7z6VYl5zXpeVFJTGRHV6 g1RU+Rv07WDgOsOji28RB9IsAvm8y7EO0Rw2VgbchArMDXFaJgL1YzqkyHyaUxU2lGTa wBiJ1NdIpL/ZG+qdAv/EOtT4zchMQ3EArup0+r93syKYj6k/5ge+DhYDRB7Un37NnE7J s4gWtaY/SL/DyxIxS3S2msSpDewXusTZEsl6MhGDrDJhu8pqjiU+KORzw/aU6W1VQs6G o1W/1ydeFFUz12CEMkNK6C3Lu2OkmAvbbS1oZDjnsdeDbv2up6tMJwW3z43BdVQLN/Mc 3YRQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lFi+TwD2; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v8si1426604ejx.1.2020.10.23.12.13.22; Fri, 23 Oct 2020 12:13:45 -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=@gmail.com header.s=20161025 header.b=lFi+TwD2; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S463684AbgJWSNh (ORCPT + 99 others); Fri, 23 Oct 2020 14:13:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36444 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S371522AbgJWSNg (ORCPT ); Fri, 23 Oct 2020 14:13:36 -0400 Received: from mail-ej1-x641.google.com (mail-ej1-x641.google.com [IPv6:2a00:1450:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0F173C0613CE; Fri, 23 Oct 2020 11:13:36 -0700 (PDT) Received: by mail-ej1-x641.google.com with SMTP id ce10so3606576ejc.5; Fri, 23 Oct 2020 11:13:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=J4Eh2qaJksTCTY1k45teLXaWXNH/ycvD9ltpm944k0Q=; b=lFi+TwD2vaAsrYHdJUzkp6N61fIOnh9+vKHJEudtGhn9CdTxA44JxC28ilTy4/53iD ZVNwMOqKf0jPH8k5codeD54T6uVec8mcd9Bk4K5U4bma2IoUpueoyD9uSEy78ml8VzRO LNcsCN+TUIF596XouiRcRboHJoyDTnt8yBoYr3qu92wlW8KRgB+TzWYlVReuER3Y9eT2 jBaT+9DrkKSorVSnG5g4Zfn+XCrfUPJ/o91TjhXX9BrbjUxSp4dT1zTe6EkvYKk2TaPf aS6qcZz5zum5mdHIKGuv52mVvYKDP6G+CICO+eYC4YmEc1rzn+QCRmmtN+LFmBJpr+C0 zX+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=J4Eh2qaJksTCTY1k45teLXaWXNH/ycvD9ltpm944k0Q=; b=knBbwYtSYwd0LSk7WLikukwbQiYOrhDlw4uQPcTrYtujXE3lLVQFr15dpoS6rYOb+U dwwF4ECWn7AKPVIYP9HoMySLRVDOEkFKl/Dd2yfP92Zs51jFMyCQAK/o9IAPb2+wTbGN 7PCkGbkn15y9aXidN77eDFxZs9pHtrhtoayk4D1r1gneuy96i2BZAlx/Kqs5woaQ/liX jghI7txD8oxUtJHNjt7LkhuJ4MoYZxYFagisZfgYyfzOQvHB5QadHe05XnnSC6RcXriP YJDXcZ94Xr+A0qxGqWlr0wHnWt6NkqzbExgYlra3X0lYZ20Whb9UnBVFgx2oF/Uxqctx /XPg== X-Gm-Message-State: AOAM531xyWfB4yg8rnp+RaxjhlyCsRGESwltdZhmMa0P8H/fy50zAMnM 4lE23ZULbmmHjiMVvIj4ZCxg7Bz/Pw0m3w== X-Received: by 2002:a17:906:12cf:: with SMTP id l15mr3434340ejb.540.1603476814307; Fri, 23 Oct 2020 11:13:34 -0700 (PDT) Received: from kista.localnet (cpe1-5-97.cable.triera.net. [213.161.5.97]) by smtp.gmail.com with ESMTPSA id k23sm1231498ejk.0.2020.10.23.11.13.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Oct 2020 11:13:32 -0700 (PDT) From: Jernej =?utf-8?B?xaBrcmFiZWM=?= To: linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org, linux-sunxi@googlegroups.com Cc: Mauro Carvalho Chehab , Rob Herring , Maxime Ripard , Chen-Yu Tsai , Yong Deng , Kishon Vijay Abraham I , Vinod Koul , Helen Koike , Greg Kroah-Hartman , Philipp Zabel , Paul Kocialkowski , Hans Verkuil , Sakari Ailus , Thomas Petazzoni , Hans Verkuil , kevin.lhopital@hotmail.com, paul.kocialkowski@bootlin.com Subject: Re: [linux-sunxi] [PATCH 01/14] phy: Distinguish between Rx and Tx for MIPI D-PHY with submodes Date: Fri, 23 Oct 2020 20:18:58 +0200 Message-ID: <7673189.jqQXtdQLJ6@kista> In-Reply-To: <20201023174546.504028-2-paul.kocialkowski@bootlin.com> References: <20201023174546.504028-1-paul.kocialkowski@bootlin.com> <20201023174546.504028-2-paul.kocialkowski@bootlin.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! Dne petek, 23. oktober 2020 ob 19:45:33 CEST je Paul Kocialkowski napisal(a): > As some D-PHY controllers support both Rx and Tx mode, we need a way for > users to explicitly request one or the other. For instance, Rx mode can > be used along with MIPI CSI-2 while Tx mode can be used with MIPI DSI. > > Introduce new MIPI D-PHY PHY submodes to use with PHY_MODE_MIPI_DPHY. > The default (zero value) is kept to Tx so only the rkisp1 driver, which > uses D-PHY in Rx mode, needs to be adapted. > > Signed-off-by: Paul Kocialkowski > --- > drivers/staging/media/rkisp1/rkisp1-isp.c | 3 ++- > include/linux/phy/phy-mipi-dphy.h | 13 +++++++++++++ I think some changes are missing in this patch. For example, phy_set_mode_ext() must be modified to take another argument, otherwise change of rkisp1-isp driver doesn't make much sense. Best regards, Jernej > 2 files changed, 15 insertions(+), 1 deletion(-) > > diff --git a/drivers/staging/media/rkisp1/rkisp1-isp.c b/drivers/staging/ media/rkisp1/rkisp1-isp.c > index 6ec1e9816e9f..0afbce00121e 100644 > --- a/drivers/staging/media/rkisp1/rkisp1-isp.c > +++ b/drivers/staging/media/rkisp1/rkisp1-isp.c > @@ -902,7 +902,8 @@ static int rkisp1_mipi_csi2_start(struct rkisp1_isp *isp, > > phy_mipi_dphy_get_default_config(pixel_clock, isp->sink_fmt- >bus_width, > sensor->lanes, cfg); > - phy_set_mode(sensor->dphy, PHY_MODE_MIPI_DPHY); > + phy_set_mode_ext(cdev->dphy, PHY_MODE_MIPI_DPHY, > + PHY_MIPI_DPHY_SUBMODE_RX); > phy_configure(sensor->dphy, &opts); > phy_power_on(sensor->dphy); > > diff --git a/include/linux/phy/phy-mipi-dphy.h b/include/linux/phy/phy-mipi- dphy.h > index a877ffee845d..0f57ef46a8b5 100644 > --- a/include/linux/phy/phy-mipi-dphy.h > +++ b/include/linux/phy/phy-mipi-dphy.h > @@ -6,6 +6,19 @@ > #ifndef __PHY_MIPI_DPHY_H_ > #define __PHY_MIPI_DPHY_H_ > > +/** > + * enum phy_mipi_dphy_submode - MIPI D-PHY sub-mode > + * > + * A MIPI D-PHY can be used to transmit or receive data. > + * Since some controllers can support both, the direction to enable is specified > + * with the PHY sub-mode. Transmit is assumed by default with phy_set_mode. > + */ > + > +enum phy_mipi_dphy_submode { > + PHY_MIPI_DPHY_SUBMODE_TX = 0, > + PHY_MIPI_DPHY_SUBMODE_RX, > +}; > + > /** > * struct phy_configure_opts_mipi_dphy - MIPI D-PHY configuration set > * > -- > 2.28.0 > > -- > You received this message because you are subscribed to the Google Groups "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe@googlegroups.com. > To view this discussion on the web, visit https://groups.google.com/d/msgid/ linux-sunxi/20201023174546.504028-2-paul.kocialkowski%40bootlin.com. >