From: Benoit Parrot <bparrot@ti.com>
To: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Benoit Parrot <bparrot@ti.com>
Subject: [Patch v2 0/3] ARM: dts: am43x-vpfe/ov2659.patch
Date: Tue, 12 Nov 2019 08:29:26 -0600 [thread overview]
Message-ID: <20191112142929.23058-1-bparrot@ti.com> (raw)
This patch series adds the missing camera endpoint (ov2659) as well as
the required source clocks nodes for the sensor.
On the am437x-sk-evm the camera sensor is sourced from clkout1 but that
clock nodes/tree was removed as it was unsed at the time, we are
re-adding the needed clock nodes here.
Changes since v1:
- Fix clock name to make it generic
- Add non-standard clock node naming to commit message as per Tony's
comment
- Rename all clock nodes to use '-' instead of '_'
Benoit Parrot (2):
ARM: dts: am437x-sk-evm: Add VPFE and OV2659 entries
ARM: dts: am43x-epos-evm: Add VPFE and OV2659 entries
Tero Kristo (1):
ARM: dts: am43xx: add support for clkout1 clock
arch/arm/boot/dts/am437x-sk-evm.dts | 27 +++++++++++++-
arch/arm/boot/dts/am43x-epos-evm.dts | 23 +++++++++++-
arch/arm/boot/dts/am43xx-clocks.dtsi | 54 ++++++++++++++++++++++++++++
3 files changed, 102 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-12 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 14:29 Benoit Parrot [this message]
2019-11-12 14:29 ` [Patch v2 1/3] ARM: dts: am43xx: add support for clkout1 clock Benoit Parrot
2019-11-12 15:39 ` Tony Lindgren
2019-11-12 14:29 ` [Patch v2 2/3] ARM: dts: am437x-sk-evm: Add VPFE and OV2659 entries Benoit Parrot
2019-11-12 14:29 ` [Patch v2 3/3] ARM: dts: am43x-epos-evm: " 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=20191112142929.23058-1-bparrot@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.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).