linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/9] powerpc/pci: clean up direct access to sysdata
Date: Thu, 30 Apr 2009 23:49:26 +1000	[thread overview]
Message-ID: <1241099366.7356.4.camel@concordia> (raw)
In-Reply-To: <1241096999-11164-1-git-send-email-galak@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

On Thu, 2009-04-30 at 08:09 -0500, Kumar Gala wrote:
> We shouldn't be accessing sysdata directly.  In the future we might have
> sysdata be a device_node on ppc32 to match ppc64.  Direct access would make that
> a bit difficult.
> 
> If someone can look at the iseries code I would appreciate that:
> 
> arch/powerpc/platforms/iseries/pci.c:           iomm_table[current_iomm_table_entry] = dev->sysdata;
> arch/powerpc/platforms/iseries/pci.c:                   iseries_ds_addr(dev->sysdata) | (bar_num << 24);
> arch/powerpc/platforms/iseries/pci.c:   pdev->sysdata = node;

It looks like it's basically doing the same logic as
pci_device_to_OF_node(), and fetch_dev_dn(), but there's probably some
reason why it's not using those.

Given how much new iseries hardware there is, I think we'd probably
rather leave the code as is. It's a device node anyway, so it doesn't
block your plans RE ppc32.

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-04-30 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 13:09 [PATCH 0/9] powerpc/pci: clean up direct access to sysdata Kumar Gala
2009-04-30 13:49 ` Michael Ellerman [this message]
2009-04-30 14:18   ` Kumar Gala
2009-04-30 14:50     ` Michael Ellerman
2009-05-05 11:40       ` Kumar Gala

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=1241099366.7356.4.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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).