From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Guruswamy Senthilvadivu <svadivu@ti.com>
Cc: khilman@deeprootsystems.com, paul@pwsan.com, hvaibhav@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 03/17] OMAP3: hwmod data: add DSS DISPC RFBI DSI VENC
Date: Mon, 20 Dec 2010 15:08:07 +0200 [thread overview]
Message-ID: <1292850487.2421.46.camel@tubuntu> (raw)
In-Reply-To: <1291031503-21036-4-git-send-email-svadivu@ti.com>
Hi,
On Mon, 2010-11-29 at 17:21 +0530, ext Guruswamy Senthilvadivu wrote:
> From: Senthilvadivu Guruswamy <svadivu@ti.com>
>
> Database generated for Display Sub System applicable for
> OMAP3430-ES2 onwards and OMAP36xx.
> dss is also considered as an IP as dispc,rfbi, and named as dss_dss.
> For all the IP modules in DSS, same clock is needed for enabling.
> hwmod sees as independent IPs, so same clock has to be
> repeated as .mainclk in each IP.
> OMAP3430ES1 do not have IDLEST bit to poll on for dss IP. So this hwmod
> is not applicable for 3430ES1.
I'm not so familiar with hwmods, so I cannot comment much on the first
three patches in this series. I'll continue going through the latter
patches.
One question though: what does the mainclk do? If it means "a clock
which enables access to the registers", I'm not sure it's entirely
correct. The DSS clocking can be changed to get the functional clock
from DSI PLL.
Then a general comment about all the patches in the series: The commit
descriptions do not seem to be of very high quality. They are short and
poorly formatted. The descriptions are almost as important as the patch
itself.
Here's a nice text about commit messages:
http://who-t.blogspot.com/2009/12/on-commit-messages.html
And some comments of my own:
- Use capital letters for DSS, DISPC, etc. when not spesifically
referring to some variable or similar.
- Use space after comma.
- Wrap the lines consistently. Now it looks like the lines are wrapped
at random points in some commits.
- Use an empty line between paragraphs
- While I understand that you (me neither) are not native english
speaker, try to spend some time to be sure that there are no errors due
to carelessness.
- Remember that the 00 patch is not saved in git, so it should only be
an intro, and all the relevant information should be found in the actual
commit messages.
Tomi
next prev parent reply other threads:[~2010-12-20 13:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 11:51 [PATCH v2 00/17] OMAP2,3: hwmod DSS Adaptation Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 01/17] OMAP2420: hwmod data: add DSS DISPC RFBI VENC Guruswamy Senthilvadivu
2010-12-06 7:44 ` Guruswamy, Senthilvadivu
2010-12-13 11:31 ` Guruswamy, Senthilvadivu
[not found] ` <FCCFB4CDC6E5564B9182F639FC356087035F28E41F@dbde02.ent.ti.com>
2010-12-14 14:20 ` Tomi Valkeinen
2010-11-29 11:51 ` [PATCH v2 02/17] OMAP2430: " Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 03/17] OMAP3: hwmod data: add DSS DISPC RFBI DSI VENC Guruswamy Senthilvadivu
2010-12-20 13:08 ` Tomi Valkeinen [this message]
2010-12-20 16:43 ` Taneja, Archit
2010-12-21 3:29 ` Guruswamy, Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 04/17] OMAP2420,OMAP2430,OMAP3xx: change dss driver name in clock files Guruswamy Senthilvadivu
2010-12-21 13:44 ` Tomi Valkeinen
2010-12-22 10:29 ` Guruswamy, Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 05/17] OMAP2,3 DSS Driver register moved to mach_omap2 Guruswamy Senthilvadivu
2010-12-21 13:49 ` Tomi Valkeinen
2010-12-22 11:25 ` Guruswamy, Senthilvadivu
2010-12-22 11:36 ` Tomi Valkeinen
2010-11-29 11:51 ` [PATCH v2 06/17] OMAP2,3 board files DSS Driver register moved to devices.c Guruswamy Senthilvadivu
2010-12-21 13:59 ` Tomi Valkeinen
2010-11-29 11:51 ` [PATCH v2 07/17] OMAP2,3: DSS: Build omap_device for each DSS HWIP Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 08/17] OMAP2,3: DSS: Create platform_driver for each DSS HW IP Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 09/17] OMAP2,3: DSS: Move clocks from core driver to dss driver Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 10/17] OMAP2,3: DSS: Move dss_feature_init to dss Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 11/17] OMAP2,3: DSS: DSS Move init,exit to driver Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 12/17] OMAP2,3: DSS: RFBI " Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 13/17] OMAP2,3: DSS: DISPC " Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 14/17] OMAP2,3: DSS: VENC " Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 15/17] OMAP2,3: DSS: DSI Move init, exit " Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 16/17] OMAP2,3: DSS: Use platform device to get baseaddr Guruswamy Senthilvadivu
2010-11-29 11:51 ` [PATCH v2 17/17] OMAP2,3: DSS: Get DSS IRQ from platform device Guruswamy Senthilvadivu
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=1292850487.2421.46.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=hvaibhav@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=svadivu@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