From: Eddie James <eajames@linux.ibm.com>
To: Andrew Jeffery <andrew@aj.id.au>, linux-fsi@lists.ozlabs.org
Cc: devicetree@vger.kernel.org,
Alistair Popple <alistair@popple.id.au>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: fsi: Document the IBM I2C Responder virtual FSI master
Date: Wed, 25 Jan 2023 15:35:32 -0600 [thread overview]
Message-ID: <2fd38f3d-e26b-6888-10b7-8da06f94bfac@linux.ibm.com> (raw)
In-Reply-To: <a8be2b47-b0e9-4a28-8c32-81b9af81299e@app.fastmail.com>
On 1/19/23 18:22, Andrew Jeffery wrote:
>
> On Fri, 20 Jan 2023, at 04:17, Eddie James wrote:
>> The I2C Responder translates I2C commands to CFAM or SCOM operations,
>> effectively implementing an FSI master.
>>
>> Signed-off-by: Eddie James <eajames@linux.ibm.com>
>> ---
>> .../devicetree/bindings/fsi/ibm,i2cr.yaml | 42 +++++++++++++++++++
>> 1 file changed, 42 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml
>> b/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml
>> new file mode 100644
>> index 000000000000..929ca10988f9
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml
>> @@ -0,0 +1,42 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/fsi/ibm,i2cr.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: IBM I2C Responder virtual FSI master
>> +
>> +maintainers:
>> + - Eddie James <eajames@linux.ibm.com>
>> +
>> +description: |
>> + This binding describes an I2C device called the I2C Responder
>> (I2CR). The
>> + I2CR translates commands sent over I2C bus to FSI CFAM reads and
>> writes or
>> + SCOM operations. The CFAM access means that the I2CR can act as an
>> FSI
>> + master.
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - ibm,i2cr
>
> I think this should be a bit more descriptive and at least mention that
> it's FSI-related, e.g. `ibm,fsi-i2cr`? Thoughts?
Yea that probably makes sense.
Thanks for the suggestion!
Eddie
>
>> +
>> + reg:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + i2cr@20 {
>> + compatible = "ibm,i2cr";
> Change this in accordance with the above.
>
> Andrew
next prev parent reply other threads:[~2023-01-25 21:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:47 [PATCH 0/2] fsi: Add IBM I2C Responder virtual FSI master Eddie James
2023-01-19 17:47 ` [PATCH 1/2] dt-bindings: fsi: Document the " Eddie James
2023-01-20 0:22 ` Andrew Jeffery
2023-01-25 21:35 ` Eddie James [this message]
2023-01-20 1:42 ` Rob Herring
2023-01-20 8:16 ` Krzysztof Kozlowski
2023-01-19 17:47 ` [PATCH 2/2] fsi: Add " Eddie James
2023-01-20 1:09 ` Andrew Jeffery
2023-01-25 22:36 ` Eddie James
2023-01-20 10:41 ` kernel test robot
2023-01-20 23:34 ` kernel test robot
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=2fd38f3d-e26b-6888-10b7-8da06f94bfac@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).