From: Kamel Bouhara <kamel.bouhara@bootlin.com>
To: Codrin.Ciubotariu@microchip.com
Cc: Kamel Bouhara <kamel.bouhara@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] SAMA5D2 i2c bus recovery testing
Date: Thu, 5 Dec 2019 15:03:02 +0100 [thread overview]
Message-ID: <20191205140305.1144788-1-kamel.bouhara@bootlin.com> (raw)
Here are the sama5d2 patches, as there is not pinmux defined in the
dtsi. I choosed to only apply it to derivated board as the i2c
configuration is specific for each.
Of course, it could be great if could test it on the ptc board as well.
Best Regards,
Kamel
Kamel Bouhara (3):
dt-bindings: i2c: at91: document optional bus recovery properties
i2c: at91: implement i2c bus recovery
ARM: at91/dt: sama5d2: add i2c gpio pinctrl
.../devicetree/bindings/i2c/i2c-at91.txt | 10 +++
arch/arm/boot/dts/at91-sama5d2_ptc_ek.dts | 33 +++++++++-
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 33 +++++++++-
drivers/i2c/busses/i2c-at91-master.c | 64 +++++++++++++++++++
drivers/i2c/busses/i2c-at91.h | 8 +++
5 files changed, 142 insertions(+), 6 deletions(-)
--
2.24.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-12-05 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:03 Kamel Bouhara [this message]
2019-12-05 14:03 ` [PATCH 1/3] dt-bindings: i2c: at91: document optional bus recovery properties Kamel Bouhara
2019-12-05 14:03 ` [PATCH 2/3] i2c: at91: implement i2c bus recovery Kamel Bouhara
2019-12-05 14:03 ` [PATCH 3/3] ARM: at91/dt: sama5d2: add i2c gpio pinctrl Kamel Bouhara
2019-12-16 10:10 ` [PATCH 0/3] SAMA5D2 i2c bus recovery testing Ludovic Desroches
2019-12-16 10:26 ` Kamel Bouhara
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=20191205140305.1144788-1-kamel.bouhara@bootlin.com \
--to=kamel.bouhara@bootlin.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ludovic.desroches@microchip.com \
/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