From: Bjorn Helgaas <bhelgaas@google.com>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: phil.edworthy@renesas.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: Add PCIE_CONF_REGNO macro for PCIECAR register
Date: Fri, 20 Mar 2015 17:44:46 -0500 [thread overview]
Message-ID: <20150320224446.GO26935@google.com> (raw)
In-Reply-To: <1426047830-26410-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>
On Wed, Mar 11, 2015 at 01:23:50PM +0900, Nobuhiro Iwamatsu wrote:
> The reg variable used when setting PCIECAR register need to be masked by 0xFC
> by restriction of the corresponding register.
> This adds PCIE_CONF_REGNO are macros for masking changes that PCIE_CONF_REGNO
> is used when setting PCIECAR register.
>
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> ---
> drivers/pci/host/pcie-rcar.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/host/pcie-rcar.c b/drivers/pci/host/pcie-rcar.c
> index c57bd0a..1f493ef 100644
> --- a/drivers/pci/host/pcie-rcar.c
> +++ b/drivers/pci/host/pcie-rcar.c
> @@ -104,6 +104,7 @@
> #define PCIE_CONF_BUS(b) (((b) & 0xff) << 24)
> #define PCIE_CONF_DEV(d) (((d) & 0x1f) << 19)
> #define PCIE_CONF_FUNC(f) (((f) & 0x7) << 16)
> +#define PCIE_CONF_REGNO(r) (r & 0xfc)
>
> #define RCAR_PCI_MAX_RESOURCES 4
> #define MAX_NR_INBOUND_MAPS 6
> @@ -227,7 +228,8 @@ static int rcar_pcie_config_access(struct rcar_pcie *pcie,
>
> /* Set the PIO address */
> rcar_pci_write_reg(pcie, PCIE_CONF_BUS(bus->number) |
> - PCIE_CONF_DEV(dev) | PCIE_CONF_FUNC(func) | reg, PCIECAR);
> + PCIE_CONF_DEV(dev) | PCIE_CONF_FUNC(func) |
> + PCIE_CONF_REGNO(reg), PCIECAR);
What about the other rcar_pci_read_reg()/rcar_pci_write_reg() calls (the
ones for "if (pci_is_root_bus())"? Do those need to be limited to the
first 256 bytes also?
It seems a little strange to mask "reg = where & ~3" at the top (making it
4-byte aligned), then mask "r & 0xfc" here (limiting to first 256 bytes and
also making it 4-byte aligned).
Seems like those two operations should either be combined or completely
split.
> /* Enable the configuration access */
> if (bus->parent->number == pcie->root_bus_nr)
> --
> 2.1.3
>
next prev parent reply other threads:[~2015-03-20 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 4:23 [PATCH] PCI: rcar: Add PCIE_CONF_REGNO macro for PCIECAR register Nobuhiro Iwamatsu
2015-03-20 22:44 ` Bjorn Helgaas [this message]
2015-03-23 16:16 ` Phil Edworthy
2015-03-25 6:13 ` Nobuhiro Iwamatsu
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=20150320224446.GO26935@google.com \
--to=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=phil.edworthy@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.