Re: [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate

From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	Swapnil Jakhade <sjakhade@cadence.com>,
	kishon@ti.com, linux-kernel@vger.kernel.org, maxime@cerno.tech,
	mparab@cadence.com, yamonkar@cadence.com, tomi.valkeinen@ti.com,
	jsarha@ti.com, praneeth@ti.com
Subject: Re: [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate
Date: Wed, 16 Sep 2020 20:34:12 +0300	[thread overview]
Message-ID: <20200916173412.GI3853@pendragon.ideasonboard.com> (raw)
In-Reply-To: <d7d2f8b5-86a2-c2f9-62ff-cf60278a5463@ti.com>

On Wed, Sep 16, 2020 at 10:57:46PM +0530, Sekhar Nori wrote:
> On 16/09/20 6:13 PM, Vinod Koul wrote:
> > On 16-09-20, 15:18, Laurent Pinchart wrote:
> >> Hi Sekhar,
> >>
> >> On Wed, Sep 16, 2020 at 01:11:17PM +0530, Sekhar Nori wrote:
> >>> 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?
> >>
> >> I think that will work fine.
> > 
> > Please pull tag phy-attrs-5.10 for phy tree
> 
> Thanks Vinod!
> 
> Swapnil, please be sure to let DRM maintainers know about the PHY tree
> and the tag they can use when the DP patches are ready for merge.

This should be mentioned in the pull request, but as the branch
submitted for DRM/KMS has to be based on 

The simplest (and maybe only) option is to base the branch for the
DRM/KMS subsystem on Vinod's branch. It's however good to mention this
explicitly in the pull request, stating that the base branch is
scheduled for merge in v5.10 through the PHY tree.

> Please keep Vinod in the loop too so he is aware of the tag being pulled.

-- 
Regards,

Laurent Pinchart