From: Igor Grinberg <grinberg@compulab.co.il>
To: Tarun Kanti DebBarma <tarun.kanti@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 0/13] OMAP: dmtimer: hwmod
Date: Sun, 15 Aug 2010 13:48:30 +0300 [thread overview]
Message-ID: <4C67C5FE.8070607@compulab.co.il> (raw)
In-Reply-To: <1281800359-15285-1-git-send-email-tarun.kanti@ti.com>
On 08/14/10 18:39, Tarun Kanti DebBarma wrote:
> This patch series contains:
> (*) most of the comments provided in v1 implemented and
> (*) OMAP4 timers support
>
> The comment details are availabe in respective patch series.
>
> The comment regarding usage of "dmtimer" name will be resolved
> after final round of consultation with members.
>
> Baseline: "origin/pm-wip/hwmods-omap4"
> Test info: Tested on OMAP4430SDP, OMAP3630SDP
>
> Tarun Kanti DebBarma (13):
> dmtimer: hwmod: OMAP4: add device names to flck nodes
> dmtimer: hwmod: add omap3xxx database
> dmtimer: hwmod: OMAP: rev field to identify timer version
> dmtimer: hwmod: OMAP: api to read omap_hwmod _clk
> dmtimer: hwmod: OMAP: conversion to platform driver
> dmtimer: OMAP: multi-platform register map definitions
> dmtimer: hwmod: OMAP2PLUS: device registration
> dmtimer: OMAP: multi-platform register access support
> dmtimer: hwmod: OMAP3: add device names to flck nodes
> dmtimer: hwmod: add omap2430 database
> dmtimer: hwmod: add omap2420 database
> dmtimer: hwmod: OMAP2: add device names to flck nodes
> dmtimer: hwmod: OMAP1: device registration
>
> arch/arm/mach-omap1/Makefile | 2 +-
> arch/arm/mach-omap1/dmtimer.c | 146 +++++
> arch/arm/mach-omap1/timer32k.c | 3 -
> arch/arm/mach-omap2/Makefile | 2 +-
> arch/arm/mach-omap2/clock2420_data.c | 12 +
> arch/arm/mach-omap2/clock2430_data.c | 12 +
> arch/arm/mach-omap2/clock3xxx_data.c | 24 +-
> arch/arm/mach-omap2/clock44xx_data.c | 22 +-
> arch/arm/mach-omap2/dmtimer.c | 403 +++++++++++++
> arch/arm/mach-omap2/dmtimer.h | 19 +
> arch/arm/mach-omap2/io.c | 2 +
> arch/arm/mach-omap2/omap_hwmod.c | 21 +
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 597 ++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 595 ++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 674 ++++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 3 +
> arch/arm/mach-omap2/timer-gp.c | 1 -
> arch/arm/plat-omap/dmtimer.c | 781 ++++++++++++--------------
> arch/arm/plat-omap/include/plat/dmtimer.h | 15 +-
> arch/arm/plat-omap/include/plat/omap_hwmod.h | 1 +
> 20 files changed, 2894 insertions(+), 441 deletions(-)
> mode change 100644 => 100755 arch/arm/mach-omap1/Makefile
> create mode 100755 arch/arm/mach-omap1/dmtimer.c
> mode change 100644 => 100755 arch/arm/mach-omap1/timer32k.c
> mode change 100644 => 100755 arch/arm/mach-omap2/clock2420_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/clock2430_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/clock3xxx_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/clock44xx_data.c
> create mode 100755 arch/arm/mach-omap2/dmtimer.c
> create mode 100755 arch/arm/mach-omap2/dmtimer.h
> mode change 100644 => 100755 arch/arm/mach-omap2/io.c
> mode change 100644 => 100755 arch/arm/mach-omap2/omap_hwmod.c
> mode change 100644 => 100755 arch/arm/mach-omap2/omap_hwmod_2420_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/omap_hwmod_2430_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> mode change 100644 => 100755 arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> mode change 100644 => 100755 arch/arm/plat-omap/dmtimer.c
> mode change 100644 => 100755 arch/arm/plat-omap/include/plat/dmtimer.h
> mode change 100644 => 100755 arch/arm/plat-omap/include/plat/omap_hwmod.h
>
What the point of all this mode changes? What's wrong with 644?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Regards,
Igor.
next prev parent reply other threads:[~2010-08-15 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 15:39 [PATCHv2 0/13] OMAP: dmtimer: hwmod Tarun Kanti DebBarma
2010-08-15 10:48 ` Igor Grinberg [this message]
2010-08-16 4:24 ` DebBarma, Tarun Kanti
2010-08-24 0:22 ` Kevin Hilman
2010-09-01 9:23 ` DebBarma, Tarun Kanti
-- strict thread matches above, loose matches on Subject: below --
2010-08-14 15:46 Tarun Kanti DebBarma
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=4C67C5FE.8070607@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=linux-omap@vger.kernel.org \
--cc=tarun.kanti@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 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.