From: Michael Ellerman <mpe@ellerman.id.au>
To: Philippe Bergheaud <felix@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Philippe Bergheaud <felix@linux.vnet.ibm.com>,
mikey@neuling.org, imunsie@au1.ibm.com
Subject: Re: [v2,2/2] cxl: Configure the PSL for two CAPI ports on POWER8NVL
Date: Wed, 30 Mar 2016 11:21:57 +1100 (AEDT) [thread overview]
Message-ID: <3qZSxx3cszz9sBg@ozlabs.org> (raw)
In-Reply-To: <1458145736-20326-2-git-send-email-felix@linux.vnet.ibm.com>
On Wed, 2016-16-03 at 16:28:56 UTC, Philippe Bergheaud wrote:
> The POWER8NVL chip has two CAPI ports. Configure the PSL to route
> data to the port corresponding to the CAPP unit.
>
> diff --git a/drivers/misc/cxl/pci.c b/drivers/misc/cxl/pci.c
> index 0c6c17a1..924ba63 100644
> --- a/drivers/misc/cxl/pci.c
> +++ b/drivers/misc/cxl/pci.c
> @@ -340,12 +341,35 @@ static void dump_afu_descriptor(struct cxl_afu *afu)
> #undef show_reg
> }
>
> +#define CAPP_UNIT0_ID 0xBA
> +#define CAPP_UNIT1_ID 0XBE
> +
> +static u64 capp_unit_id(struct device_node *np)
It's always nice if function names contain a verb, eg. get_capp_unit_id().
> +{
> + const __be32 *prop;
> + u64 phb_index;
> +
> + /* For chips other than POWER8NVL, we only have CAPP 0,
> + * irrespective of which PHB is used */
Can you use the standard block commenting style please, eg:
/*
* For chips ..
*/
> + if (!pvr_version_is(PVR_POWER8NVL))
> + return CAPP_UNIT0_ID ;
^
don't need a space here
> + /* For POWER8NVL, assume CAPP 0 is attached to PHB0 and
> + * CAPP 1 is attached to PHB1 */
> + prop = of_get_property(np, "ibm,phb-index", NULL);
Please use of_property_read_u32().
> + if (!prop)
> + return 0;
> + phb_index = be32_to_cpup(prop);
Some blank lines here would help readability.
> + return phb_index ? CAPP_UNIT1_ID : CAPP_UNIT0_ID;
This logic doesn't quite match your comment above. This says that any non-zero
PHB index is CAPP1, whereas the comment says CAPP1 == PHB1.
> +}
> +
> 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 cappunitid;
capp_unit_id ?
> if (!(np = pnv_pci_get_phb_node(dev)))
> return -ENODEV;
> @@ -355,10 +379,15 @@ static int init_implementation_adapter_regs(struct cxl *adapter, struct pci_dev
> if (!np)
> return -ENODEV;
> chipid = be32_to_cpup(prop);
> + cappunitid = capp_unit_id(np);
> of_node_put(np);
> + if (!cappunitid)
> + return -ENODEV;
You probably want a pr_xxx() there don't you?
> /* Tell PSL where to route data to */
> - psl_dsnctl = 0x02E8900002000000ULL | (chipid << (63-5));
> + psl_dsnctl = 0x0000900002000000ULL | (chipid << (63-5));
> + psl_dsnctl |= (cappunitid << (63-13));
> +
> cxl_p1_write(adapter, CXL_PSL_DSNDCTL, psl_dsnctl);
> cxl_p1_write(adapter, CXL_PSL_RESLCKTO, 0x20000000200ULL);
> /* snoop write mask */
cheers
next prev parent reply other threads:[~2016-03-30 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:28 [PATCH v2 1/2] powerpc: Define PVR value for POWER8NVL processor Philippe Bergheaud
2016-03-16 16:28 ` [PATCH v2 2/2] cxl: Configure the PSL for two CAPI ports on POWER8NVL Philippe Bergheaud
2016-03-24 20:48 ` Ian Munsie
2016-03-30 0:21 ` Michael Ellerman [this message]
2016-03-24 20:48 ` [PATCH v2 1/2] powerpc: Define PVR value for POWER8NVL processor Ian Munsie
2016-03-25 10:06 ` [v2,1/2] " Michael Ellerman
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=3qZSxx3cszz9sBg@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=felix@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).