From: Frank Li <Frank.li@nxp.com>
To: alexandre.belloni@bootlin.com, conor.culhane@silvaco.com,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
imx@lists.linux.dev, jirislaby@kernel.org, joe@perches.com,
krzysztof.kozlowski+dt@linaro.org,
krzysztof.kozlowski@linaro.org, linux-i3c@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
miquel.raynal@bootlin.com, robh@kernel.org,
zbigniew.lukwinski@linux.intel.com
Subject: Re: [PATCH v3 0/8] I3C target mode support
Date: Tue, 23 Jan 2024 18:12:08 -0500 [thread overview]
Message-ID: <ZbBHyJALhEn8UU9R@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20240123212549.3858137-1-Frank.Li@nxp.com>
On Tue, Jan 23, 2024 at 04:25:41PM -0500, Frank Li wrote:
> This patch introduces support for I3C target mode, which is referenced
Please forget v3 and check v4.
Frank
> with a PCIe Endpoint system. It also establishes a configuration framework
> (configfs) for the I3C target controller driver and the I3C target function
> driver
>
> Typic usage as
>
> The user can configure the i3c-target-tty device using configfs entry. In
> order to change the vendorid, the following commands can be used
>
> # echo 0x011b > functions/tty/func1/vendor_id
> # echo 0x1000 > functions/tty/func1/part_id
> # echo 0x6 > functions/tty/t/bcr
>
> Binding i3c-target-tty Device to target Controller
> ------------------------------------------------
>
> In order for the target function device to be useful, it has to be bound to
> a I3C target controller driver. Use the configfs to bind the function
> device to one of the controller driver present in the system::
>
> # ln -s functions/pci_epf_test/func1 controllers/44330000.i3c-target/
>
> Host side:
> cat /dev/ttyI3C0
> Taret side:
> echo abc >/dev/ttyI3C0
>
> Chagne from v2 to v3
> - using 'mode' distingiush master and target.
> - move svc-i3c-target.c to under master,
> - built together with svc-i3c-master.c
>
> Change from v1 to v2
> - change "slave" to "target"
> - include master side tty patch
> - fixed dtbcheck problem
> - fixed kerne-doc check warning
>
> Some review comment may be lost since it is quite long time since v1. Now
> master side dependent patches already in linux-next. So sent target side
> patches with tty support again.
>
> No sure why an additional "\r\n" appended.
>
> Frank Li (8):
> i3c: add target mode support
> dt-bindings: i3c: svc: add proptery mode
> Documentation: i3c: Add I3C target mode controller and function
> i3c: svc: Add svc-i3c-main.c and svc-i3c.h
> i3c: target: add svc target controller support
> i3c: target: func: add tty driver
> i3c: add API i3c_dev_gettstatus_format1() to get target device status
> tty: i3c: add TTY over I3C master support
>
> .../bindings/i3c/silvaco,i3c-master.yaml | 11 +-
> Documentation/driver-api/i3c/index.rst | 1 +
> .../driver-api/i3c/target/i3c-target-cfs.rst | 109 +++
> .../driver-api/i3c/target/i3c-target.rst | 189 +++++
> .../driver-api/i3c/target/i3c-tty-howto.rst | 109 +++
> Documentation/driver-api/i3c/target/index.rst | 13 +
> drivers/i3c/Kconfig | 31 +-
> drivers/i3c/Makefile | 3 +
> drivers/i3c/device.c | 24 +
> drivers/i3c/func/Kconfig | 9 +
> drivers/i3c/func/Makefile | 3 +
> drivers/i3c/func/tty.c | 475 +++++++++++
> drivers/i3c/i3c-cfs.c | 389 +++++++++
> drivers/i3c/internals.h | 1 +
> drivers/i3c/master.c | 26 +
> drivers/i3c/master/Makefile | 3 +-
> drivers/i3c/master/svc-i3c-main.c | 79 ++
> drivers/i3c/master/svc-i3c-master.c | 34 +-
> drivers/i3c/master/svc-i3c-target.c | 776 ++++++++++++++++++
> drivers/i3c/master/svc-i3c.h | 14 +
> drivers/i3c/target.c | 453 ++++++++++
> drivers/tty/Kconfig | 13 +
> drivers/tty/Makefile | 1 +
> drivers/tty/i3c_tty.c | 426 ++++++++++
> include/linux/i3c/device.h | 1 +
> include/linux/i3c/target.h | 527 ++++++++++++
> 26 files changed, 3689 insertions(+), 31 deletions(-)
> create mode 100644 Documentation/driver-api/i3c/target/i3c-target-cfs.rst
> create mode 100644 Documentation/driver-api/i3c/target/i3c-target.rst
> create mode 100644 Documentation/driver-api/i3c/target/i3c-tty-howto.rst
> create mode 100644 Documentation/driver-api/i3c/target/index.rst
> create mode 100644 drivers/i3c/func/Kconfig
> create mode 100644 drivers/i3c/func/Makefile
> create mode 100644 drivers/i3c/func/tty.c
> create mode 100644 drivers/i3c/i3c-cfs.c
> create mode 100644 drivers/i3c/master/svc-i3c-main.c
> create mode 100644 drivers/i3c/master/svc-i3c-target.c
> create mode 100644 drivers/i3c/master/svc-i3c.h
> create mode 100644 drivers/i3c/target.c
> create mode 100644 drivers/tty/i3c_tty.c
> create mode 100644 include/linux/i3c/target.h
>
> --
> 2.34.1
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2024-01-23 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 21:25 [PATCH v3 0/8] I3C target mode support Frank Li
2024-01-23 21:25 ` [PATCH v3 1/8] i3c: add " Frank Li
2024-01-23 21:25 ` [PATCH v3 2/8] dt-bindings: i3c: svc: add proptery mode Frank Li
2024-01-23 22:38 ` Rob Herring
2024-01-23 21:25 ` [PATCH v3 3/8] Documentation: i3c: Add I3C target mode controller and function Frank Li
2024-01-23 21:25 ` [PATCH v3 4/8] i3c: svc: Add svc-i3c-main.c and svc-i3c.h Frank Li
2024-01-23 21:25 ` [PATCH v3 5/8] i3c: target: add svc target controller support Frank Li
2024-01-23 21:25 ` [PATCH v3 6/8] i3c: target: func: add tty driver Frank Li
2024-01-23 21:25 ` [PATCH v3 7/8] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2024-01-23 21:25 ` [PATCH v3 8/8] tty: i3c: add TTY over I3C master support Frank Li
2024-01-23 23:12 ` Frank Li [this message]
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=ZbBHyJALhEn8UU9R@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=zbigniew.lukwinski@linux.intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).