devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Parrot <bparrot@ti.com>
To: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-omap@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Benoit Parrot <bparrot@ti.com>
Subject: [Patch 0/9] ARM: dts: dra7: add cal nodes
Date: Fri, 18 Oct 2019 10:48:40 -0500	[thread overview]
Message-ID: <20191018154849.3127-1-bparrot@ti.com> (raw)

This patch series adds the needed clkctrl and ty-sysc nodes for CAL module.
It also adds support for the module in related dtsi and dts for DRA72,
DRA76 and AM654 SoC.

Benoit Parrot (9):
  ARM: dts: dra7: add cam clkctrl node
  ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only
  ARM: dts: dra7-l4: Add ti-sysc node for CAM
  ARM: dts: DRA72: Add CAL dtsi node
  arm: dts: dra72-evm-common: Add entries for the CSI2 cameras
  arm: dtsi: dra76x: Add CAL dtsi node
  arm: dts: dra76-evm: Add CAL and OV5640 nodes
  arm64: dts: k3-am65-main Add CAL node
  arm64: dts: k3-am654-base-board: Add CSI2 OV5640 camera

 arch/arm/boot/dts/dra7-l4.dtsi                | 43 ++++++++++++++++---
 arch/arm/boot/dts/dra72-evm-common.dtsi       | 35 +++++++++++++++
 arch/arm/boot/dts/dra72x.dtsi                 | 43 +++++++++++++++++++
 arch/arm/boot/dts/dra76-evm.dts               | 39 +++++++++++++++++
 arch/arm/boot/dts/dra76x.dtsi                 | 43 +++++++++++++++++++
 arch/arm/boot/dts/dra7xx-clocks.dtsi          | 14 ++++++
 arch/arm/mach-omap2/clockdomains7xx_data.c    |  2 +-
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi      | 23 ++++++++++
 .../arm64/boot/dts/ti/k3-am654-base-board.dts | 36 ++++++++++++++++
 drivers/clk/ti/clk-7xx.c                      | 19 ++++++++
 include/dt-bindings/clock/dra7.h              | 10 +++++
 11 files changed, 300 insertions(+), 7 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-10-18 15:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 15:48 Benoit Parrot [this message]
2019-10-18 15:48 ` [Patch 1/9] ARM: dts: dra7: add cam clkctrl node Benoit Parrot
2019-10-22 15:40   ` Tony Lindgren
2019-10-22 16:13     ` Benoit Parrot
2019-10-22 16:28       ` Tony Lindgren
2019-10-18 15:48 ` [Patch 2/9] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Benoit Parrot
2019-10-18 15:48 ` [Patch 3/9] ARM: dts: dra7-l4: Add ti-sysc node for CAM Benoit Parrot
2019-10-18 15:48 ` [Patch 4/9] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-10-18 15:48 ` [Patch 5/9] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras Benoit Parrot
2019-10-22 15:44   ` Tony Lindgren
2019-10-22 16:16     ` Benoit Parrot
2019-10-22 16:27       ` Tony Lindgren
2019-10-18 15:48 ` [Patch 6/9] arm: dtsi: dra76x: Add CAL dtsi node Benoit Parrot
2019-10-18 15:48 ` [Patch 7/9] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-10-18 15:48 ` [Patch 8/9] arm64: dts: k3-am65-main Add CAL node Benoit Parrot
2019-10-18 15:48 ` [Patch 9/9] arm64: dts: k3-am654-base-board: Add CSI2 OV5640 camera 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=20191018154849.3127-1-bparrot@ti.com \
    --to=bparrot@ti.com \
    --cc=devicetree@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).