public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	Benoit Cousson <bcousson@baylibre.com>,
	Tony Lindgren <tony@atomide.com>,
	Kumar Gala <galak@codeaurora.org>, <linux-kernel@vger.kernel.org>,
	<linux-omap@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCHv2 0/9] omap hwspinlock dt support
Date: Mon, 30 Sep 2013 10:56:51 -0500	[thread overview]
Message-ID: <52499F43.3010007@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309300309530.17980@utopia.booyaka.com>

On 09/29/2013 10:12 PM, Paul Walmsley wrote:
> Hi
> 
> On Fri, 27 Sep 2013, Suman Anna wrote:
> 
>> Paul,
>> The hwmod data patches needs to be merged only after the respective DT
>> node patches are merged, without which the hwmod entry will not have a
>> base address while enabling and idling (using sysc) the hwmod during
>> hwmod initialization.
> 
> Hmm, ideally there shouldn't be a merge dependency here. Could you please 
> send a patch to the hwmod core that logs a warning and skips the operation 
> in these circumstances?  Or maybe just skips the registration of the 
> device?
> 

Yes, will look into this. This is not specific to hwspinlock, but may be
seen with others as well if the omap_hwmod_addr_space or its equivalent
is not populated.

regards
Suman


      reply	other threads:[~2013-09-30 15:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:30 [PATCHv2 0/9] omap hwspinlock dt support Suman Anna
2013-09-17 19:30 ` [PATCHv2 1/9] hwspinlock/core: add common dt bindings and OF helpers Suman Anna
2013-09-27 16:04   ` Kumar Gala
2013-09-27 16:48     ` Suman Anna
2013-09-27 17:14       ` Kumar Gala
2013-09-27 19:26         ` Suman Anna
2013-10-01  8:36     ` Mark Rutland
2013-10-03  4:04       ` Suman Anna
2013-10-09 21:40         ` Mark Rutland
2013-09-17 19:30 ` [PATCHv2 2/9] hwspinlock/omap: add support for dt nodes Suman Anna
2013-09-27 16:06   ` Kumar Gala
2013-09-27 16:21     ` Suman Anna
2013-09-27 17:14       ` Kumar Gala
2013-10-01  8:40     ` Mark Rutland
2013-10-03  4:12       ` Suman Anna
2013-10-09 21:46         ` Mark Rutland
2013-10-10 20:29           ` Suman Anna
2013-09-17 19:31 ` [PATCHv2 3/9] ARM: dts: OMAP4: Add hwspinlock node Suman Anna
2013-09-17 19:31 ` [PATCHv2 4/9] ARM: OMAP5: hwmod data: Add spinlock data Suman Anna
2013-10-09  7:12   ` Paul Walmsley
2013-10-09 17:49     ` Suman Anna
2013-09-17 19:31 ` [PATCHv2 5/9] ARM: dts: OMAP5: Add hwspinlock node Suman Anna
2013-09-17 19:31 ` [PATCHv2 6/9] hwspinlock/omap: support AM33xx Suman Anna
2013-09-17 19:31 ` [PATCHv2 7/9] hwspinlock/omap: enable module before reading SYSSTATUS register Suman Anna
2013-09-17 19:31 ` [PATCHv2 8/9] ARM: dts: AM33XX: Add hwspinlock node Suman Anna
2013-09-17 19:31 ` [PATCHv2 9/9] ARM: AM33xx: hwmod_data: add the sysc configuration for spinlock Suman Anna
2013-10-09  7:12   ` Paul Walmsley
2013-09-27 15:48 ` [PATCHv2 0/9] omap hwspinlock dt support Suman Anna
2013-09-30  3:12   ` Paul Walmsley
2013-09-30 15:56     ` Suman Anna [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=52499F43.3010007@ti.com \
    --to=s-anna@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox