linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Bansal <pankaj.bansal@nxp.com>
To: Leo Li <leoyang.li@nxp.com>
Cc: Alexandru Marginean <alexandru.marginean@nxp.com>,
	Pankaj Bansal <pankaj.bansal@nxp.com>,
	linuxppc-dev@lists.ozlabs.org, Varun Sethi <V.Sethi@nxp.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] add i2c controlled qixis driver
Date: Fri,  5 Oct 2018 14:25:03 +0530	[thread overview]
Message-ID: <20181005085505.29024-1-pankaj.bansal@nxp.com> (raw)

FPGA on LX2160AQDS/LX2160ARDB connected on I2C bus, so add qixis
driver which is basically an i2c client driver to control FPGA.

This driver is essential to control MDIO mux multiplexing.

Cc: Varun Sethi <V.Sethi@nxp.com>

Pankaj Bansal (2):
  dt-bindings: soc: fsl: Document Qixis FPGA usage
  fsl: add i2c controlled qixis driver

 .../bindings/soc/fsl/qixis_ctrl.txt           | 33 ++++++++
 drivers/soc/fsl/Kconfig                       |  9 +++
 drivers/soc/fsl/Makefile                      |  1 +
 drivers/soc/fsl/qixis_ctrl.c                  | 75 +++++++++++++++++++
 include/linux/fsl/qixis_ctrl.h                | 20 +++++
 5 files changed, 138 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/soc/fsl/qixis_ctrl.txt
 create mode 100644 drivers/soc/fsl/qixis_ctrl.c
 create mode 100644 include/linux/fsl/qixis_ctrl.h

-- 
2.17.1


             reply	other threads:[~2018-10-05  4:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  8:55 Pankaj Bansal [this message]
2018-10-05  8:55 ` [PATCH 1/2] dt-bindings: soc: fsl: Document Qixis FPGA usage Pankaj Bansal
2018-10-05  8:55 ` [PATCH 2/2] fsl: add i2c controlled qixis driver Pankaj Bansal
2018-12-06  0:12   ` Li Yang

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=20181005085505.29024-1-pankaj.bansal@nxp.com \
    --to=pankaj.bansal@nxp.com \
    --cc=V.Sethi@nxp.com \
    --cc=alexandru.marginean@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.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).