[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4d3048fd-76be-e07d-b155-95a9600053eb@lechnology.com>
Date: Mon, 4 Jan 2021 14:56:41 -0600
From: David Lechner <david@...hnology.com>
To: grzegorz.jaszczyk@...aro.org
Cc: bjorn.andersson@...aro.org, devicetree@...r.kernel.org,
lee.jones@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
linux-remoteproc@...r.kernel.org, mathieu.poirier@...aro.org,
ohad@...ery.com, praneeth@...com, robh+dt@...nel.org,
rogerq@...com, s-anna@...com, ssantosh@...nel.org, t-kristo@...com
Subject: Re: [PATCH v2 2/5] remoteproc: pru: Add APIs to get and put the PRU
cores
>
> @@ -706,14 +824,14 @@ static int pru_rproc_set_id(struct pru_rproc *pru)
> case RTU0_IRAM_ADDR_MASK:
> fallthrough;
> case PRU0_IRAM_ADDR_MASK:
> - pru->id = 0;
> + pru->id = PRUSS_PRU0;
> break;
> case TX_PRU1_IRAM_ADDR_MASK:
> fallthrough;
> case RTU1_IRAM_ADDR_MASK:
> fallthrough;
> case PRU1_IRAM_ADDR_MASK:
> - pru->id = 1;
> + pru->id = PRUSS_PRU1;
> break;
> default:
> ret = -EINVAL;
There is a similar opportunity for using PRUSS_PRU1 in pru_d_da_to_va()
Powered by blists - more mailing lists