From: tomi.valkeinen@ti•com (Tomi Valkeinen)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] ARM: dts: Fix OMAP3 ISP functional clock configuration
Date: Thu, 8 May 2014 13:57:15 +0300 [thread overview]
Message-ID: <536B630B.8010303@ti.com> (raw)
In-Reply-To: <1398076907-2901-1-git-send-email-laurent.pinchart@ideasonboard.com>
On 21/04/14 13:41, Laurent Pinchart wrote:
> Hello,
>
> This patch set enables rate propagation from the OMAP3 ISP functional clock to
> the DPLL4 M5 clock. It copies Tomi Valkeinen's similar patch set for the OMAP
> DSS functional clock from the "OMAP: OMAP3 DSS related clock patches" patch
> series.
>
> Laurent Pinchart (2):
> ARM: dts: use ti,fixed-factor-clock for dpll4_m5x2_mul_ck
> ARM: dts: set 'ti,set-rate-parent' for dpll4_m5 path
>
> arch/arm/boot/dts/omap36xx-clocks.dtsi | 2 +-
> arch/arm/boot/dts/omap3xxx-clocks.dtsi | 7 ++++---
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
These look fine to me.
Acked-by: Tomi Valkeinen <tomi.valkeinen@ti•com>
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140508/209bba74/attachment.sig>
next prev parent reply other threads:[~2014-05-08 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 10:41 [PATCH 0/2] ARM: dts: Fix OMAP3 ISP functional clock configuration Laurent Pinchart
2014-04-21 10:41 ` [PATCH 1/2] ARM: dts: use ti, fixed-factor-clock for dpll4_m5x2_mul_ck Laurent Pinchart
2014-04-21 10:41 ` [PATCH 2/2] ARM: dts: set 'ti,set-rate-parent' for dpll4_m5 path Laurent Pinchart
2014-05-08 10:57 ` Tomi Valkeinen [this message]
2014-05-12 23:16 ` [PATCH 0/2] ARM: dts: Fix OMAP3 ISP functional clock configuration Laurent Pinchart
2014-05-13 1:06 ` Tony Lindgren
2014-05-15 15:53 ` Laurent Pinchart
2014-05-15 15:54 ` Tero Kristo
2014-05-19 13:11 ` Tero Kristo
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=536B630B.8010303@ti.com \
--to=tomi.valkeinen@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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