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 X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4EDA5C433E2 for ; Wed, 16 Sep 2020 07:41:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ED16B2078D for ; Wed, 16 Sep 2020 07:41:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="KxF1FxOK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726414AbgIPHlc (ORCPT ); Wed, 16 Sep 2020 03:41:32 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:36158 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726159AbgIPHlb (ORCPT ); Wed, 16 Sep 2020 03:41:31 -0400 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 08G7fM12077914; Wed, 16 Sep 2020 02:41:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1600242082; bh=WohhcHNTIV/ovv97AWxzinKNg6nq6ImDJaomVMGpR50=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=KxF1FxOKY6U6oLU2s0j/Cek6Fhz2SKoWKjgZfED/5iPC1FwS6SBZx8cAquKYcCDSV ykFmMW3FfxR+fjawhUFJHwKvF9b4awYxLIlGKV34ujZdaCRR/ZB5VftntULcAJqasi Ewuyuuekg2qG21UfPLTIjC13DVBr0oChLzIVWnXY= Received: from DLEE114.ent.ti.com (dlee114.ent.ti.com [157.170.170.25]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTP id 08G7fMhG095493; Wed, 16 Sep 2020 02:41:22 -0500 Received: from DLEE112.ent.ti.com (157.170.170.23) by DLEE114.ent.ti.com (157.170.170.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Wed, 16 Sep 2020 02:41:22 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE112.ent.ti.com (157.170.170.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Wed, 16 Sep 2020 02:41:22 -0500 Received: from [10.24.69.198] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 08G7fIqw095952; Wed, 16 Sep 2020 02:41:19 -0500 Subject: Re: [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate To: Swapnil Jakhade , , , , , CC: , , , , References: <1599805114-22063-1-git-send-email-sjakhade@cadence.com> From: Sekhar Nori Message-ID: Date: Wed, 16 Sep 2020 13:11:17 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <1599805114-22063-1-git-send-email-sjakhade@cadence.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vinod, On 11/09/20 11:48 AM, Swapnil Jakhade wrote: > This patch series adds a new PHY attribute max_link_rate. > It also updates Cadence Torrent PHY driver to set attributes bus_width, > max_link_rate and mode for DisplayPort. > > It includes following patches: > > 1. 0001-phy-Add-new-PHY-attribute-max_link_rate.patch > This patch adds max_link_rate as a new PHY attribute. > > 2. 0002-phy-cadence-torrent-Set-Torrent-PHY-attributes.patch > This patch sets PHY attributes in Cadence Torrent PHY driver. This will > enable drivers using this PHY to read these properties. > > These attributes will be used in the Cadence MHDP DRM bridge driver [1] > which is in the process of upstreaming. Can you please add these patches on an immutable branch/tag when you are ready to apply them - will try to see if we can use it to get the DisplayPort driver merged in v5.10 too. Hi Laurent, any other ideas on managing the dependency? Thanks, Sekhar