From: Tony Lindgren <tony@atomide.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
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 v3 0/3] ARM: dts: am43x-vpfe/ov2659.patch
Date: Tue, 14 Jan 2020 08:04:22 -0800 [thread overview]
Message-ID: <20200114160422.GQ5885@atomide.com> (raw)
In-Reply-To: <20200113165413.i6nbi2i7xyue4fti@ti.com>
* Benoit Parrot <bparrot@ti.com> [200113 16:51]:
> Tony Lindgren <tony@atomide.com> wrote on Fri [2019-Dec-13 07:29:38 -0800]:
> > * Tero Kristo <t-kristo@ti.com> [191213 07:43]:
> > > On 12/12/2019 19:41, Tony Lindgren wrote:
> > > > * Benoit Parrot <bparrot@ti.com> [191211 06:04]:
> > > > > 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.
> > > >
> > > > Tero, it seems I can already pick this series?
> > >
> > > I believe it is ready if you approve the clkout1 clock patch.
> >
> > OK yeah looks fine.
> >
> > > > Or ou want to queue the changes to am43xx-clocks.dtsi along with all
> > > > your other clock patches?
> > >
> > > Well, I have actually never queued any omap2+ dts patches myself, and I
> > > don't think there would be too many of those coming for next merge either.
> >
> > OK will queue this series then. For the other ones from Benoit
> > looks like we need an immutable clock branch before I can apply
> > anything.
>
> Tony, Tero,
>
> Are these merged anyware now?
> I still don't see any of these on linux-next?
Tero any news on getting some immutable clock changes branch done?
Looks like there are quite a few pending clock patches right now,
probably best to set them all into a branch that I can also merge
in.
> And by "these" I mean this one and both
> ARM: dts: dra7: add vpe nodes
> ARM: dts: dra7: add cal nodes
Yeah looks good to me other than the clock dependency.
Regards,
Tony
next prev parent reply other threads:[~2020-01-14 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:07 [Patch v3 0/3] ARM: dts: am43x-vpfe/ov2659.patch Benoit Parrot
2019-12-11 14:07 ` [Patch v3 1/3] ARM: dts: am43xx: add support for clkout1 clock Benoit Parrot
2019-12-11 14:07 ` [Patch v3 2/3] ARM: dts: am437x-sk-evm: Add VPFE and OV2659 entries Benoit Parrot
2019-12-11 14:07 ` [Patch v3 3/3] ARM: dts: am43x-epos-evm: " Benoit Parrot
2019-12-12 17:41 ` [Patch v3 0/3] ARM: dts: am43x-vpfe/ov2659.patch Tony Lindgren
2019-12-13 7:42 ` Tero Kristo
2019-12-13 15:29 ` Tony Lindgren
2020-01-13 16:54 ` Benoit Parrot
2020-01-14 16:04 ` Tony Lindgren [this message]
2020-01-17 14:15 ` Tero Kristo
2020-01-23 17:20 ` Tony Lindgren
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=20200114160422.GQ5885@atomide.com \
--to=tony@atomide.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=t-kristo@ti.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).