linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, iivanov.xz@gmail.com
Subject: Re: [PATCH v1 1/2] amba: Defer device peripheral ID read
Date: Mon, 11 Apr 2016 16:01:31 +0100	[thread overview]
Message-ID: <20160411150130.GL19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1460386716-23262-1-git-send-email-georgi.djakov@linaro.org>

On Mon, Apr 11, 2016 at 05:58:35PM +0300, Georgi Djakov wrote:
> From: "Ivan T. Ivanov" <ivan.ivanov@linaro.org>
> 
> To be able to read peripheral ID during device create time
> bus code have turn on device interface clock, but this
> clock could be unavailable at this time. Fix this by defer
> device ID read until driver match time.
> 
> Signed-off-by: Ivan T. Ivanov <ivan.ivanov@linaro.org>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>

Can't do this.  See comments on previous similar patches trying to do the
very same thing.  (Sorry, I don't have time to provide a fuller reply,
especially given that there's already a fuller reply in the last two
months of mailing list archives.)

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      parent reply	other threads:[~2016-04-11 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 14:58 [PATCH v1 1/2] amba: Defer device peripheral ID read Georgi Djakov
2016-04-11 14:58 ` [PATCH v1 2/2] amba: Propagate match errors to the driver core Georgi Djakov
2016-04-11 15:01 ` Russell King - ARM Linux [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=20160411150130.GL19428@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=georgi.djakov@linaro.org \
    --cc=iivanov.xz@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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).