From: Rob Herring <robh@kernel.org>
To: Eugen Hristev <eugen.hristev@microchip.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
luis.oliveira@synopsys.com
Subject: Re: [PATCH v5 2/4] dt-bindings: phy: Document the Synopsys MIPI DPHY Rx bindings
Date: Fri, 16 Dec 2022 17:37:19 -0600 [thread overview]
Message-ID: <20221216233719.GA80712-robh@kernel.org> (raw)
In-Reply-To: <20221216143717.1002015-3-eugen.hristev@microchip.com>
On Fri, Dec 16, 2022 at 04:37:15PM +0200, Eugen Hristev wrote:
> From: Luis Oliveira <Luis.Oliveira@synopsys.com>
>
> Add device-tree bindings documentation for SNPS DesignWare MIPI D-PHY in
> RX mode.
>
> Signed-off-by: Luis Oliveira <luis.oliveira@synopsys.com>
> ---
> .../bindings/phy/snps,dw-dphy-rx.txt | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/snps,dw-dphy-rx.txt
New bindings must be in schema format.
Rob
next prev parent reply other threads:[~2022-12-16 23:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 14:37 [PATCH v5 0/4] media: dwc: add csi2host driver Eugen Hristev
2022-12-16 14:37 ` [PATCH v5 1/4] dt-bindings: media: Document bindings for DW MIPI CSI-2 Host Eugen Hristev
2022-12-16 23:35 ` Rob Herring
2022-12-20 14:16 ` Krzysztof Kozlowski
2022-12-20 14:36 ` Eugen.Hristev
2022-12-16 14:37 ` [PATCH v5 2/4] dt-bindings: phy: Document the Synopsys MIPI DPHY Rx bindings Eugen Hristev
2022-12-16 23:37 ` Rob Herring [this message]
2022-12-20 14:38 ` Eugen.Hristev
2022-12-16 23:42 ` Rob Herring
2022-12-16 14:37 ` [PATCH v5 3/4] media: platform: dwc: Add MIPI CSI-2 controller driver Eugen Hristev
2022-12-16 19:24 ` kernel test robot
2023-03-14 14:20 ` Sakari Ailus
2023-03-14 15:35 ` Conor Dooley
2022-12-16 14:37 ` [PATCH v5 4/4] media: platform: dwc: Add DW MIPI DPHY Rx driver Eugen Hristev
2022-12-16 18:23 ` kernel test robot
2022-12-16 22:16 ` kernel test robot
2023-03-14 14:00 ` Sakari Ailus
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=20221216233719.GA80712-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=luis.oliveira@synopsys.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).