From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org, Alain Volmat <alain.volmat@st.com>
Subject: Re: [RFC PATCH] WIP: i2c: rcar: add HostNotify support
Date: Wed, 1 Jul 2020 14:16:33 +0200 [thread overview]
Message-ID: <20200701121633.GI2261@ninjato> (raw)
In-Reply-To: <20200701092731.GD2261@ninjato>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
> BTW I think the DTS additions don't look too bad? It is a grey area,
> though...
>
> &i2c3 {
> pinctrl-0 = <&i2c3_pins>;
> pinctrl-names = "i2c-pwr";
> +
> + enable-host-notify;
I got another idea. What about a boolean binding "smbus"?
This describes the bus as SMBus (and not I2C bus), so the additional
SMBus restrictions/requirements apply. HostNotify is required for SMBus,
so address 0x08 can't be used. Alert is optional, but still it uses a
reserved address. SMBus timeouts maybe can be handled through this as
well (there is the HWMON specific "smbus-timeout-disable" so far).
So, we have one simple binding for HostNotify and Alert which really
describes the HW.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-01 12:16 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 [this message]
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
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=20200701121633.GI2261@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alain.volmat@st.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).