All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Andy Gross" <agross@codeaurora.org>,
	"Bjorn Andersson" <bjorn.andersson@sonymobile.com>,
	"Hauke Mehrtens" <hauke@hauke-m.de>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Paul Walmsley" <paul@pwsan.com>,
	linux-mips@linux-mips.org, "David Howells" <dhowells@redhat.com>,
	linux-soc@vger.kernel.org
Subject: [PATCH v3 0/4] Add __ioread32_copy() and use it
Date: Fri, 23 Oct 2015 13:01:48 -0700	[thread overview]
Message-ID: <1445630512-10888-1-git-send-email-sboyd@codeaurora.org> (raw)

The SMD driver is reading and writing chunks of data to iomem,
and there's an __iowrite32_copy() function for the writing part, but
no __ioread32_copy() function for the reading part. This series
adds __ioread32_copy() and uses it in two places.

This is a respin with some small fixes found with soaking in -next.

Andrew, the patches should apply cleanly to linux-next, so I hope
you can pick them up directly now, instead of the previous plan where
they would go through Andy's tree.

Changes from v2:
 * Make bcm patch actually compile
 * Add new patch for frv to avoid warnings

Cc: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Rafał Miłecki <zajec5@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: linux-mips@linux-mips.org
Cc: David Howells <dhowells@redhat.com>
Cc: linux-soc@vger.kernel.org

Stephen Boyd (4):
  frv: io: Accept const void pointers for read{b,w,l}()
  lib: iomap_copy: Add __ioread32_copy()
  soc: qcom: smd: Use __ioread32_copy() instead of open-coding it
  FIRMWARE: bcm47xx_nvram: Use __ioread32_copy() instead of open-coding

 arch/frv/include/asm/io.h                 | 17 ++++++++++++++---
 drivers/firmware/broadcom/bcm47xx_nvram.c | 11 +++--------
 drivers/soc/qcom/smd.c                    | 13 ++++---------
 include/linux/io.h                        |  1 +
 lib/iomap_copy.c                          | 21 +++++++++++++++++++++
 5 files changed, 43 insertions(+), 20 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 v3 0/4] Add __ioread32_copy() and use it
Date: Fri, 23 Oct 2015 13:01:48 -0700	[thread overview]
Message-ID: <1445630512-10888-1-git-send-email-sboyd@codeaurora.org> (raw)

The SMD driver is reading and writing chunks of data to iomem,
and there's an __iowrite32_copy() function for the writing part, but
no __ioread32_copy() function for the reading part. This series
adds __ioread32_copy() and uses it in two places.

This is a respin with some small fixes found with soaking in -next.

Andrew, the patches should apply cleanly to linux-next, so I hope
you can pick them up directly now, instead of the previous plan where
they would go through Andy's tree.

Changes from v2:
 * Make bcm patch actually compile
 * Add new patch for frv to avoid warnings

Cc: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Rafa? Mi?ecki <zajec5@gmail.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: linux-mips at linux-mips.org
Cc: David Howells <dhowells@redhat.com>
Cc: linux-soc at vger.kernel.org

Stephen Boyd (4):
  frv: io: Accept const void pointers for read{b,w,l}()
  lib: iomap_copy: Add __ioread32_copy()
  soc: qcom: smd: Use __ioread32_copy() instead of open-coding it
  FIRMWARE: bcm47xx_nvram: Use __ioread32_copy() instead of open-coding

 arch/frv/include/asm/io.h                 | 17 ++++++++++++++---
 drivers/firmware/broadcom/bcm47xx_nvram.c | 11 +++--------
 drivers/soc/qcom/smd.c                    | 13 ++++---------
 include/linux/io.h                        |  1 +
 lib/iomap_copy.c                          | 21 +++++++++++++++++++++
 5 files changed, 43 insertions(+), 20 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2015-10-23 20:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 20:01 Stephen Boyd [this message]
2015-10-23 20:01 ` [PATCH v3 0/4] Add __ioread32_copy() and use it Stephen Boyd
2015-10-23 20:01 ` [PATCH v3 1/4] frv: io: Accept const void pointers for read{b,w,l}() Stephen Boyd
2015-10-23 20:01   ` Stephen Boyd
2015-10-23 20:01 ` [PATCH v3 2/4] lib: iomap_copy: Add __ioread32_copy() Stephen Boyd
2015-10-23 20:01   ` Stephen Boyd
2015-10-23 20:01 ` [PATCH v3 3/4] soc: qcom: smd: Use __ioread32_copy() instead of open-coding it Stephen Boyd
2015-10-23 20:01   ` Stephen Boyd
2015-10-23 20:22   ` Bjorn Andersson
2015-10-23 20:22     ` Bjorn Andersson
2015-10-26  2:00   ` Andy Gross
2015-10-26  2:00     ` Andy Gross
2015-10-23 20:01 ` [PATCH v3 4/4] FIRMWARE: bcm47xx_nvram: Use __ioread32_copy() instead of open-coding Stephen Boyd
2015-10-23 20:01   ` 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=1445630512-10888-1-git-send-email-sboyd@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=agross@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=dhowells@redhat.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=zajec5@gmail.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.