From: Aswath Govindraju <a-govindraju@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Matt Kline <matt@bitbashing.io>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] can: m_can: m_can_platform: Fix iomap_read_fifo() and iomap_write_fifo()
Date: Mon, 20 Sep 2021 17:57:26 +0530 [thread overview]
Message-ID: <2f34d1bf-48d1-ed6e-b789-b5930a8effaa@ti.com> (raw)
In-Reply-To: <20210920122610.570-1-a-govindraju@ti.com>
Hi all,
On 20/09/21 5:56 pm, Aswath Govindraju wrote:
> The read an writes from the fifo are from a buffer with various fields and
> data at predefined offsets. So, they reads and writes should not be done to
> the same address(or port) in case of val_count greater than 1. Therefore,
> fix this by using iowrite32/ioread32 instead of ioread32_rep/iowrite32_rep.
>
> Also, the write into fifo must be performed with an offset from the message
> ram base address. Therefore, fix the base address to mram_base.
>
> Fixes: e39381770ec9 ("can: m_can: Disable IRQs on FIFO bus errors")
> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> ---
Please ignore this patch sent it my mistake. Sorry for the inconvenience.
Thanks,
Aswath
> drivers/net/can/m_can/m_can_platform.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/can/m_can/m_can_platform.c b/drivers/net/can/m_can/m_can_platform.c
> index 308d4f2fff00..eee47bad0592 100644
> --- a/drivers/net/can/m_can/m_can_platform.c
> +++ b/drivers/net/can/m_can/m_can_platform.c
> @@ -32,8 +32,13 @@ static u32 iomap_read_reg(struct m_can_classdev *cdev, int reg)
> static int iomap_read_fifo(struct m_can_classdev *cdev, int offset, void *val, size_t val_count)
> {
> struct m_can_plat_priv *priv = cdev_to_priv(cdev);
> + void __iomem *src = priv->mram_base + offset;
>
> - ioread32_rep(priv->mram_base + offset, val, val_count);
> + while (val_count--) {
> + *(unsigned int *)val = ioread32(src);
> + val += 4;
> + src += 4;
> + }
>
> return 0;
> }
> @@ -51,8 +56,13 @@ static int iomap_write_fifo(struct m_can_classdev *cdev, int offset,
> const void *val, size_t val_count)
> {
> struct m_can_plat_priv *priv = cdev_to_priv(cdev);
> + void __iomem *dst = priv->mram_base + offset;
>
> - iowrite32_rep(priv->base + offset, val, val_count);
> + while (val_count--) {
> + iowrite32(*(unsigned int *)val, dst);
> + val += 4;
> + dst += 4;
> + }
>
> return 0;
> }
>
next prev parent reply other threads:[~2021-09-20 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:26 [PATCH] can: m_can: m_can_platform: Fix iomap_read_fifo() and iomap_write_fifo() Aswath Govindraju
2021-09-20 12:27 ` Aswath Govindraju [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-20 12:33 Aswath Govindraju
2021-10-17 20:44 ` Marc Kleine-Budde
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=2f34d1bf-48d1-ed6e-b789-b5930a8effaa@ti.com \
--to=a-govindraju@ti.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=matt@bitbashing.io \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rcsekar@samsung.com \
--cc=wg@grandegger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox