From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [RFC 0/2] sandbox: add gpio support with libftdi1
Date: Wed, 15 Feb 2017 10:12:25 +0300 [thread overview]
Message-ID: <20170215071227.31183-1-antonynpavlov@gmail.com> (raw)
This patch series makes it possible to use FT2232H ACBUS[7:0]
pins as gpio pins from sandbox barebox.
I have tested output gpio functionality by connecting
a LED to ACBUS[0] and lightening it with gpio_direction_output
and gpio_set_value barebox commands.
Also I have performed input test with ACBUS[0] -> ACBUS[1] loopback.
The main goal of adding gpio functionality to sandbox barebox
is using it for connecting real i2c and spi devices to sandbox barebox
(not tested yet).
Antony Pavlov (2):
sandbox: avoid symbol conflict for {open,read,close}dir
sandbox: add gpio support with libftdi1
arch/sandbox/Kconfig | 1 +
arch/sandbox/Makefile | 10 +-
arch/sandbox/board/board.c | 7 ++
arch/sandbox/mach-sandbox/include/mach/linux.h | 11 ++
arch/sandbox/os/Makefile | 3 +
arch/sandbox/os/ftdi.c | 167 +++++++++++++++++++++++++
drivers/gpio/Kconfig | 4 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-libftdi1.c | 116 +++++++++++++++++
9 files changed, 318 insertions(+), 2 deletions(-)
create mode 100644 arch/sandbox/os/ftdi.c
create mode 100644 drivers/gpio/gpio-libftdi1.c
--
2.11.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-02-15 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 7:12 Antony Pavlov [this message]
2017-02-15 7:12 ` [RFC 1/2] sandbox: avoid symbol conflict for {open,read,close}dir Antony Pavlov
2017-02-15 7:12 ` [RFC 2/2] sandbox: add gpio support with libftdi1 Antony Pavlov
2017-02-16 7:34 ` [RFC 0/2] " Sascha Hauer
2017-02-16 8:28 ` Antony Pavlov
2017-02-16 8:25 ` Sascha Hauer
2017-02-16 11:11 ` Ian Abbott
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=20170215071227.31183-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