All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v7 1/2] drivers: base: add support for registering notifier about deferred probe
Date: Thu, 14 Apr 2016 14:51:39 -0700	[thread overview]
Message-ID: <20160414215139.GA11535@kroah.com> (raw)
In-Reply-To: <20160414213322.GW19428@n2100.arm.linux.org.uk>

On Thu, Apr 14, 2016 at 10:33:22PM +0100, Russell King - ARM Linux wrote:
> The problem that's being addressed here is that there's no way at the
> moment to know when the drivers on a different bus (namely the platform
> bus) have probed and are providing the clock and power domain resources
> necessary to be able to read these identifying values.
> 
> I guess if you don't like a notifier, the other alternative is to
> setup a delayed workqueue and have the workqueue repeatedly attempt
> to register the devices until they all succeed.  That's not
> particularly nice, because we'd be wasting CPU cycles running
> that workqueue for no reason until all the devices get registered.

I like that idea, it handles the issue of this crazy hardware where it
belongs, in that bus subsystem :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/2] drivers: base: add support for registering notifier about deferred probe
Date: Thu, 14 Apr 2016 14:51:39 -0700	[thread overview]
Message-ID: <20160414215139.GA11535@kroah.com> (raw)
In-Reply-To: <20160414213322.GW19428@n2100.arm.linux.org.uk>

On Thu, Apr 14, 2016 at 10:33:22PM +0100, Russell King - ARM Linux wrote:
> The problem that's being addressed here is that there's no way at the
> moment to know when the drivers on a different bus (namely the platform
> bus) have probed and are providing the clock and power domain resources
> necessary to be able to read these identifying values.
> 
> I guess if you don't like a notifier, the other alternative is to
> setup a delayed workqueue and have the workqueue repeatedly attempt
> to register the devices until they all succeed.  That's not
> particularly nice, because we'd be wasting CPU cycles running
> that workqueue for no reason until all the devices get registered.

I like that idea, it handles the issue of this crazy hardware where it
belongs, in that bus subsystem :)

thanks,

greg k-h

  reply	other threads:[~2016-04-14 21:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13  9:35 [PATCH v7 0/2] AMBA: add complete support for power domains Marek Szyprowski
2016-04-13  9:35 ` Marek Szyprowski
2016-04-13  9:35 ` [PATCH v7 1/2] drivers: base: add support for registering notifier about deferred probe Marek Szyprowski
2016-04-13  9:35   ` Marek Szyprowski
2016-04-13 14:12   ` Greg Kroah-Hartman
2016-04-13 14:12     ` Greg Kroah-Hartman
2016-04-14  7:36     ` Marek Szyprowski
2016-04-14  7:36       ` Marek Szyprowski
2016-04-14  8:40       ` Russell King - ARM Linux
2016-04-14  8:40         ` Russell King - ARM Linux
2016-04-14 21:17       ` Greg Kroah-Hartman
2016-04-14 21:17         ` Greg Kroah-Hartman
2016-04-14 21:33         ` Russell King - ARM Linux
2016-04-14 21:33           ` Russell King - ARM Linux
2016-04-14 21:51           ` Greg Kroah-Hartman [this message]
2016-04-14 21:51             ` Greg Kroah-Hartman
2016-04-13  9:36 ` [PATCH v7 2/2] drivers: amba: properly handle devices with power domains Marek Szyprowski
2016-04-13  9:36   ` Marek Szyprowski

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=20160414215139.GA11535@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=ulf.hansson@linaro.org \
    /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.