Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Jiang Liu <liuj97@gmail.com>, Ralf Baechle <ralf@linux-mips.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Don Dutile <ddutile@redhat.com>, Jiang Liu <jiang.liu@huawei.com>,
	Yinghai Lu <yinghai@kernel.org>,
	Taku Izumi <izumi.taku@jp.fujitsu.com>,
	"Rafael J . Wysocki" <rjw@sisk.pl>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	Yijing Wang <wangyijing@huawei.com>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 13/32] PCI/MIPS: use PCIe capabilities access functions to simplify implementation
Date: Mon, 13 Aug 2012 14:40:04 -0700	[thread overview]
Message-ID: <50297434.8090806@gmail.com> (raw)
In-Reply-To: <1343836477-7287-14-git-send-email-jiang.liu@huawei.com>

On 08/01/2012 08:54 AM, Jiang Liu wrote:
> From: Jiang Liu<jiang.liu@huawei.com>
>
> Use PCIe capabilities access functions to simplify PCIe MIPS implementation.
>
> Signed-off-by: Jiang Liu<liuj97@gmail.com>

Acked-by: David Daney <david.daney@cavium.com>

> ---
>   arch/mips/pci/pci-octeon.c |   15 +++++----------
>   1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/arch/mips/pci/pci-octeon.c b/arch/mips/pci/pci-octeon.c
> index 52a1ba7..aaed2ad 100644
> --- a/arch/mips/pci/pci-octeon.c
> +++ b/arch/mips/pci/pci-octeon.c
> @@ -117,16 +117,11 @@ int pcibios_plat_dev_init(struct pci_dev *dev)
>   	}
>
>   	/* Enable the PCIe normal error reporting */
> -	pos = pci_find_capability(dev, PCI_CAP_ID_EXP);
> -	if (pos) {
> -		/* Update Device Control */
> -		pci_read_config_word(dev, pos + PCI_EXP_DEVCTL,&config);
> -		config |= PCI_EXP_DEVCTL_CERE; /* Correctable Error Reporting */
> -		config |= PCI_EXP_DEVCTL_NFERE; /* Non-Fatal Error Reporting */
> -		config |= PCI_EXP_DEVCTL_FERE;  /* Fatal Error Reporting */
> -		config |= PCI_EXP_DEVCTL_URRE;  /* Unsupported Request */
> -		pci_write_config_word(dev, pos + PCI_EXP_DEVCTL, config);
> -	}
> +	config = PCI_EXP_DEVCTL_CERE; /* Correctable Error Reporting */
> +	config |= PCI_EXP_DEVCTL_NFERE; /* Non-Fatal Error Reporting */
> +	config |= PCI_EXP_DEVCTL_FERE;  /* Fatal Error Reporting */
> +	config |= PCI_EXP_DEVCTL_URRE;  /* Unsupported Request */
> +	pci_pcie_capability_change_word(dev, PCI_EXP_DEVCTL, config, 0);
>
>   	/* Find the Advanced Error Reporting capability */
>   	pos = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ERR);

      reply	other threads:[~2012-08-13 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1343836477-7287-1-git-send-email-jiang.liu@huawei.com>
2012-08-01 15:54 ` [PATCH v3 13/32] PCI/MIPS: use PCIe capabilities access functions to simplify implementation Jiang Liu
2012-08-13 21:40   ` David Daney [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=50297434.8090806@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=ddutile@redhat.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=rjw@sisk.pl \
    --cc=wangyijing@huawei.com \
    --cc=yinghai@kernel.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