From: Wolfram Sang <wsa@the-dreams.de>
To: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
Cc: Rob Herring <robh@kernel.org>,
Eduardo Valentin <eduval@amazon.com>,
jarkko.nikula@linux.intel.com, andriy.shevchenko@intel.com,
brendanhiggins@google.com, Mark Rutland <mark.rutland@arm.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv7 1/3] dt-bindings: i2c: document bindings for i2c-slave-mqueue
Date: Mon, 1 Jul 2019 14:42:18 +0200 [thread overview]
Message-ID: <20190701124218.GA4399@kunai> (raw)
In-Reply-To: <b3e5ac5c-baf7-bc8a-701a-4af3b8983155@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
> Looks like the slave reg missed the key value bit:
>
>
> https://elinux.org/images/f/f6/ELCE15-WolframSang-ShinyNewI2CSlaveFramework.pdf
>
> Example: reg = <(I2C_OWN_SLAVE_ADDRESS | 0x42)>;
Yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-01 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190605164651.15991-1-eduval@amazon.com>
2019-06-05 16:46 ` [PATCHv7 1/3] dt-bindings: i2c: document bindings for i2c-slave-mqueue Eduardo Valentin
2019-06-05 16:46 ` Eduardo Valentin
2019-06-11 23:14 ` Rob Herring
2019-06-12 2:46 ` Wang, Haiyue
2019-07-01 12:42 ` Wolfram Sang [this message]
2019-07-01 12:43 ` Wolfram Sang
2019-06-05 16:46 ` [PATCHv7 2/3] i2c: slave-mqueue: add a slave backend to receive and queue messages Eduardo Valentin
2019-06-05 16:46 ` Eduardo Valentin
2019-06-05 17:02 ` Andy Shevchenko
2019-06-05 17:28 ` Eduardo Valentin
2019-07-01 12:56 ` Wolfram Sang
2019-06-05 16:46 ` [PATCHv7 3/3] Documentation: ABI: Add i2c-slave-mqueue sysfs documentation Eduardo Valentin
2019-06-05 16:46 ` Eduardo Valentin
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=20190701124218.GA4399@kunai \
--to=wsa@the-dreams.de \
--cc=andriy.shevchenko@intel.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=eduval@amazon.com \
--cc=haiyue.wang@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.