From: Stephen Boyd <sboyd@codeaurora.org>
To: Andy Gross <agross@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bjorn Andersson <bjorn.andersson@sonymobile.com>
Subject: [PATCH 0/3] qcom smd big endian support
Date: Mon, 31 Aug 2015 18:39:51 -0700 [thread overview]
Message-ID: <1441071594-15941-1-git-send-email-sboyd@codeaurora.org> (raw)
This set of patches does some tidying in the beginning to prepare
for adding big endian CPU support to the smd code. It builds on a
previous patch to add big endian support to smem.
Stephen Boyd (3):
soc: qcom: smd: Represent channel layout in structures
soc: qcom: smd: Use __iowrite32_copy() instead of open-coding it
soc: qcom: smd: Handle big endian CPUs
drivers/soc/qcom/smd.c | 221 ++++++++++++++++++++++++++++++-------------------
1 file changed, 136 insertions(+), 85 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] qcom smd big endian support
Date: Mon, 31 Aug 2015 18:39:51 -0700 [thread overview]
Message-ID: <1441071594-15941-1-git-send-email-sboyd@codeaurora.org> (raw)
This set of patches does some tidying in the beginning to prepare
for adding big endian CPU support to the smd code. It builds on a
previous patch to add big endian support to smem.
Stephen Boyd (3):
soc: qcom: smd: Represent channel layout in structures
soc: qcom: smd: Use __iowrite32_copy() instead of open-coding it
soc: qcom: smd: Handle big endian CPUs
drivers/soc/qcom/smd.c | 221 ++++++++++++++++++++++++++++++-------------------
1 file changed, 136 insertions(+), 85 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2015-09-01 1:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 1:39 Stephen Boyd [this message]
2015-09-01 1:39 ` [PATCH 0/3] qcom smd big endian support Stephen Boyd
2015-09-01 1:39 ` [PATCH 1/3] soc: qcom: smd: Represent channel layout in structures Stephen Boyd
2015-09-01 1:39 ` Stephen Boyd
2015-09-01 1:39 ` Stephen Boyd
2015-09-01 4:55 ` Bjorn Andersson
2015-09-01 4:55 ` Bjorn Andersson
2015-09-01 4:55 ` Bjorn Andersson
2015-09-01 17:51 ` Stephen Boyd
2015-09-01 17:51 ` Stephen Boyd
2015-09-01 17:51 ` Stephen Boyd
2015-09-01 1:39 ` [PATCH 2/3] soc: qcom: smd: Use __iowrite32_copy() instead of open-coding it Stephen Boyd
2015-09-01 1:39 ` Stephen Boyd
2015-09-01 4:59 ` Bjorn Andersson
2015-09-01 4:59 ` Bjorn Andersson
2015-09-01 4:59 ` Bjorn Andersson
2015-09-01 18:03 ` Stephen Boyd
2015-09-01 18:03 ` Stephen Boyd
2015-09-01 18:03 ` Stephen Boyd
2015-09-01 20:30 ` Stephen Boyd
2015-09-01 20:30 ` Stephen Boyd
2015-09-01 20:30 ` Stephen Boyd
2015-09-01 1:39 ` [PATCH 3/3] soc: qcom: smd: Handle big endian CPUs Stephen Boyd
2015-09-01 1:39 ` Stephen Boyd
2015-09-01 5:06 ` Bjorn Andersson
2015-09-01 5:06 ` Bjorn Andersson
2015-09-01 5:06 ` Bjorn Andersson
2015-09-01 18:04 ` Stephen Boyd
2015-09-01 18:04 ` Stephen Boyd
2015-09-01 18:04 ` Stephen Boyd
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=1441071594-15941-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.