From: Vinod Koul <vkoul@kernel.org>
To: Swapnil Jakhade <sjakhade@cadence.com>
Cc: kishon@ti.com, linux-kernel@vger.kernel.org, maxime@cerno.tech,
Laurent.pinchart@ideasonboard.com, mparab@cadence.com,
yamonkar@cadence.com, nsekhar@ti.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 17:38:54 +0530 [thread overview]
Message-ID: <20200916120854.GF2968@vkoul-mobl> (raw)
In-Reply-To: <1599805114-22063-1-git-send-email-sjakhade@cadence.com>
On 11-09-20, 08:18, 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.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2020-09-16 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 6:18 [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate Swapnil Jakhade
2020-09-11 6:18 ` [PATCH v6 1/2] phy: " Swapnil Jakhade
2020-09-15 23:00 ` Laurent Pinchart
2020-09-11 6:18 ` [PATCH v6 2/2] phy: cadence-torrent: Set Torrent PHY attributes Swapnil Jakhade
2020-09-15 23:01 ` Laurent Pinchart
2020-09-16 7:41 ` [PATCH v6 0/2] PHY: Add new PHY attribute max_link_rate Sekhar Nori
2020-09-16 12:09 ` Vinod Koul
2020-09-16 12:18 ` Laurent Pinchart
2020-09-16 12:43 ` Vinod Koul
2020-09-16 17:27 ` Sekhar Nori
2020-09-16 17:34 ` Laurent Pinchart
2020-09-16 12:08 ` Vinod Koul [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=20200916120854.GF2968@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=jsarha@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mparab@cadence.com \
--cc=nsekhar@ti.com \
--cc=praneeth@ti.com \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ti.com \
--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