linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michal Ostrowski <mostrows@watson.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Do not write virq back to PCI config space (revised patch).
Date: Thu, 28 Dec 2006 15:45:35 +1100	[thread overview]
Message-ID: <1167281135.23340.60.camel@localhost.localdomain> (raw)
In-Reply-To: <E1GzmfD-00076j-G2@arlx188.austin.ibm.com>

On Wed, 2006-12-27 at 22:14 -0600, Michal Ostrowski wrote:
> (Revised version, includes changes for 32 and 64 bit platforms.)
> 
> - Drivers will not rely on the PCI config space value, as they've
>   already been conditioned to rely on the irq field in "struct pci_dev".
> 
> - The virq value may not be < 256 as it has been remapped.
> 
> - The PCI config space should reflect the hardware configuration, which
>   is not being changed.  We are only creating a virtual irq mapping that
>   exists in the kernel only. One would never expect the PCI hardware to
>   generate the "virq" interrupt.
> 
> Signed-off-by: Michal Ostrowski <mostrows@watson.ibm.com>

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

> ---
>  arch/powerpc/kernel/pci_32.c |    1 -
>  arch/powerpc/kernel/pci_64.c |    1 -
>  2 files changed, 0 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/powerpc/kernel/pci_32.c b/arch/powerpc/kernel/pci_32.c
> index 0d9ff72..0df9126 100644
> --- a/arch/powerpc/kernel/pci_32.c
> +++ b/arch/powerpc/kernel/pci_32.c
> @@ -1459,7 +1459,6 @@ int pci_read_irq_line(struct pci_dev *pci_dev)
>  		return -1;
>  	}
>  	pci_dev->irq = virq;
> -	pci_write_config_byte(pci_dev, PCI_INTERRUPT_LINE, virq);
>  
>  	return 0;
>  }
> diff --git a/arch/powerpc/kernel/pci_64.c b/arch/powerpc/kernel/pci_64.c
> index 9bae8a5..81a73fb 100644
> --- a/arch/powerpc/kernel/pci_64.c
> +++ b/arch/powerpc/kernel/pci_64.c
> @@ -1305,7 +1305,6 @@ int pci_read_irq_line(struct pci_dev *pci_dev)
>  	DBG(" -> mapped to linux irq %d\n", virq);
>  
>  	pci_dev->irq = virq;
> -	pci_write_config_byte(pci_dev, PCI_INTERRUPT_LINE, virq);
>  
>  	return 0;
>  }

      reply	other threads:[~2006-12-28  4:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28  4:14 [PATCH] Do not write virq back to PCI config space (revised patch) Michal Ostrowski
2006-12-28  4:45 ` Benjamin Herrenschmidt [this message]

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=1167281135.23340.60.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mostrows@watson.ibm.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).