From: Nishanth Menon <nm@ti.com>
To: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: TI816X: add clock domain support for TI816x
Date: Mon, 16 Sep 2013 08:14:54 -0500 [thread overview]
Message-ID: <20130916131451.GB14873@kahuna> (raw)
In-Reply-To: <5236A9FA.2040100@skitlab.ru>
On 10:49-20130916, Aida Mynzhasova wrote:
> On 24.08.2013 18:02, Aida Mynzhasova wrote:
> >This patch adds required definitions and structures for clockdomain
> >initialization, so omap3xxx_clockdomains_init() was substituted by
> >new ti81xx_clockdomains_init() while early initialization of
> >TI81XX platform.
> >
> >signed-off-by: Aida Mynzhasova <aida.mynzhasova@skitlab.ru>
> >---
> > arch/arm/mach-omap2/Makefile | 2 +
> > arch/arm/mach-omap2/clockdomain.h | 1 +
> > arch/arm/mach-omap2/clockdomains_ti81xx_data.c | 208 +++++++++++++++++++++++++
> > arch/arm/mach-omap2/cm-regbits-ti81xx.h | 22 +++
> > arch/arm/mach-omap2/cm_ti81xx.h | 61 ++++++++
> > arch/arm/mach-omap2/io.c | 2 +-
> > 6 files changed, 295 insertions(+), 1 deletion(-)
> > create mode 100644 arch/arm/mach-omap2/clockdomains_ti81xx_data.c
> > create mode 100644 arch/arm/mach-omap2/cm-regbits-ti81xx.h
> > create mode 100644 arch/arm/mach-omap2/cm_ti81xx.h
> >
>
[...]
> Can anybody please review my changes?
We are transitioning out of having clock information in mach-omap2 to
using devicetree
http://marc.info/?l=devicetree&m=137778225431749&w=2
Will be good to align the conversion with upcoming V7 of the patch
series as well.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-09-16 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 14:02 [PATCH] ARM: OMAP: TI816X: add clock domain support for TI816x Aida Mynzhasova
2013-09-16 6:49 ` Aida Mynzhasova
2013-09-16 13:14 ` Nishanth Menon [this message]
2013-09-18 9:40 ` Aida Mynzhasova
2013-09-18 11:56 ` Nishanth Menon
2013-09-18 16:42 ` Aida Mynzhasova
2013-10-03 18:03 ` 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=20130916131451.GB14873@kahuna \
--to=nm@ti.com \
--cc=aida.mynzhasova@skitlab.ru \
--cc=linux-omap@vger.kernel.org \
/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