From: Aleksander Morgado <aleksander@aleksander.es>
To: barebox@lists.infradead.org
Cc: andrew.smirnov@gmail.com, Aleksander Morgado <aleksander@aleksander.es>
Subject: [PATCH v2 0/7] RATP i2c and GPIO support
Date: Wed, 12 Sep 2018 15:45:43 +0200 [thread overview]
Message-ID: <20180912134550.3970-1-aleksander@aleksander.es> (raw)
This series of patches implements support for i2c and GPIO operations via RATP.
It addresses most of the comments from the first series review, except for Sascha's suggestion to implement name resolving for the i2c buses and Andrey's suggestion to prepare a new helper method to initialize the i2c_client structure. I already have a patch for the latter, but will send it for review once these have been accepted and merged, as it's really a bit orthogonal to the whole RATP logic.
Another different w.r.t. v1 apart from addressing the comments is the review is that I made the RATP i2c support depend on CONFIG_I2C and the RATP GPIO support on CONFIG_GENERIC_GPIO. That was missing, and was breaking build if RATP was selected but no i2c or GPIO support was included in the build.
Comments welcome!
Aleksander Morgado (7):
ratp: implement i2c read/write support
bbremote: implement i2c read/write support
ratp: implement support for GPIO commands
bbremote: implement support for GPIO operations
ratp: use __packed instead of the full form
ratp: use pr_ macros to print messages
ratp: fix incorrect whitespaces in method calls
common/ratp/Kconfig | 15 ++
common/ratp/Makefile | 2 +
common/ratp/getenv.c | 12 +-
common/ratp/gpio.c | 144 ++++++++++++++++++
common/ratp/i2c.c | 284 +++++++++++++++++++++++++++++++++++
common/ratp/md.c | 24 +--
common/ratp/mw.c | 24 +--
common/ratp/reset.c | 10 +-
include/ratp_bb.h | 10 ++
scripts/remote/controller.py | 60 ++++++++
scripts/remote/main.py | 74 +++++++++
scripts/remote/messages.py | 179 ++++++++++++++++++++++
12 files changed, 806 insertions(+), 32 deletions(-)
create mode 100644 common/ratp/gpio.c
create mode 100644 common/ratp/i2c.c
--
2.19.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-09-12 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 13:45 Aleksander Morgado [this message]
2018-09-12 13:45 ` [PATCH v2 1/7] ratp: implement i2c read/write support Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 2/7] bbremote: " Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 3/7] ratp: implement support for GPIO commands Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 4/7] bbremote: implement support for GPIO operations Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 5/7] ratp: use __packed instead of the full form Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 6/7] ratp: use pr_ macros to print messages Aleksander Morgado
2018-09-12 13:45 ` [PATCH v2 7/7] ratp: fix incorrect whitespaces in method calls Aleksander Morgado
2018-09-17 7:50 ` [PATCH v2 0/7] RATP i2c and GPIO support Sascha Hauer
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=20180912134550.3970-1-aleksander@aleksander.es \
--to=aleksander@aleksander.es \
--cc=andrew.smirnov@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