public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <micky_ching@realsil.com.cn>
To: <sameo@linux.intel.com>, <lee.jones@linaro.org>
Cc: <devel@linuxdriverproject.org>, <linux-kernel@vger.kernel.org>,
	<gregkh@linuxfoundation.org>, <rogerable@realtek.com>,
	<wei_wang@realsil.com.cn>,
	Micky Ching <micky_ching@realsil.com.cn>
Subject: [PATCH v2 0/9] mfd: rtsx: add support for new rts524A and rts525A
Date: Thu, 22 Jan 2015 15:03:07 +0800	[thread overview]
Message-ID: <cover.1421909642.git.micky_ching@realsil.com.cn> (raw)

From: Micky Ching <micky_ching@realsil.com.cn>

v2:
- remove debug info when access failed.
- using macro list for phy register init.
- rename function for multi chip prefix with rtsx_base_
- save pcie_cap offset when init chip, not calling pci_find_capacity()
  every time.
- add pcr->ops: write_phy/read_phy for special chip.

This patchset including re-format some coding-style and add two new chip
rts524A and rts525A.


Micky Ching (9):
  mfd: rtsx: replace TAB by SPC after #define
  mfd: rtsx: place register address and values togather
  mfd: rtsx: update PETXCFG address
  mfd: rtsx: update driving settings
  mfd: rtsx: update phy register
  mfd: rtsx: remove LCTLR defination
  mfd: rtsx: add support for rts524A
  mfd: rtsx: add support for rts525A
  mfd: rtsx: using pcr_dbg replace dev_dbg

 drivers/mfd/Makefile         |    2 +-
 drivers/mfd/rtl8411.c        |   11 +-
 drivers/mfd/rts5209.c        |    4 +-
 drivers/mfd/rts5227.c        |   12 +-
 drivers/mfd/rts5229.c        |    4 +-
 drivers/mfd/rts5249.c        |  368 +++++++++++---
 drivers/mfd/rtsx_gops.c      |   37 --
 drivers/mfd/rtsx_pcr.c       |  110 +++--
 drivers/mfd/rtsx_pcr.h       |    8 +
 include/linux/mfd/rtsx_pci.h | 1109 ++++++++++++++++++++++--------------------
 10 files changed, 966 insertions(+), 699 deletions(-)
 delete mode 100644 drivers/mfd/rtsx_gops.c

-- 
1.9.1


             reply	other threads:[~2015-01-22  7:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  7:03 micky_ching [this message]
2015-01-22  7:03 ` [PATCH v2 1/9] mfd: rtsx: replace TAB by SPC after #define micky_ching
2015-01-22  7:03 ` [PATCH v2 2/9] mfd: rtsx: place register address and values togather micky_ching
2015-01-22  7:03 ` [PATCH v2 3/9] mfd: rtsx: update PETXCFG address micky_ching
2015-01-22  7:03 ` [PATCH v2 4/9] mfd: rtsx: update driving settings micky_ching
2015-01-22  7:03 ` [PATCH v2 5/9] mfd: rtsx: update phy register micky_ching
2015-01-22  7:03 ` [PATCH v2 6/9] mfd: rtsx: remove LCTLR defination micky_ching
2015-01-22  7:03 ` [PATCH v2 7/9] mfd: rtsx: add support for rts524A micky_ching
2015-01-22  7:03 ` [PATCH v2 8/9] mfd: rtsx: add support for rts525A micky_ching
2015-01-22  7:03 ` [PATCH v2 9/9] mfd: rtsx: using pcr_dbg replace dev_dbg micky_ching
2015-01-22  7:18 ` [PATCH v2 0/9] mfd: rtsx: add support for new rts524A and rts525A Lee Jones

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=cover.1421909642.git.micky_ching@realsil.com.cn \
    --to=micky_ching@realsil.com.cn \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rogerable@realtek.com \
    --cc=sameo@linux.intel.com \
    --cc=wei_wang@realsil.com.cn \
    /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