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: Tue, 9 Aug 2016 11:51:32 +0100 [thread overview]
Message-ID: <20160809105132.GI10383@sirena.org.uk> (raw)
In-Reply-To: <1470712490330.33016-dS4nfl7sBO4@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Tue, Aug 09, 2016 at 03:14:51AM +0000, First Light wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> but pdev->id is not initialized, it is -1 by default. also there is no dts information for this driver to init bus number.
> I know pdev->id is used frequently when dts is not used long time ago. is this out of date?
> should we add dts to pass bus_num to this driver?
No, nothing should be relying on the bus number anyway and it's
certainly not something that should be part of a description of the
hardware - the expectation is that if things are using DT they will be
using a dynamically assigned bus number.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next parent reply other threads:[~2016-08-09 10:51 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 ` Mark Brown [this message]
[not found] ` <1470819008289.64659@dji.com>
[not found] ` <1470819008289.64659-dS4nfl7sBO4@public.gmane.org>
2016-08-10 11:03 ` 答复: dw-spi driver bus number Mark Brown
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=20160809105132.GI10383@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).