From: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: t-kristo-l0cyMroinI0@public.gmane.orgTero Kristo
<t-kristo-l0cyMroinI0@public.gmane.org>
Cc: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH RFC 0/3] first pass converting omap4 clock data to DT
Date: Tue, 04 Jun 2013 23:45:45 -0700 [thread overview]
Message-ID: <20130605064545.10233.72880@quantum> (raw)
In-Reply-To: <1370352534.25965.52.camel@sokoban>
Quoting Tero Kristo (2013-06-04 06:28:54)
> Hi Mike,
>
> On Mon, 2013-06-03 at 23:39 -0700, Mike Turquette wrote:
> > This is a very incomplete conversion of a handful of OMAP4 PRCM clocks
> > from the statically defined clock data in
> > arch/arm/mach-omap2/cclock44xx_data.c to a new dts file in
> > arch/arm/boot/dts/omap4-clocks.dtsi.
>
> I gave a quick try for this set and it seems to be working nicely, so
> for at least me this approach is fine. Feel free to add tested-by me if
> you like (for the basic clock bindings also.) Can't comment much on the
> DT stuff though as my experience is rather limited on it.
>
> > I am not a DT expert so many of the choices here may be quite disgusting
> > to look at, or may be on the right path. In particular I simply include
> > the new omap4-clocks.dtsi from omap4.dtsi, which feels a bit kludgey.
> > Also this series depends on the basic clock bindings RFC I posted
> > earlier today[1].
> >
> > I actually have an omap4-clock.dtsi file with many more clocks converted
> > to the mux-clock, divider-clock, fixed-clock, fixed-factor and
> > (unpublished) gate-clock bindings in my local repo, but it is not
> > currently booting. I wanted to get this early preview out regardless.
>
> Any way I can get access to your local tree? Can you push a branch
> somewhere? I could provide you debugging support on this at least, as I
> spent quite a bit of time earlier moving the clock data under
> drivers/clk... I guess you are probably seeing similar issues I faced.
>
I'll be pushing changes to my github tree:
git://github.com/mturquette/linux.git clk-next-omap-dt
https://github.com/mturquette/linux/tree/clk-next-omap-dt
For now it is just this series based on the prerequisites, based on
clk-next, based on -rc3.
Regards,
Mike
> -Tero
>
> >
> > [1] http://article.gmane.org/gmane.linux.kernel/1501216
> >
> > Mike Turquette (3):
> > clk: omap: introduce clock driver
> > ARM: dts: omap4 clock data
> > ARM: omap4: register DT clocks & remove old data
> >
> > arch/arm/boot/dts/omap4-clocks.dtsi | 128 ++++++++++++++++++++++++++++++++++
> > arch/arm/boot/dts/omap4.dtsi | 2 +
> > arch/arm/mach-omap2/cclock44xx_data.c | 54 ++------------
> > drivers/clk/Makefile | 1 +
> > drivers/clk/omap/Makefile | 1 +
> > drivers/clk/omap/clk.c | 55 +++++++++++++++
> > include/linux/clk/omap.h | 24 +++++++
> > 7 files changed, 217 insertions(+), 48 deletions(-)
> > create mode 100644 arch/arm/boot/dts/omap4-clocks.dtsi
> > create mode 100644 drivers/clk/omap/Makefile
> > create mode 100644 drivers/clk/omap/clk.c
> > create mode 100644 include/linux/clk/omap.h
> >
WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/3] first pass converting omap4 clock data to DT
Date: Tue, 04 Jun 2013 23:45:45 -0700 [thread overview]
Message-ID: <20130605064545.10233.72880@quantum> (raw)
In-Reply-To: <1370352534.25965.52.camel@sokoban>
Quoting Tero Kristo (2013-06-04 06:28:54)
> Hi Mike,
>
> On Mon, 2013-06-03 at 23:39 -0700, Mike Turquette wrote:
> > This is a very incomplete conversion of a handful of OMAP4 PRCM clocks
> > from the statically defined clock data in
> > arch/arm/mach-omap2/cclock44xx_data.c to a new dts file in
> > arch/arm/boot/dts/omap4-clocks.dtsi.
>
> I gave a quick try for this set and it seems to be working nicely, so
> for at least me this approach is fine. Feel free to add tested-by me if
> you like (for the basic clock bindings also.) Can't comment much on the
> DT stuff though as my experience is rather limited on it.
>
> > I am not a DT expert so many of the choices here may be quite disgusting
> > to look at, or may be on the right path. In particular I simply include
> > the new omap4-clocks.dtsi from omap4.dtsi, which feels a bit kludgey.
> > Also this series depends on the basic clock bindings RFC I posted
> > earlier today[1].
> >
> > I actually have an omap4-clock.dtsi file with many more clocks converted
> > to the mux-clock, divider-clock, fixed-clock, fixed-factor and
> > (unpublished) gate-clock bindings in my local repo, but it is not
> > currently booting. I wanted to get this early preview out regardless.
>
> Any way I can get access to your local tree? Can you push a branch
> somewhere? I could provide you debugging support on this at least, as I
> spent quite a bit of time earlier moving the clock data under
> drivers/clk... I guess you are probably seeing similar issues I faced.
>
I'll be pushing changes to my github tree:
git://github.com/mturquette/linux.git clk-next-omap-dt
https://github.com/mturquette/linux/tree/clk-next-omap-dt
For now it is just this series based on the prerequisites, based on
clk-next, based on -rc3.
Regards,
Mike
> -Tero
>
> >
> > [1] http://article.gmane.org/gmane.linux.kernel/1501216
> >
> > Mike Turquette (3):
> > clk: omap: introduce clock driver
> > ARM: dts: omap4 clock data
> > ARM: omap4: register DT clocks & remove old data
> >
> > arch/arm/boot/dts/omap4-clocks.dtsi | 128 ++++++++++++++++++++++++++++++++++
> > arch/arm/boot/dts/omap4.dtsi | 2 +
> > arch/arm/mach-omap2/cclock44xx_data.c | 54 ++------------
> > drivers/clk/Makefile | 1 +
> > drivers/clk/omap/Makefile | 1 +
> > drivers/clk/omap/clk.c | 55 +++++++++++++++
> > include/linux/clk/omap.h | 24 +++++++
> > 7 files changed, 217 insertions(+), 48 deletions(-)
> > create mode 100644 arch/arm/boot/dts/omap4-clocks.dtsi
> > create mode 100644 drivers/clk/omap/Makefile
> > create mode 100644 drivers/clk/omap/clk.c
> > create mode 100644 include/linux/clk/omap.h
> >
next prev parent reply other threads:[~2013-06-05 6:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:39 [PATCH RFC 0/3] first pass converting omap4 clock data to DT Mike Turquette
2013-06-04 6:39 ` Mike Turquette
2013-06-04 6:39 ` [PATCH RFC 1/3] clk: omap: introduce clock driver Mike Turquette
2013-06-04 6:39 ` Mike Turquette
2013-06-04 14:52 ` Tony Lindgren
2013-06-04 14:52 ` Tony Lindgren
2013-06-14 22:12 ` Grant Likely
2013-06-14 22:12 ` Grant Likely
2013-06-04 6:39 ` [PATCH RFC 2/3] ARM: dts: omap4 clock data Mike Turquette
2013-06-04 6:39 ` Mike Turquette
2013-06-04 14:55 ` Tony Lindgren
2013-06-04 14:55 ` Tony Lindgren
[not found] ` <20130604145543.GK3331-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-06-04 18:34 ` Mike Turquette
2013-06-04 18:34 ` Mike Turquette
2013-06-04 19:37 ` Tony Lindgren
2013-06-04 19:37 ` Tony Lindgren
2013-06-04 6:39 ` [PATCH RFC 3/3] ARM: omap4: register DT clocks & remove old data Mike Turquette
2013-06-04 6:39 ` Mike Turquette
2013-06-04 13:28 ` [PATCH RFC 0/3] first pass converting omap4 clock data to DT Tero Kristo
2013-06-04 13:28 ` Tero Kristo
2013-06-05 6:45 ` Mike Turquette [this message]
2013-06-05 6:45 ` Mike Turquette
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=20130605064545.10233.72880@quantum \
--to=mturquette-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nm-l0cyMroinI0@public.gmane.org \
--cc=t-kristo-l0cyMroinI0@public.gmane.orgTero \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.