linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC
Date: Sun, 5 Jan 2014 10:27:56 -0700	[thread overview]
Message-ID: <20140105172756.GA11280@obsidianresearch.com> (raw)
In-Reply-To: <20140105154023.GA2048@lunn.ch>

On Sun, Jan 05, 2014 at 04:40:23PM +0100, Andrew Lunn wrote:
> > > +static int __init mvebu_soc_id_init(void)
> > > +{
> > > +	struct device_node *np;
> > > +	int ret = 0;
> > > +
> > > +	np = of_find_matching_node(NULL, mvebu_pcie_of_match_table);
> > > +	if (np) {
> > > +		void __iomem *pci_base;
> > > +		struct clk *clk;
> > > +		/*
> > > +		 * ID and revision are available from any port, so we
> > > +		 * just pick the first one
> > > +		 */
> > > +		struct device_node *child = of_get_next_child(np, NULL);
> > 
> > I guess all this will fail if for some reason the PCIe node is not
> > present on machines that don't use PCIe.
> 
> Hi Arnd
> 
> That would be rather odd. These nodes are in the top level SoC dtsi
> file. When they are not used, they have status = "disabled" and are in
> the dtb blob with this state.

Hang on, you can't safely read from a disabled PCI node, it could have been
powered down by the bootloader..

Jason

  reply	other threads:[~2014-01-05 17:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  9:59 [PATCH v2 0/2] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-03  9:59 ` [PATCH v2 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC Gregory CLEMENT
2014-01-03 14:47   ` Andrew Lunn
2014-01-03 14:51     ` Gregory CLEMENT
2014-01-03 15:13       ` Gregory CLEMENT
2014-01-03 16:41         ` Andrew Lunn
2014-01-03 19:30           ` Gregory CLEMENT
2014-01-03 18:48   ` Thomas Petazzoni
2014-01-03 19:25     ` Gregory CLEMENT
2014-01-03 18:59   ` Jason Gunthorpe
2014-01-03 19:35     ` Gregory CLEMENT
2014-01-05 14:25   ` Arnd Bergmann
2014-01-05 15:40     ` Andrew Lunn
2014-01-05 17:27       ` Jason Gunthorpe [this message]
2014-01-05 17:37         ` Sebastian Hesselbarth
2014-01-05 23:07           ` Jason Gunthorpe
2014-01-05 23:12             ` Sebastian Hesselbarth
2014-01-05 23:40               ` Jason Gunthorpe
2014-01-06  0:05                 ` Sebastian Hesselbarth
2014-01-06  0:17                   ` Andrew Lunn
2014-01-06  9:55                     ` Gregory CLEMENT
2014-01-06 10:10                       ` Gregory CLEMENT
2014-01-05 19:17       ` Arnd Bergmann
2014-01-05 23:51         ` Andrew Lunn
2014-01-06 15:37           ` Arnd Bergmann
2014-01-06 16:24             ` Andrew Lunn
2014-01-07 14:41               ` Arnd Bergmann
2014-01-06 10:28     ` Gregory CLEMENT
2014-01-03  9:59 ` [PATCH v2 2/2] i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-03 12:20   ` Gregory CLEMENT
2014-01-03 18:49   ` Thomas Petazzoni
2014-01-03 19:31     ` Gregory CLEMENT
2014-01-05 14:33   ` Arnd Bergmann
2014-01-06  9:09     ` Gregory CLEMENT
2014-01-07  9:03       ` Arnd Bergmann
2014-01-07 13:17         ` Gregory CLEMENT
2014-01-07 20:50           ` Arnd Bergmann

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=20140105172756.GA11280@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=linux-arm-kernel@lists.infradead.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).