linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 4/9] [POWERPC] move Efika support files into platforms/52xx
Date: Mon, 27 Nov 2006 15:09:34 -0700	[thread overview]
Message-ID: <528646bc0611271409g27ec05a0m9d7149e55256d363@mail.gmail.com> (raw)
In-Reply-To: <200611272256.44623.arnd@arndb.de>

On 11/27/06, Arnd Bergmann <arnd@arndb.de> wrote:
> On Monday 27 November 2006 22:16, Grant Likely wrote:
> > +#ifdef CONFIG_PCI
> > +/*
> > + * Access functions for PCI config space using RTAS calls.
> > + */
> > +static int rtas_read_config(struct pci_bus *bus, unsigned int devfn, int offset,
> > + int len, u32 * val)
> > +{
> > +struct pci_controller *hose = bus->sysdata;
> > +unsigned long addr = (offset & 0xff) | ((devfn & 0xff) << 8)
> > + | (((bus->number - hose->first_busno) & 0xff) << 16)
> > + | (hose->index << 24);
> > +int ret = -1;
> > +int rval;
> > +
> > +rval = rtas_call(rtas_token("read-pci-config"), 2, 2, &ret, addr, len);
> > +*val = ret;
> > +return rval ? PCIBIOS_DEVICE_NOT_FOUND : PCIBIOS_SUCCESSFUL;
> > +}
> > +
> > +static int rtas_write_config(struct pci_bus *bus, unsigned int devfn,
> > + int offset, int len, u32 val)
> > +{
> > +struct pci_controller *hose = bus->sysdata;
> > +unsigned long addr = (offset & 0xff) | ((devfn & 0xff) << 8)
> > + | (((bus->number - hose->first_busno) & 0xff) << 16)
> > + | (hose->index << 24);
> > +int rval;
> > +
> > +rval = rtas_call(rtas_token("write-pci-config"), 3, 1, NULL,
> > + addr, len, val);
> > +return rval ? PCIBIOS_DEVICE_NOT_FOUND : PCIBIOS_SUCCESSFUL;
> > +}
> > +
>
> I know you're only moving this code, but shouldn't this really use the
> code from arch/powerpc/kernel/rtas_pci.c? If it doesn't work out of
> the box, I guess we should rather split out the pseries specific
> bits from it and make the common parts more generic.
>

Oh, probably.  :)  As you mentioned; because I'm just moving the code,
I certainly don't want to tackle that with this patch series.

The Efika code is still quite young (in fact the code in Paul's tree
isn't complete enough yet to boot), and it is being actively
developed.  Expect to see PCI rework in the future, but I don't know
if it will make the .20 merge window.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2006-11-27 22:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 21:16 MPC52xx support rework for 2.6.20 Grant Likely
2006-11-27 21:16 ` [PATCH 1/9] [POWERPC] Document describing mpc52xx device tree binding conventions Grant Likely
2006-11-27 21:16   ` [PATCH 2/9] [POWERPC] Move MPC52xx PIC driver into arch/powerpc/platforms/52xx Grant Likely
2006-11-27 21:16     ` [PATCH 3/9] [POWERPC] Put mpc52xx support file in platforms/52xx Grant Likely
2006-11-27 21:16       ` [PATCH 4/9] [POWERPC] move Efika support files into platforms/52xx Grant Likely
2006-11-27 21:16         ` [PATCH 5/9] [POWERPC] Separate IRQ config / register set from main header Grant Likely
2006-11-27 21:16           ` [PATCH 6/9] [POWERPC] Add common routines for 52xx support in arch/powerpc Grant Likely
2006-11-27 21:16             ` [PATCH 7/9] [POWERPC] Add lite5200 board support to arch/powerpc Grant Likely
2006-11-27 21:16               ` [PATCH 8/9] [POWERPC] Add device trees for lite5200 and lite5200b eval boards Grant Likely
2006-11-27 21:16                 ` [PATCH 9/9] [POWERPC] defconfig for lite5200 board Grant Likely
2006-11-27 21:56         ` [PATCH 4/9] [POWERPC] move Efika support files into platforms/52xx Arnd Bergmann
2006-11-27 22:09           ` Grant Likely [this message]
2006-11-27 22:12           ` Benjamin Herrenschmidt
2006-11-27 22:33             ` Arnd Bergmann
2006-11-27 21:39 ` MPC52xx support rework for 2.6.20 Sylvain Munaut

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=528646bc0611271409g27ec05a0m9d7149e55256d363@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).