From: Benoit Parrot <bparrot@ti.com>
To: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>,
<linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Benoit Parrot <bparrot@ti.com>
Subject: [Patch v5 0/3] ARM: dts: dra7: add vpe nodes
Date: Wed, 11 Dec 2019 08:08:07 -0600 [thread overview]
Message-ID: <20191211140810.10657-1-bparrot@ti.com> (raw)
This patch series adds the needed clkctrl and ty-sysc nodes for VPE module.
We also document the VPE DT bindings.
Changes since v4:
- Added Tony's ack
Changes since v3:
- Patches [1](dt-bindings) and [5](driver compatible) were merged in
linux-media
- Added special clock naming notice to commit message as per Tony's
comment
Changes since v2:
- Fix binding spdx license
- Added Rob's ack
Changes since v1:
- Added a patch to update the compatible in the driver
- Removed unnededed #cell #size properties
- Updated the compatible in dtsi to match binding
- Split off the clk code into its own patch
- Added device specific prefix
- Converted binding to dt schema
Benoit Parrot (3):
clk: ti: dra7: add vpe clkctrl data
ARM: dts: dra7: add vpe clkctrl node
ARM: dts: dra7: Add ti-sysc node for VPE
arch/arm/boot/dts/dra7-l4.dtsi | 28 +++++++++++++++++++++++++---
arch/arm/boot/dts/dra7xx-clocks.dtsi | 18 ++++++++++++++++--
drivers/clk/ti/clk-7xx.c | 6 ++++++
include/dt-bindings/clock/dra7.h | 10 ++++++++++
4 files changed, 57 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-11 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:08 Benoit Parrot [this message]
2019-12-11 14:08 ` [Patch v5 1/3] clk: ti: dra7: add vpe clkctrl data Benoit Parrot
2019-12-30 19:58 ` Stephen Boyd
2020-01-21 7:32 ` Tero Kristo
2020-01-23 17:22 ` Tony Lindgren
2019-12-11 14:08 ` [Patch v5 2/3] ARM: dts: dra7: add vpe clkctrl node Benoit Parrot
2019-12-11 14:08 ` [Patch v5 3/3] ARM: dts: dra7: Add ti-sysc node for VPE Benoit Parrot
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=20191211140810.10657-1-bparrot@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).