From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: First Light <xiaoguang.chen-dS4nfl7sBO4@public.gmane.org>
Cc: "linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Edison Chen <yongsen.chen-dS4nfl7sBO4@public.gmane.org>,
Fang Yingju <yingju.fang-dS4nfl7sBO4@public.gmane.org>,
Flare <jiaquan.su-dS4nfl7sBO4@public.gmane.org>
Subject: Re: 答复: dw-spi driver bus number
Date: Wed, 10 Aug 2016 12:03:29 +0100 [thread overview]
Message-ID: <20160810110328.GH9347@sirena.org.uk> (raw)
In-Reply-To: <1470819008289.64659-dS4nfl7sBO4@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Wed, Aug 10, 2016 at 08:50:08AM +0000, First Light wrote:
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
> But I found the dynamically assigned bus number is always -1.?
> I have two spi buses, both get the -1 bus number.
That shouldn't happen, if it does it's a bug - users should never see a
negative bus number, the core should dynamically assign one if it is
given a negative bus number. Can you check what happens in
spi_register_master()? That's where the dynamic bus number should be
being assigned.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-08-10 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1470712490330.33016@dji.com>
[not found] ` <1470712490330.33016-dS4nfl7sBO4@public.gmane.org>
2016-08-09 10:51 ` dw-spi driver bus number Mark Brown
[not found] ` <1470819008289.64659@dji.com>
[not found] ` <1470819008289.64659-dS4nfl7sBO4@public.gmane.org>
2016-08-10 11:03 ` Mark Brown [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=20160810110328.GH9347@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=jiaquan.su-dS4nfl7sBO4@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xiaoguang.chen-dS4nfl7sBO4@public.gmane.org \
--cc=yingju.fang-dS4nfl7sBO4@public.gmane.org \
--cc=yongsen.chen-dS4nfl7sBO4@public.gmane.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).