From: Vinod Koul <vkoul@kernel.org>
To: Pratyush Yadav <p.yadav@ti.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Swapnil Jakhade <sjakhade@cadence.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v10 0/4] Rx mode support for Cadence DPHY
Date: Wed, 2 Mar 2022 19:54:53 +0530 [thread overview]
Message-ID: <Yh9+Ncc2DulmBpXr@matsya> (raw)
In-Reply-To: <20220301111621.2992275-1-p.yadav@ti.com>
On 01-03-22, 16:46, Pratyush Yadav wrote:
> Hi,
>
> This series adds support for Cadence DPHY Rx driver. It has been split
> off from [0] to facilitate easier merging. I have still kept the version
> number to maintain continuity with the previous patches. The earlier
> version used the same binding for Tx and Rx DPHY. With the separate
> driver, I have added a separate binding. But I am still keeping the old
> conversion patch in this series since I have already done the work in
> converting the binding to yaml, might as well get it merged.
>
> Tested on TI's J721E with OV5640 sensor.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2022-03-02 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 11:16 [PATCH v10 0/4] Rx mode support for Cadence DPHY Pratyush Yadav
2022-03-01 11:16 ` [PATCH v10 1/4] phy: cadence: Add Cadence D-PHY Rx driver Pratyush Yadav
2022-03-01 11:16 ` [PATCH v10 2/4] phy: dt-bindings: Convert Cadence DPHY binding to YAML Pratyush Yadav
2022-03-01 11:16 ` [PATCH v10 3/4] phy: dt-bindings: cdns, dphy: add power-domains property Pratyush Yadav
2022-03-01 11:16 ` [PATCH v10 4/4] phy: dt-bindings: Add Cadence D-PHY Rx bindings Pratyush Yadav
2022-03-02 14:24 ` 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=Yh9+Ncc2DulmBpXr@matsya \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.yadav@ti.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sjakhade@cadence.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@ti.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).