From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Simon Horman <horms@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Dan Carpenter <error27@gmail.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] remoteproc: pru: remove always true check positive unsigned value
Date: Wed, 5 Apr 2023 10:59:46 -0600 [thread overview]
Message-ID: <20230405165946.GA3812912@p14s> (raw)
In-Reply-To: <20230404-pru-always-true-v1-1-b1b55eeff188@kernel.org>
On Tue, Apr 04, 2023 at 02:44:53PM +0200, Simon Horman wrote:
> In both cases they type of da is u32. And PRU_PDRAM_DA is 0.
> So the check da >= PRU_PDRAM_DA is always true and can be removed.
>
> Flagged by Smatch:
>
> drivers/remoteproc/pru_rproc.c:660 pru_d_da_to_va() warn: always true condition '(da >= 0) => (0-u32max >= 0)'
> drivers/remoteproc/pru_rproc.c:709 pru_i_da_to_va() warn: always true condition '(da >= 0) => (0-u32max >= 0)'
>
> No functional changes intended.
> Compile tested only.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://www.spinics.net/lists/kernel/msg4025983.html
> Signed-off-by: Simon Horman <horms@kernel.org>
> ---
> drivers/remoteproc/pru_rproc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
Applied
Thanks,
Mathieu
> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
> index b76db7fa693d..095f66130f48 100644
> --- a/drivers/remoteproc/pru_rproc.c
> +++ b/drivers/remoteproc/pru_rproc.c
> @@ -657,7 +657,7 @@ static void *pru_d_da_to_va(struct pru_rproc *pru, u32 da, size_t len)
> swap(dram0, dram1);
> shrd_ram = pruss->mem_regions[PRUSS_MEM_SHRD_RAM2];
>
> - if (da >= PRU_PDRAM_DA && da + len <= PRU_PDRAM_DA + dram0.size) {
> + if (da + len <= PRU_PDRAM_DA + dram0.size) {
> offset = da - PRU_PDRAM_DA;
> va = (__force void *)(dram0.va + offset);
> } else if (da >= PRU_SDRAM_DA &&
> @@ -706,8 +706,7 @@ static void *pru_i_da_to_va(struct pru_rproc *pru, u32 da, size_t len)
> */
> da &= 0xfffff;
>
> - if (da >= PRU_IRAM_DA &&
> - da + len <= PRU_IRAM_DA + pru->mem_regions[PRU_IOMEM_IRAM].size) {
> + if (da + len <= PRU_IRAM_DA + pru->mem_regions[PRU_IOMEM_IRAM].size) {
> offset = da - PRU_IRAM_DA;
> va = (__force void *)(pru->mem_regions[PRU_IOMEM_IRAM].va +
> offset);
>
prev parent reply other threads:[~2023-04-05 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 12:44 [PATCH] remoteproc: pru: remove always true check positive unsigned value Simon Horman
2023-04-04 12:51 ` Mukesh Ojha
2023-04-05 16:59 ` Mathieu Poirier [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=20230405165946.GA3812912@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=error27@gmail.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lkp@intel.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.