From: Rob Herring <robh@kernel.org>
To: Yuti Amonkar <yamonkar@cadence.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kishon@ti.com, mark.rutland@arm.com, maxime@cerno.tech,
jsarha@ti.com, tomi.valkeinen@ti.com, praneeth@ti.com,
mparab@cadence.com, sjakhade@cadence.com
Subject: Re: [PATCH v3 13/14] dt-bindings: phy: phy-cadence-torrent: Add subnode bindings.
Date: Mon, 27 Jan 2020 10:45:38 -0600 [thread overview]
Message-ID: <20200127164538.GB7662@bogus> (raw)
In-Reply-To: <1579689918-7181-14-git-send-email-yamonkar@cadence.com>
On Wed, Jan 22, 2020 at 11:45:17AM +0100, Yuti Amonkar wrote:
> From: Swapnil Jakhade <sjakhade@cadence.com>
>
> Add sub-node bindings for each group of PHY lanes based on PHY
> type. Only PHY_TYPE_DP is supported currently. Each sub-node
> includes properties such as master lane number, link reset, phy
> type, number of lanes etc.
>
> Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
Also, if you send patches from another author, your S-o-b should also be
present.
next prev parent reply other threads:[~2020-01-27 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 10:45 [PATCH v3 00/14] PHY: Update Cadence Torrent PHY driver with reconfiguration Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 01/14] dt-bindings: phy: Convert Cadence MHDP PHY bindings to YAML Yuti Amonkar
2020-01-27 16:25 ` Rob Herring
2020-01-22 10:45 ` [PATCH v3 02/14] phy: cadence-dp: Rename to phy-cadence-torrent Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 03/14] phy: cadence-torrent: Adopt Torrent nomenclature Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 04/14] phy: cadence-torrent: Add wrapper for PHY register access Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 05/14] phy: cadence-torrent: Add wrapper for DPTX " Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 06/14] phy: cadence-torrent: Refactor code for reusability Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 07/14] phy: cadence-torrent: Add 19.2 MHz reference clock support Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 08/14] phy: cadence-torrent: Implement PHY configure APIs Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 09/14] phy: cadence-torrent: Use regmap to read and write Torrent PHY registers Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 10/14] phy: cadence-torrent: Use regmap to read and write DPTX " Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 11/14] dt-bindings: phy: phy-cadence-torrent: Add platform dependent compatible string Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 12/14] phy: cadence-torrent: Add platform dependent initialization structure Yuti Amonkar
2020-01-22 10:45 ` [PATCH v3 13/14] dt-bindings: phy: phy-cadence-torrent: Add subnode bindings Yuti Amonkar
2020-01-27 16:42 ` Rob Herring
2020-01-28 10:04 ` Jyri Sarha
2020-01-28 15:40 ` Rob Herring
2020-01-27 16:45 ` Rob Herring [this message]
2020-01-22 10:45 ` [PATCH v3 14/14] phy: cadence-torrent: Add support for " Yuti Amonkar
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=20200127164538.GB7662@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime@cerno.tech \
--cc=mparab@cadence.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;
as well as URLs for NNTP newsgroup(s).