LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>,
	LAK <linux-arm-kernel@lists.infradead.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Benoit Parrot <bparrot@ti.com>,
	Darren Etheridge <detheridge@ti.com>, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH v2] ARM: AM43xx: hwmod: add VPFE hwmod entries
Date: Mon, 26 Jan 2015 08:13:01 +0000	[thread overview]
Message-ID: <CA+V-a8urS2C20FDcfsGa+Gg+7wmbbQQw3U7BfXf6GBKoBGMc9w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501260205090.5450@utopia.booyaka.com>

Hi Paul,

Thanks for the review.

On Mon, Jan 26, 2015 at 2:15 AM, Paul Walmsley <paul@pwsan.com> wrote:
> Hi
>
> On Sun, 25 Jan 2015, Lad, Prabhakar wrote:
>
>> From: Benoit Parrot <bparrot@ti.com>
>>
>> this patch adds VPFE HWMOD data for AM43xx.
>>
>> Signed-off-by: Benoit Parrot <bparrot@ti.com>
>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>> Signed-off-by: Felipe Balbi <balbi@ti.com>
>> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@gmail.com>
>> ---
>>  Hi Paul,
>>
>>  You were right, the hardware team has confirmed that, the VPFE master port is
>>  connected to L3 and the VPFE slave port is connected to L4. The L3 port cannot
>>  serve as a register target because it is initiator only.
>
> OK makes sense to me.,
>
>>
>>  I have created links referring to dss l3/l4 hwmod and tested it, lemme know
>>  if I have missed something.
>
> A few minor comments below
>
>>
[Snip]
>>  /* Interfaces */
>>  static struct omap_hwmod_ocp_if am43xx_l3_main__l4_hs = {
>>       .master         = &am33xx_l3_main_hwmod,
>> @@ -788,6 +826,36 @@ static struct omap_hwmod_ocp_if am43xx_l4_ls__dss_rfbi = {
>>       .user           = OCP_USER_MPU | OCP_USER_SDMA,
>>  };
>>
>> +static struct omap_hwmod_ocp_if am43xx_l3__vpfe0 = {
>> +     .master         = &am43xx_vpfe0_hwmod,
>> +     .slave          = &am33xx_l3_main_hwmod,
>> +     .clk            = "l3_gclk",
>> +     .flags          = OCPIF_SWSUP_IDLE,
>
> OCPIF_SWSUP_IDLE probably isn't needed here.  Could you please try without
> it?
>
>> +     .user           = OCP_USER_MPU | OCP_USER_SDMA,
>> +};
>> +
>> +static struct omap_hwmod_ocp_if am43xx_l3__vpfe1 = {
>> +     .master         = &am43xx_vpfe1_hwmod,
>> +     .slave          = &am33xx_l3_main_hwmod,
>> +     .clk            = "l3_gclk",
>> +     .flags          = OCPIF_SWSUP_IDLE,
>
> Same point as the above.
>
Dropped and tested works! posting a v3.

Cheers,
--Prabhakar Lad

  reply	other threads:[~2015-01-26  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 20:31 Lad, Prabhakar
2015-01-26  2:15 ` Paul Walmsley
2015-01-26  8:13   ` Lad, Prabhakar [this message]
2015-01-26 15:50     ` Benoit Parrot
2015-01-26 15:56       ` Lad, Prabhakar
2015-01-26 18:47         ` Paul Walmsley
2015-01-28 19:30           ` Benoit Parrot

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=CA+V-a8urS2C20FDcfsGa+Gg+7wmbbQQw3U7BfXf6GBKoBGMc9w@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=balbi@ti.com \
    --cc=bparrot@ti.com \
    --cc=detheridge@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    --subject='Re: [PATCH v2] ARM: AM43xx: hwmod: add VPFE hwmod entries' \
    /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

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).