From: Kieran Bingham <kieran@ksquared.org.uk>
To: laurent.pinchart@ideasonboard.com, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kieran@ksquared.org.uk
Subject: [PATCH v2 0/3] dt-bindings: RCar FCP and FDP1 bindings
Date: Thu, 30 Jun 2016 17:50:27 +0100 [thread overview]
Message-ID: <1467305430-25660-1-git-send-email-kieran@bingham.xyz> (raw)
This updated series, has collected the Acked and Reviewed tags for the
FCPF binding addition, and adds documention of the optional power-domain
property for the FCP.
Finally the FDP1 bindings have been updated following review from Laurent.
Specifically, this removes the version specific compatibles as we have a
HW version register available to us in the hardware so we can detect at
run-time what device version we are running on.
Kieran Bingham (3):
dt-bindings: Update Renesas R-Car FCP DT binding
dt-bindings: Document Renesas R-Car FCP power-domains usage
dt-bindings: Add Renesas R-Car FDP1 bindings
.../devicetree/bindings/media/renesas,fcp.txt | 9 +++++-
.../devicetree/bindings/media/renesas,fdp1.txt | 33 ++++++++++++++++++++++
2 files changed, 41 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/media/renesas,fdp1.txt
--
2.7.4
next reply other threads:[~2016-06-30 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 16:50 Kieran Bingham [this message]
2016-06-30 16:50 ` [PATCH v2 1/3] dt-bindings: Update Renesas R-Car FCP DT binding Kieran Bingham
2016-06-30 16:50 ` [PATCH v2 2/3] dt-bindings: Document Renesas R-Car FCP power-domains usage Kieran Bingham
2016-07-01 2:49 ` Rob Herring
2016-07-17 16:31 ` Laurent Pinchart
2016-06-30 16:50 ` [PATCH v2 3/3] dt-bindings: Add Renesas R-Car FDP1 bindings Kieran Bingham
2016-07-01 2:51 ` Rob Herring
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=1467305430-25660-1-git-send-email-kieran@bingham.xyz \
--to=kieran@ksquared.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).