From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>, Benoit Parrot <bparrot@ti.com>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Patch v4 00/10] ARM: dts: dra7: add cal nodes
Date: Fri, 24 Jan 2020 09:25:22 +0200 [thread overview]
Message-ID: <fde9ef6c-e214-7436-10c5-7996f19b5cfe@ti.com> (raw)
In-Reply-To: <668be3a7-d9be-6a2e-71ba-5631bf99dfae@ti.com>
On 24/01/2020 09:21, Tero Kristo wrote:
> On 23/01/2020 19:26, Tony Lindgren wrote:
>> * Tony Lindgren <tony@atomide.com> [200123 17:18]:
>>> * Benoit Parrot <bparrot@ti.com> [191211 06:03]:
>>>> 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.
>>>
>>> Applying these into omap-for-v5.6/ti-sysc-dt-cam on top of Tero's
>>> for-5.6-ti-clk branch. It might be too later for v5.6, but we'll
>>> see.
>>
>> Actually I'll leave out the k3-am65 dts changes as I don't see
>> acks for those. Tero can pick up those later.
>>
>> Regards,
>>
>> Tony
>>
>
> Right, I think I also missed the cal clkctrl patch in this series. This
> series is imho applying against too many different trees (three if I am
> not mistaken) and should be split up to avoid confusion / not to get
> lost in mailboxes.
Not cal clkctrl but the cal k3 patches. I just assumed all dts patches
in this series were against omaps.
Anyways, I am planning to send k3 dts pull v2 today due to dma patches
from Peter, so I think I can sneak these also in with that...
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2020-01-24 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:05 [Patch v4 00/10] ARM: dts: dra7: add cal nodes Benoit Parrot
2019-12-11 14:05 ` [Patch v4 01/10] clk: ti: dra7: add cam clkctrl data Benoit Parrot
2019-12-30 19:58 ` Stephen Boyd
2020-01-21 7:32 ` Tero Kristo
2019-12-11 14:05 ` [Patch v4 02/10] ARM: dts: dra7: add cam clkctrl node Benoit Parrot
2019-12-11 14:05 ` [Patch v4 03/10] ARM: OMAP: DRA7xx: Make CAM clock domain SWSUP only Benoit Parrot
2019-12-11 14:05 ` [Patch v4 04/10] ARM: dts: dra7-l4: Add ti-sysc node for CAM Benoit Parrot
2019-12-11 14:05 ` [Patch v4 05/10] ARM: dts: DRA72: Add CAL dtsi node Benoit Parrot
2019-12-11 14:05 ` [Patch v4 06/10] arm: dts: dra72-evm-common: Add entries for the CSI2 cameras Benoit Parrot
2019-12-11 14:05 ` [Patch v4 07/10] arm: dtsi: dra76x: Add CAL dtsi node Benoit Parrot
2019-12-11 14:05 ` [Patch v4 08/10] arm: dts: dra76-evm: Add CAL and OV5640 nodes Benoit Parrot
2019-12-11 14:05 ` [Patch v4 09/10] arm64: dts: k3-am65-main Add CAL node Benoit Parrot
2020-01-24 11:32 ` Tero Kristo
2019-12-11 14:05 ` [Patch v4 10/10] arm64: dts: k3-am654-base-board: Add CSI2 OV5640 camera Benoit Parrot
2020-01-23 17:17 ` [Patch v4 00/10] ARM: dts: dra7: add cal nodes Tony Lindgren
2020-01-23 17:26 ` Tony Lindgren
2020-01-24 7:21 ` Tero Kristo
2020-01-24 7:25 ` Tero Kristo [this message]
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=fde9ef6c-e214-7436-10c5-7996f19b5cfe@ti.com \
--to=t-kristo@ti.com \
--cc=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=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).