From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] OMAP4: clock: shrink clock data utilizing preprocessor.
Date: Fri, 13 May 2011 16:04:43 +0300 [thread overview]
Message-ID: <20110513130441.GH5323@atomide.com> (raw)
In-Reply-To: <4DCD2260.4090806@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [110513 15:18]:
> >>>Signed-off-by: Vladimir Zapolskiy<vzapolskiy@gmail.com>
> >>
> >Unfortunately I don't have an automated tool, but that would be great
> >to have such a script. For this time I've checked the correctness of the
> >change comparing the preprocessed output.
>
> In fact these files are already generated automatically, as written
> in the header file. So changing the output format should
> straightforward. At least for OMAP4... OMAP2 and OMAP3 were done
> manually some time ago.
Sounds like the important thing to consider here is how these macros
should be set up considering the upcoming generic clock framework
and device tree changes.
So let's wait a few days for comments from Benoit and Paul on the
format for the macros so we don't need to redo them again later.
Of course there might be other things to consider too..
Regards,
Tony
next prev parent reply other threads:[~2011-05-13 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1305247077-15927-1-git-send-email-vzapolskiy@gmail.com>
2011-05-13 11:30 ` [PATCH] [RFC] OMAP4: clock: shrink clock data utilizing preprocessor Tony Lindgren
2011-05-13 12:08 ` Vladimir Zapolskiy
2011-05-13 12:21 ` Cousson, Benoit
2011-05-13 13:04 ` Tony Lindgren [this message]
2011-05-13 13:16 ` Kevin Hilman
2011-05-13 13:45 ` Tony Lindgren
2011-05-13 14:24 ` Cousson, Benoit
2011-05-13 16:48 ` Vladimir Zapolskiy
2011-05-13 14:48 ` Premi, Sanjeev
2011-05-13 14:54 ` Cousson, Benoit
2011-05-13 12:21 ` Kevin Hilman
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=20110513130441.GH5323@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).