From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
lo <linux-omap@vger.kernel.org>,
lak <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 3/5] OMAP4: hwmod data: add mailbox data
Date: Mon, 14 Feb 2011 16:00:57 +0100 [thread overview]
Message-ID: <4D5943A9.8010205@ti.com> (raw)
In-Reply-To: <1296674843-12718-4-git-send-email-omar.ramirez@ti.com>
Hi Omar,
I found one minor change wrt to the original that I'd like to understand
better.
On 2/2/2011 8:27 PM, Ramirez Luna, Omar wrote:
> From: Benoit Cousson<b-cousson@ti.com>
>
> Mailbox hwmod data for omap4.
>
> Signed-off-by: Benoit Cousson<b-cousson@ti.com>
> Signed-off-by: Omar Ramirez Luna<omar.ramirez@ti.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 67 ++++++++++++++++++++++++++++
> 1 files changed, 67 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index c2806bd..c495669 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -2001,6 +2001,70 @@ static struct omap_hwmod omap44xx_wd_timer3_hwmod = {
> .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP4430),
> };
>
> +/*
> + * 'mailbox' class
> + * mailbox module allowing communication between the on-chip processors
> + * using a queued mailbox-interrupt mechanism.
> + */
> +
> +static struct omap_hwmod_class_sysconfig omap44xx_mailbox_sysc = {
> + .rev_offs = 0x0000,
> + .sysc_offs = 0x0010,
> + .sysc_flags = (SYSC_HAS_RESET_STATUS | SYSC_HAS_SIDLEMODE |
> + SYSC_HAS_SOFTRESET),
> + .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART),
> + .sysc_fields =&omap_hwmod_sysc_type2,
> +};
> +
> +static struct omap_hwmod_class omap44xx_mailbox_hwmod_class = {
> + .name = "mailbox",
> + .sysc =&omap44xx_mailbox_sysc,
> +};
> +
> +/* mailbox */
> +static struct omap_hwmod omap44xx_mailbox_hwmod;
> +static struct omap_hwmod_irq_info omap44xx_mailbox_irqs[] = {
> + { .name = "mbox", .irq = 26 + OMAP44XX_IRQ_GIC_START, },
The original entry was unnamed since it is an unique entry and thus does
not need to be differentiate on this platform.
{ .irq = 26 + OMAP44XX_IRQ_GIC_START },
Do you really need to have a name here? The strategy being to provide a
name only if more than one entry exist.
It is perfectibility doable, I'm just trying to understand your rational.
Thanks,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/5] OMAP4: hwmod data: add mailbox data
Date: Mon, 14 Feb 2011 16:00:57 +0100 [thread overview]
Message-ID: <4D5943A9.8010205@ti.com> (raw)
In-Reply-To: <1296674843-12718-4-git-send-email-omar.ramirez@ti.com>
Hi Omar,
I found one minor change wrt to the original that I'd like to understand
better.
On 2/2/2011 8:27 PM, Ramirez Luna, Omar wrote:
> From: Benoit Cousson<b-cousson@ti.com>
>
> Mailbox hwmod data for omap4.
>
> Signed-off-by: Benoit Cousson<b-cousson@ti.com>
> Signed-off-by: Omar Ramirez Luna<omar.ramirez@ti.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 67 ++++++++++++++++++++++++++++
> 1 files changed, 67 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index c2806bd..c495669 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -2001,6 +2001,70 @@ static struct omap_hwmod omap44xx_wd_timer3_hwmod = {
> .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP4430),
> };
>
> +/*
> + * 'mailbox' class
> + * mailbox module allowing communication between the on-chip processors
> + * using a queued mailbox-interrupt mechanism.
> + */
> +
> +static struct omap_hwmod_class_sysconfig omap44xx_mailbox_sysc = {
> + .rev_offs = 0x0000,
> + .sysc_offs = 0x0010,
> + .sysc_flags = (SYSC_HAS_RESET_STATUS | SYSC_HAS_SIDLEMODE |
> + SYSC_HAS_SOFTRESET),
> + .idlemodes = (SIDLE_FORCE | SIDLE_NO | SIDLE_SMART),
> + .sysc_fields =&omap_hwmod_sysc_type2,
> +};
> +
> +static struct omap_hwmod_class omap44xx_mailbox_hwmod_class = {
> + .name = "mailbox",
> + .sysc =&omap44xx_mailbox_sysc,
> +};
> +
> +/* mailbox */
> +static struct omap_hwmod omap44xx_mailbox_hwmod;
> +static struct omap_hwmod_irq_info omap44xx_mailbox_irqs[] = {
> + { .name = "mbox", .irq = 26 + OMAP44XX_IRQ_GIC_START, },
The original entry was unnamed since it is an unique entry and thus does
not need to be differentiate on this platform.
{ .irq = 26 + OMAP44XX_IRQ_GIC_START },
Do you really need to have a name here? The strategy being to provide a
name only if more than one entry exist.
It is perfectibility doable, I'm just trying to understand your rational.
Thanks,
Benoit
next prev parent reply other threads:[~2011-02-14 15:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 19:27 [PATCH v5 0/5] omap: mailbox: hwmod support Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 1/5] OMAP2: hwmod data: add mailbox data Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 2/5] OMAP3: " Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 3/5] OMAP4: " Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-14 15:00 ` Cousson, Benoit [this message]
2011-02-14 15:00 ` Cousson, Benoit
2011-02-15 21:55 ` Ramirez Luna, Omar
2011-02-15 21:55 ` Ramirez Luna, Omar
2011-02-15 22:05 ` Cousson, Benoit
2011-02-15 22:05 ` Cousson, Benoit
2011-02-16 0:13 ` Ramirez Luna, Omar
2011-02-16 0:13 ` Ramirez Luna, Omar
2011-02-17 23:39 ` Tony Lindgren
2011-02-17 23:39 ` Tony Lindgren
2011-02-18 0:24 ` Ramirez Luna, Omar
2011-02-18 0:24 ` Ramirez Luna, Omar
2011-02-02 19:27 ` [PATCH v5 4/5] OMAP: mailbox: build device using omap_device/omap_hwmod Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 5/5] OMAP: mailbox: use runtime pm for clk and sysc handling Omar Ramirez Luna
2011-02-02 19:27 ` Omar Ramirez Luna
2011-02-08 23:44 ` [PATCH v5 0/5] omap: mailbox: hwmod support Kevin Hilman
2011-02-08 23:44 ` Kevin Hilman
2011-02-09 18:32 ` Tony Lindgren
2011-02-09 18:32 ` Tony Lindgren
2011-02-10 6:01 ` Hiroshi DOYU
2011-02-10 6:01 ` Hiroshi DOYU
2011-02-11 16:37 ` Kevin Hilman
2011-02-11 16:37 ` Kevin Hilman
2011-02-10 5:34 ` Poddar, Sourav
2011-02-10 5:34 ` Poddar, Sourav
2011-02-10 21:12 ` Kevin Hilman
2011-02-10 21:12 ` Kevin Hilman
2011-02-11 23:01 ` Kevin Hilman
2011-02-11 23:01 ` Kevin Hilman
2011-02-15 20:56 ` Ramirez Luna, Omar
2011-02-15 20:56 ` Ramirez Luna, Omar
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=4D5943A9.8010205@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=omar.ramirez@ti.com \
--cc=tony@atomide.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.