From: Michael Neuling <mikey@neuling.org>
To: Philippe Bergheaud <felix@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: imunsie@au1.ibm.com
Subject: Re: [PATCH] cxl: Configure the PSL for dual port CAPI on Naples
Date: Wed, 16 Mar 2016 12:15:11 +1100 [thread overview]
Message-ID: <1458090911.9668.15.camel@neuling.org> (raw)
In-Reply-To: <1458052008-29254-1-git-send-email-felix@linux.vnet.ibm.com>
On Tue, 2016-03-15 at 15:26 +0100, Philippe Bergheaud wrote:
> Naples CPUs have two CAPI ports. =20
Naples is an internal name, don't use that. Use POWER8NVL is the name
we use in the kernel.
alsi, it's a "chip" that has two CAPI ports, not the CPU.
> Configure the PSL to route data to
> the port corresponding to the PHB index.
Isn't this capp unit in reality, not phb index?
>=20
> Signed-off-by: Philippe Bergheaud <felix@linux.vnet.ibm.com>
> ---
> drivers/misc/cxl/pci.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>=20
> diff --git a/drivers/misc/cxl/pci.c b/drivers/misc/cxl/pci.c
> index 0c6c17a1..3db0a0b 100644
> --- a/drivers/misc/cxl/pci.c
> +++ b/drivers/misc/cxl/pci.c
> @@ -340,12 +340,15 @@ static void dump_afu_descriptor(struct cxl_afu
> *afu)
> #undef show_reg
> }
> =20
> +#define CPU_IS_NAPLES() (cur_cpu_spec->pvr_value =3D=3D 0x004c0000)
Use pvr_version_is(PVR_POWER8NVL))
> +
> static int init_implementation_adapter_regs(struct cxl *adapter,
> struct pci_dev *dev)
> {
> struct device_node *np;
> const __be32 *prop;
> u64 psl_dsnctl;
> u64 chipid;
> + u64 phb_index;
> =20
> if (!(np =3D pnv_pci_get_phb_node(dev)))
> return -ENODEV;
> @@ -355,10 +358,20 @@ static int
> init_implementation_adapter_regs(struct cxl *adapter, struct pci_dev
> if (!np)
> return -ENODEV;
> chipid =3D be32_to_cpup(prop);
> - of_node_put(np);
> =20
> /* Tell PSL where to route data to */
> psl_dsnctl =3D 0x02E8900002000000ULL | (chipid << (63-5));
> + if (CPU_IS_NAPLES()) {
> + prop =3D of_get_property(np, "ibm,phb-index", NULL);
> + if (!prop) {
> + of_node_put(np);
> + return -ENODEV;
> + }
> + phb_index =3D be32_to_cpup(prop);
> + psl_dsnctl |=3D (phb_index << (63-11));
Looking at the psl docs, cappunitid in the dsndctl is bits 6 to 13. So
why 11 here?
Can you abstract this better and make it clear what's happening? Try
something like this:
int capp_unit()
{
if (!pvr_version_is(PVR_POWER8NVL))
/* For chips other than POWER8NVL, we only have CAPP 0
* irrespective of which PHB is used */
return 0;
/* For POWER8NVL, assume CAPP 0 is attached to PHB0 and=20
* CAPP 1 is attached to PHB1*/
prop =3D of_get_property(np, "ibm,phb-index", NULL);
if (!prop) {
of_node_put(np);
return -ENODEV;
}
return be32_to_cpup(prop);
}
Then you can do something like (although you need to fix the error
case)
psl_dsnctl |=3D (capp_unit(p) << (63-13));
Mikey
> + }
> + of_node_put(np);
> +
> cxl_p1_write(adapter, CXL_PSL_DSNDCTL, psl_dsnctl);
> cxl_p1_write(adapter, CXL_PSL_RESLCKTO, 0x20000000200ULL);
> /* snoop write mask */
next prev parent reply other threads:[~2016-03-16 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 14:26 [PATCH] cxl: Configure the PSL for dual port CAPI on Naples Philippe Bergheaud
2016-03-16 1:15 ` Michael Neuling [this message]
2016-03-16 8:49 ` Philippe Bergheaud
2016-03-16 8:55 ` Michael Neuling
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=1458090911.9668.15.camel@neuling.org \
--to=mikey@neuling.org \
--cc=felix@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.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 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.