public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: sourav <sourav.poddar@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: zbr@ioremap.net, tony@atomide.com,
	michael.opdenacker@free-electrons.com, wsa@the-dreams.de,
	bcousson@baylibre.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, balbi@ti.com
Subject: Re: [PATCH 5/5] arm: hwmod: am437x: Add hwmod data for hdq1w.
Date: Tue, 29 Apr 2014 14:19:49 +0530	[thread overview]
Message-ID: <535F67AD.2000302@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404282206360.14616@utopia.booyaka.com>

Hi Paul,

On Tuesday 29 April 2014 03:37 AM, Paul Walmsley wrote:
> On Wed, 16 Apr 2014, Sourav Poddar wrote:
>
>> These adds hwmod data for hdq/1w driver.
>>
>> Signed-off-by: Sourav Poddar<sourav.poddar@ti.com>
> Is a TRM available yet for AM43x so this patch can be properly reviewed?

NO, the TRMS are not yet public.

Thanks,
Sourav
>
> - Paul



      reply	other threads:[~2014-04-29  8:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 12:32 [PATCH 0/5] AM437x: HDQ/1wire protocol Sourav Poddar
2014-04-16 12:32 ` [PATCH 1/5] drivers: w1: omap_hdq: cleanup and bug fixes Sourav Poddar
2014-04-28 19:19   ` Paul Walmsley
2014-04-29  9:15     ` sourav
2014-04-16 12:32 ` [PATCH 2/5] w1: omap_hdq: Add compatible property for omap hdq driver Sourav Poddar
2014-04-16 12:32 ` [PATCH 3/5] arm: omap2: skip device build from platform code for dt Sourav Poddar
2014-04-28 18:28   ` Paul Walmsley
2014-04-28 18:39     ` Felipe Balbi
2014-04-29  8:51       ` sourav
2014-04-16 12:32 ` [PATCH 4/5] arm: dts: am4372: Add hdq device tree data Sourav Poddar
2014-04-16 12:32 ` [PATCH 5/5] arm: hwmod: am437x: Add hwmod data for hdq1w Sourav Poddar
2014-04-28 22:07   ` Paul Walmsley
2014-04-29  8:49     ` sourav [this message]

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=535F67AD.2000302@ti.com \
    --to=sourav.poddar@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.com \
    --cc=wsa@the-dreams.de \
    --cc=zbr@ioremap.net \
    /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