From: Eddie James <eajames@linux.ibm.com>
To: linux-fsi@lists.ozlabs.org
Cc: rostedt@goodmis.org, linux-trace-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mhiramat@kernel.org, alistair@popple.id.au, joel@jms.id.au,
jk@ozlabs.org, andrew@aj.id.au, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, eajames@linux.ibm.com
Subject: [PATCH v5 0/6] fsi: Add IBM I2C Responder virtual FSI master
Date: Tue, 21 Feb 2023 15:26:16 -0600 [thread overview]
Message-ID: <20230221212622.3897097-1-eajames@linux.ibm.com> (raw)
The I2C Responder (I2CR) is an I2C device that translates I2C commands
to CFAM or SCOM operations, effectively implementing an FSI master and
bus.
Changes since v4:
- Add I2CR scom driver and associated patches
- Use compatible strings for FSI drivers if specified
- Include aliased device numbering patch
- Restructure the trace events to eliminate holes
Changes since v3:
- Rework the endian-ness in i2cr_write
- Rework the tracing to include the i2c bus and device address
Changes since v2:
- Fix the bindings again, sorry for the spam
Changes since v1:
- Fix the binding document
- Change the binding name
- Clean up the size argument checking
- Reduce __force by using packed struct for the command
Eddie James (6):
fsi: Move fsi_slave structure definition to header
dt-bindings: fsi: Document the IBM I2C Responder virtual FSI master
fsi: Add IBM I2C Responder virtual FSI master
fsi: Add I2C Responder SCOM driver
fsi: Add aliased device numbering
fsi: Use of_match_table for bus matching if specified
.../bindings/fsi/ibm,i2cr-fsi-master.yaml | 41 ++++
drivers/fsi/Kconfig | 21 ++
drivers/fsi/Makefile | 2 +
drivers/fsi/fsi-core.c | 60 +++--
drivers/fsi/fsi-master-aspeed.c | 2 +-
drivers/fsi/fsi-master-ast-cf.c | 2 +-
drivers/fsi/fsi-master-gpio.c | 2 +-
drivers/fsi/fsi-master-hub.c | 2 +-
drivers/fsi/fsi-master-i2cr.c | 228 ++++++++++++++++++
drivers/fsi/fsi-master-i2cr.h | 24 ++
drivers/fsi/fsi-master.h | 3 +-
drivers/fsi/fsi-scom.c | 8 +
drivers/fsi/fsi-slave.h | 28 +++
drivers/fsi/i2cr-scom.c | 158 ++++++++++++
include/trace/events/fsi_master_i2cr.h | 109 +++++++++
15 files changed, 663 insertions(+), 27 deletions(-)
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,i2cr-fsi-master.yaml
create mode 100644 drivers/fsi/fsi-master-i2cr.c
create mode 100644 drivers/fsi/fsi-master-i2cr.h
create mode 100644 drivers/fsi/fsi-slave.h
create mode 100644 drivers/fsi/i2cr-scom.c
create mode 100644 include/trace/events/fsi_master_i2cr.h
--
2.31.1
next reply other threads:[~2023-02-21 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:26 Eddie James [this message]
2023-02-21 21:26 ` [PATCH v5 1/6] fsi: Move fsi_slave structure definition to header Eddie James
2023-02-21 21:26 ` [PATCH v5 2/6] dt-bindings: fsi: Document the IBM I2C Responder virtual FSI master Eddie James
2023-02-21 21:26 ` [PATCH v5 3/6] fsi: Add " Eddie James
2023-02-21 21:26 ` [PATCH v5 4/6] fsi: Add I2C Responder SCOM driver Eddie James
2023-02-22 15:37 ` kernel test robot
2023-02-21 21:26 ` [PATCH v5 5/6] fsi: Add aliased device numbering Eddie James
2023-02-21 21:26 ` [PATCH v5 6/6] fsi: Use of_match_table for bus matching if specified Eddie James
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=20230221212622.3897097-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.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.