From: Manivannan Sadhasivam <mani@kernel.org>
To: Paul Davey <paul.davey@alliedtelesis.co.nz>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] bus: mhi: Fix MHI on big endian architectures
Date: Fri, 18 Jun 2021 11:14:48 +0530 [thread overview]
Message-ID: <20210618054448.GI3682@workstation> (raw)
In-Reply-To: <20210618033132.24839-1-paul.davey@alliedtelesis.co.nz>
On Fri, Jun 18, 2021 at 03:31:30PM +1200, Paul Davey wrote:
> I encountered some problems getting the MHI driver to work on an Octeon
> 3 platform these seem to all be related to endianness issues. The modem
> interface appears to require the DMA structures to be in little endian,
> however the MHI core driver was assembling them in native endianness.
>
So glad to see MHI being used on big endian architectures :)
Thanks,
Mani
> Using little endian explicitly allows the interface to function as
> expected.
>
> Paul Davey (2):
> bus: mhi: Fix pm_state conversion to string
> bus: mhi: Fix MHI DMA structure endianness
>
> drivers/bus/mhi/core/debugfs.c | 26 +++----
> drivers/bus/mhi/core/init.c | 39 +++++-----
> drivers/bus/mhi/core/internal.h | 129 ++++++++++++++++----------------
> drivers/bus/mhi/core/main.c | 36 ++++-----
> drivers/bus/mhi/core/pm.c | 8 +-
> 5 files changed, 121 insertions(+), 117 deletions(-)
>
> --
> 2.32.0
>
prev parent reply other threads:[~2021-06-18 5:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 3:31 [PATCH 0/2] bus: mhi: Fix MHI on big endian architectures Paul Davey
2021-06-18 3:31 ` [PATCH 1/2] bus: mhi: Fix pm_state conversion to string Paul Davey
2021-06-18 6:12 ` Manivannan Sadhasivam
2021-06-18 21:41 ` Hemant Kumar
2021-06-18 3:31 ` [PATCH 2/2] bus: mhi: Fix MHI DMA structure endianness Paul Davey
2021-06-18 6:29 ` Manivannan Sadhasivam
2021-06-18 6:32 ` Manivannan Sadhasivam
2021-06-22 1:31 ` Bhaumik Bhatt
2021-06-18 5:44 ` Manivannan Sadhasivam [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=20210618054448.GI3682@workstation \
--to=mani@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.davey@alliedtelesis.co.nz \
/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).