From: Geert Uytterhoeven <geert@linux-m68k.org>
To: uli+renesas@fpond.eu
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 0/3] I2C0/3/5 pin control for H3 and M3-W
Date: Mon, 27 Aug 2018 17:15:55 +0200 [thread overview]
Message-ID: <CAMuHMdX4etTkVn=wt8CKES_=3E2f-hQ6WK1EaUTK3CUETLtuFw@mail.gmail.com> (raw)
In-Reply-To: <1534511921-19470-1-git-send-email-uli+renesas@fpond.eu>
Hi Uli,
On Fri, Aug 17, 2018 at 3:19 PM Ulrich Hecht <uli+renesas@fpond.eu> wrote:
> This is an up-port from the BSP. Unfortunately I could not test these
> because none of those pins seem to be accessible on Salvator boards (not on
> ULCB either, AFAICT), so the best thing I can say is that they don't seem to
> break anything.
For Salvator-X(S):
1. If you set SW5 and SW6 to their center positions, you can access I2C3 on
EXIO Connector D.
2. I2C5 is available on test points CP45/46.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2018-08-27 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 13:18 [PATCH 0/3] I2C0/3/5 pin control for H3 and M3-W Ulrich Hecht
2018-08-17 13:18 ` [PATCH 1/3] pinctrl: sh-pfc: r8a7795: Add I2C{0,3,5} pins, groups and functions Ulrich Hecht
2018-08-28 8:12 ` Geert Uytterhoeven
2018-08-17 13:18 ` [PATCH 2/3] pinctrl: sh-pfc: r8a7795-es1: " Ulrich Hecht
2018-08-17 13:18 ` [PATCH 3/3] pinctrl: sh-pfc: r8a7796: " Ulrich Hecht
2018-08-27 15:15 ` Geert Uytterhoeven [this message]
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='CAMuHMdX4etTkVn=wt8CKES_=3E2f-hQ6WK1EaUTK3CUETLtuFw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=uli+renesas@fpond.eu \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).