linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Balbi, Felipe" <balbi@ti.com>,
	"R, Sricharan" <r.sricharan@ti.com>
Subject: Re: [PATCH 5/6] omap4: Initialise the l3 device with the hwmod data.
Date: Mon, 21 Feb 2011 19:10:50 +0100	[thread overview]
Message-ID: <4D62AAAA.40104@ti.com> (raw)
In-Reply-To: <1298295990-1070-6-git-send-email-santosh.shilimkar@ti.com>

On 2/21/2011 2:46 PM, Shilimkar, Santosh wrote:
> From: sricharan<r.sricharan@ti.com>
>
> The l3 interconnect device is build with all the data required
> to handle the error logging. The data is extracted from the
> hwmod data base.
>
> Signed-off-by: sricharan<r.sricharan@ti.com>
> Signed-off-by: sricharan<r.sricharan@ti.com>
> Tested-by: sricharan<r.sricharan@ti.com>

Mmm, I'm not sure the tested-by is meaningfull in your case, since you 
wrote the code and so everybody will assume you tested it.
One s-o-b should be probably enough.

> Cc: Benoit Cousson<b-cousson@ti.com>
> ---
>   arch/arm/mach-omap2/devices.c |   23 +++++++++++++++++++++++
>   1 files changed, 23 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 2d46f55..25fa2ad 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -57,6 +57,29 @@ static int __init omap3_l3_init(void)
>   }
>   postcore_initcall(omap3_l3_init);
>
> +static int __init omap4_l3_init(void)
> +{
> +	int l;
> +	struct omap_hwmod *oh;
> +	struct omap_device *od;
> +	char oh_name[12];
> +
> +	l = snprintf(oh_name, 12, "l3_main_1");
> +
> +	oh = omap_hwmod_lookup(oh_name);
> +
> +	if (!oh)
> +		pr_err("could not look up %s\n", oh_name);
> +
> +	od = omap_device_build("omap4-l3-interconnect", 0, oh, NULL,

In order to stick to the OMAP device naming convention and to have 
something not dependent of the chip version, I think we'd better name 
the device like that: "omap_l3_noc". Since it is a Arteris "Network On 
Chip" on OMAP4. We will not have to change it for OMAP5 then.
On OMAP3 the name can then be "omap_l3_smx" for the Sonics MX interconnect.

Please note that the L4 is in both case a Sonics 3220. But I don't think 
the L4 is managed by this series.
Maybe the driver file name should be renamed accordingly.

Regards,
Benoit

> +						     0, NULL, 0, 0);
> +
> +	WARN(IS_ERR(od), "could not build omap_device for %s\n", oh_name);
> +
> +	return PTR_ERR(od);
> +}
> +postcore_initcall(omap4_l3_init);
> +
>   #if defined(CONFIG_VIDEO_OMAP2) || defined(CONFIG_VIDEO_OMAP2_MODULE)
>
>   static struct resource cam_resources[] = {


  reply	other threads:[~2011-02-21 18:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 13:46 [PATCH 0/6] omap3/4: Add l3-interconnect error logging support Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 1/6] omap3: hwmod_data: Add l3 error log data to hwmod database Santosh Shilimkar
2011-02-23  8:03   ` Sricharan R
2011-02-23  8:14   ` Sricharan R
2011-02-21 13:46 ` [PATCH 2/6] omap3: Initialise the l3 device with the hwmod data Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 3/6] omap3: l3: Introduce l3-interconnect error handling driver Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 4/6] omap4: hwmod_data: Add l3 errorlog data to hwmod database Santosh Shilimkar
2011-02-21 14:39   ` Cousson, Benoit
2011-02-23  5:38     ` Sricharan R
2011-02-23  8:04     ` Sricharan R
2011-03-04 21:34       ` Cousson, Benoit
2011-03-05  7:51         ` Santosh Shilimkar
2011-02-23  8:14     ` Sricharan R
2011-02-21 13:46 ` [PATCH 5/6] omap4: Initialise the l3 device with the hwmod data Santosh Shilimkar
2011-02-21 18:10   ` Cousson, Benoit [this message]
2011-02-21 19:03     ` Santosh Shilimkar
2011-03-03 18:31       ` Tony Lindgren
2011-03-04  6:20         ` Santosh Shilimkar
2011-03-04 18:08           ` Tony Lindgren
2011-03-05  7:46             ` Santosh Shilimkar
2011-03-07 10:22       ` Cousson, Benoit
2011-03-07 11:19         ` Santosh Shilimkar
2011-03-07 11:25           ` Santosh Shilimkar
2011-02-21 13:46 ` [PATCH 6/6] omap4: l3: Introduce l3-interconnect error handling driver Santosh Shilimkar

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=4D62AAAA.40104@ti.com \
    --to=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r.sricharan@ti.com \
    --cc=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).