mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: 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 v4 0/2] Add new PHY APIs to framework to get/set PHY attributes
Date: Mon, 27 Jul 2020 22:32:41 +0530	[thread overview]
Message-ID: <b6c1984d-e774-3b24-cb10-ee47cb5fd835@ti.com> (raw)
In-Reply-To: <20200727095515.GX12965@vkoul-mobl>

On 7/27/20 3:25 PM, Vinod Koul wrote:
> Hi Sekhar,
> 
> On 26-07-20, 01:24, Sekhar Nori wrote:
>> Hi Vinod,
>>
>> On 7/17/20 12:20 PM, Swapnil Jakhade wrote:
>>> This patch series adds a new pair of PHY APIs that can be used to get/set
>>> all the PHY attributes. It also adds a new PHY attribute max_link_rate.
>>>
>>> It includes following patches:
>>>
>>> 1. v4-0001-phy-Add-new-PHY-attribute-max_link_rate-and-APIs-.patch
>>> This patch adds max_link_rate as a new PHY attribute along with a pair of
>>> APIs that allow using the generic PHY subsystem to get/set PHY attributes
>>> supported by the PHY.
>>>
>>> 2. v4-0002-phy-cadence-torrent-Use-kernel-PHY-API-to-set-PHY.patch
>>> This patch uses PHY API phy_set_attrs() to set corresponding PHY properties
>>> in Cadence Torrent PHY driver. This will enable drivers using this PHY to
>>> read these properties using PHY framework.
>>>
>>> The phy_get_attrs() API will be used in the DRM bridge driver [1] which is
>>> in the process of upstreaming.
>>
>> Is it possible to queue these for v5.9 also? I did notice that phy
>> updates for v5.9-rc1 are posted already. But these APIs are needed for
>> the DisplayPort driver thats getting ready for merge too. Having these
>> queued now will make managing dependencies much easier.
> 
> I would prefer if we defer core change to post rc1. For your display, we
> can provide a signed tag for you/drm folks to fetch.
> 
> Would that be okay?

Okay, that would work too.

Thanks,
Sekhar

      reply	other threads:[~2020-07-27 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  6:50 Swapnil Jakhade
2020-07-17  6:50 ` [PATCH v4 1/2] phy: Add new PHY attribute max_link_rate and APIs " Swapnil Jakhade
2020-07-23  4:51   ` Kishon Vijay Abraham I
2020-08-11  0:20   ` Laurent Pinchart
2020-07-17  6:50 ` [PATCH v4 2/2] phy: cadence-torrent: Use kernel PHY API to set " Swapnil Jakhade
2020-07-23  4:55   ` Kishon Vijay Abraham I
2020-07-25 19:54 ` [PATCH v4 0/2] Add new PHY APIs to framework to get/set " Sekhar Nori
2020-07-27  9:55   ` Vinod Koul
2020-07-27 17:02     ` Sekhar Nori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6c1984d-e774-3b24-cb10-ee47cb5fd835@ti.com \
    --to=nsekhar@ti.com \
    --cc=jsarha@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mparab@cadence.com \
    --cc=praneeth@ti.com \
    --cc=sjakhade@cadence.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=vkoul@kernel.org \
    --cc=yamonkar@cadence.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®