From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH v3 0/3] sandbox: add gpio support with libftdi1
Date: Mon, 22 Jan 2018 12:59:15 +0300 [thread overview]
Message-ID: <20180122095918.11721-1-antonynpavlov@gmail.com> (raw)
This patch series makes it possible to use FT2232H ACBUS[7:0]
pins as gpio pins from sandbox barebox.
There are ready-to-use FT2232H-based boards:
* FT2232H-56Q Mini-Module (http://www.ftdichip.com/Products/Modules/DevelopmentModules.htm#FT2232H-56_Mini)
* FT2232 breakout board (http://dangerousprototypes.com/docs/FT2232_breakout_board)
The main goal of adding gpio functionality to sandbox barebox
is using it for connecting real i2c and spi devices to sandbox barebox.
Sample dts-file for at24 i2c eeprom and at25 spi flash is included.
Changes since v2 patch series (http://lists.infradead.org/pipermail/barebox/2018-January/031887.html):
* ftdi USB IDs are moved to dts, parseopt_* functions are unused;
* dts stuff moved to sandbox-libftdi-example.dtsi;
* led example is added.
Changes since v1 patch series (http://lists.infradead.org/pipermail/barebox/2017-October/031306.html):
* rebase on top barebox v2017.12.0;
* ds1307 i2c rtc driver works fine (i2c-gpio,scl-output-only is used);
* parseopt_* functions are used for cmdline parsing.
Changes since RFC v1 patch series (http://lists.infradead.org/pipermail/barebox/2017-February/029106.html):
* rebase on top barebox v2017.10.0;
* libftdi cmdline options are added;
* device tree support is added.
Antony Pavlov (3):
sandbox: avoid symbol conflict for {open,read,close}dir
sandbox: add gpio support with libftdi1
sandbox: add i2c and spi libftdi1 bit-bang example
arch/sandbox/Kconfig | 1 +
arch/sandbox/Makefile | 10 +-
arch/sandbox/configs/sandbox_defconfig | 21 +++-
arch/sandbox/dts/sandbox-libftdi-example.dtsi | 80 +++++++++++++
arch/sandbox/mach-sandbox/include/mach/linux.h | 12 ++
arch/sandbox/os/Makefile | 3 +
arch/sandbox/os/ftdi.c | 154 +++++++++++++++++++++++++
drivers/gpio/Kconfig | 4 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-libftdi1.c | 137 ++++++++++++++++++++++
10 files changed, 420 insertions(+), 3 deletions(-)
create mode 100644 arch/sandbox/dts/sandbox-libftdi-example.dtsi
create mode 100644 arch/sandbox/os/ftdi.c
create mode 100644 drivers/gpio/gpio-libftdi1.c
--
2.15.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-01-22 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 9:59 Antony Pavlov [this message]
2018-01-22 9:59 ` [PATCH v3 1/3] sandbox: avoid symbol conflict for {open, read, close}dir Antony Pavlov
2018-01-22 9:59 ` [PATCH v3 2/3] sandbox: add gpio support with libftdi1 Antony Pavlov
2018-01-22 9:59 ` [PATCH v3 3/3] sandbox: add i2c and spi libftdi1 bit-bang example Antony Pavlov
2018-01-25 7:12 ` Sascha Hauer
2018-01-26 8:37 ` Antony Pavlov
2018-01-29 7:28 ` Sascha Hauer
2018-01-24 9:10 ` [PATCH v3 0/3] sandbox: add gpio support with libftdi1 Antony Pavlov
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=20180122095918.11721-1-antonynpavlov@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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