From: Pankaj Bansal <pankaj.bansal@nxp.com>
To: Leo Li <leoyang.li@nxp.com>
Cc: Pankaj Bansal <pankaj.bansal@nxp.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Varun Sethi <V.Sethi@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v3 0/2] add qixis driver
Date: Mon, 4 Feb 2019 09:10:00 +0000 [thread overview]
Message-ID: <20190204143449.25040-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.
Also added platform driver for MMIO based FPGA, like the one available
on LS2088ARDB/LS2088AQDS.
This driver is essential to control MDIO mux multiplexing.
This driver is dependent on below patches:
https://www.mail-archive.com/netdev@vger.kernel.org/msg281274.html
Cc: Varun Sethi <V.Sethi@nxp.com>
---
Notes:
V2:
- https://patchwork.kernel.org/cover/10788341/
V1:
- https://patchwork.kernel.org/cover/10627297/
Pankaj Bansal (2):
dt-bindings: soc: fsl: Document Qixis FPGA usage
drivers: soc: fsl: add qixis driver
.../bindings/soc/fsl/qixis_ctrl.txt | 53 +++++
drivers/soc/fsl/Kconfig | 11 +
drivers/soc/fsl/Makefile | 1 +
drivers/soc/fsl/qixis_ctrl.c | 207 ++++++++++++++++++
4 files changed, 272 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/fsl/qixis_ctrl.txt
create mode 100644 drivers/soc/fsl/qixis_ctrl.c
--
2.17.1
next reply other threads:[~2019-02-04 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 9:10 Pankaj Bansal [this message]
2019-02-04 9:10 ` [PATCH v3 1/2] dt-bindings: soc: fsl: Document Qixis FPGA usage Pankaj Bansal
2019-02-04 20:12 ` Li Yang
2019-02-04 9:10 ` [PATCH v3 2/2] drivers: soc: fsl: add qixis driver Pankaj Bansal
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=20190204143449.25040-1-pankaj.bansal@nxp.com \
--to=pankaj.bansal@nxp.com \
--cc=V.Sethi@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