From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Gerlando Falauto <gerlando.falauto@keymile.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
"Longchamp, Valentin" <Valentin.Longchamp@keymile.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: pci-mvebu driver on km_kirkwood
Date: Mon, 26 Aug 2013 13:16:15 -0600 [thread overview]
Message-ID: <20130826191615.GA20192@obsidianresearch.com> (raw)
In-Reply-To: <521B6AF3.9070909@keymile.com>
On Mon, Aug 26, 2013 at 04:49:23PM +0200, Gerlando Falauto wrote:
> One last question though... what does then the numbering ("@a,b")
> stand for? I assume if the output of a plain (i.e. no params)
> 'lspci' is
It is device,function, but it is only descriptive and not used by
Linux.
> I should only have a "pci@dd,f" node, with the bus numbering being
> imposed by the hierarchy after an actual probing, right?
> So the actual bus number is never listed in the device tree (whereas
> the "@device,function" is). Is that right?
The reg must encode the bus number according to the OF format:
33222222 22221111 11111100 00000000
10987654 32109876 54321098 76543210
phys.hi cell: npt000ss bbbbbbbb dddddfff rrrrrrrr
phys.mid cell: hhhhhhhh hhhhhhhh hhhhhhhh hhhhhhhh
phys.lo cell: llllllll llllllll llllllll llllllll
bbbbbbbb is the 8-bit Bus Number
ddddd is the 5-bit Device Number
fff is the 3-bit Function Number
Others are 0.
Jason
next prev parent reply other threads:[~2013-08-26 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51DD88A4.1030506@keymile.com>
[not found] ` <20130731100359.3e789236@skate>
[not found] ` <51F8CA44.4080802@keymile.com>
[not found] ` <20130731110045.2dc84981@skate>
[not found] ` <20130731205034.GA17615@obsidianresearch.com>
[not found] ` <20130809140140.GA14990@ulmo>
2013-08-26 9:27 ` pci-mvebu driver on km_kirkwood Gerlando Falauto
2013-08-26 12:02 ` Thierry Reding
2013-08-26 14:49 ` Gerlando Falauto
2013-08-26 19:16 ` Jason Gunthorpe [this message]
[not found] ` <20130826191615.GA20192-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2013-11-04 14:49 ` Gerlando Falauto
[not found] ` <5277B417.2030506-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-11-05 8:13 ` Thierry Reding
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=20130826191615.GA20192@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Valentin.Longchamp@keymile.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gerlando.falauto@keymile.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).