From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC PATCH] WIP: i2c: rcar: add HostNotify support
Date: Wed, 1 Jul 2020 16:00:33 +0200 [thread overview]
Message-ID: <20200701140033.GK2261@ninjato> (raw)
In-Reply-To: <20200701134619.GD3457@gnbcxd0016.gnb.st.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
> Well yes and no (for my case). I am NOT relying on GPIO for the SMBus Alert,
> this is handled by the I2C controller itself via a dedicated input into the
> controller. However, the pin itself can still be shared with other IPs,
I see.
> depending on how the DT is configured. Just usual pinmux stuff. So I was
> just mentioning that the pinctrl should also be correct to properly configure
> the pinmuxing for that SMBus Alert input signal as well.
Well, yes, the DT needs to be correct :) Same for pinmuxing SCL and SDA,
right?
> Sorry, this is just making the story more confusing for something which in
> fact wasn't important in the first place probably. There is no real issue
> here.
No worries. It is better than to miss something.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-01 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:09 [RFC PATCH] WIP: i2c: rcar: add HostNotify support Wolfram Sang
2020-07-01 9:27 ` Wolfram Sang
2020-07-01 12:16 ` Wolfram Sang
2020-07-01 12:32 ` Alain Volmat
2020-07-01 13:21 ` Wolfram Sang
2020-07-01 13:46 ` Alain Volmat
2020-07-01 14:00 ` Wolfram Sang [this message]
2020-07-01 14:37 ` Alain Volmat
2020-07-01 14:57 ` Wolfram Sang
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=20200701140033.GK2261@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).