linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Gorski <jogo-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Florian Fainelli
	<florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Subject: [PATCH V3 0/3] spi/bcm63xx: cleanup and decouple from arch code
Date: Mon, 12 Oct 2015 12:24:20 +0200	[thread overview]
Message-ID: <1444645463-20915-1-git-send-email-jogo@openwrt.org> (raw)

This patchset decouples spi-bcm63xx from any arch code to allow building
it for more than MIPS/BCM63XX as well as allow compile testing it on any
arch/platform.

Since the main target of this patch is the spi driver, it should
probably go through the spi tree.

Changes v2 -> v3:

* Rebase onto applied patches 1~4 of v1.

Changes v1 -> v2:

* Use device name instead of register size for identifying core
  version.
* Since we now touch arch/mips, drop the rest as well.
* Fix big endian detection.
* Reorder the patches so the move of the register definitions is the
  last step.

Jonas Gorski (3):
  spi/bcm63xx: fix standard accessors and compile guard
  spi/bcm63xx: move message control word description to register offsets
  spi/bcm63xx: move register definitions into the driver

 arch/mips/bcm63xx/dev-spi.c                        |  42 +----
 .../include/asm/mach-bcm63xx/bcm63xx_dev_spi.h     |  44 -----
 drivers/spi/Kconfig                                |   2 +-
 drivers/spi/spi-bcm63xx.c                          | 202 ++++++++++++++++++---
 4 files changed, 179 insertions(+), 111 deletions(-)

-- 
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-10-12 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 10:24 Jonas Gorski [this message]
     [not found] ` <1444645463-20915-1-git-send-email-jogo-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2015-10-12 10:24   ` [PATCH V3 1/3] spi/bcm63xx: fix standard accessors and compile guard Jonas Gorski
     [not found]     ` <1444645463-20915-2-git-send-email-jogo-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2015-10-12 16:59       ` Applied "spi/bcm63xx: fix standard accessors and compile guard" to the spi tree Mark Brown
2015-10-12 10:24   ` [PATCH V3 2/3] spi/bcm63xx: move message control word description to register offsets Jonas Gorski
     [not found]     ` <1444645463-20915-3-git-send-email-jogo-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2015-10-12 16:59       ` Applied "spi/bcm63xx: move message control word description to register offsets" to the spi tree Mark Brown
2015-10-12 10:24   ` [PATCH V3 3/3] spi/bcm63xx: move register definitions into the driver Jonas Gorski

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=1444645463-20915-1-git-send-email-jogo@openwrt.org \
    --to=jogo-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=florian-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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).