From: Jiri Slaby <jirislaby@kernel.org>
To: Frank Li <Frank.Li@nxp.com>,
miquel.raynal@bootlin.com, conor.culhane@silvaco.com,
alexandre.belloni@bootlin.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
corbet@lwn.net, joe@perches.com, linux-i3c@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: gregkh@linuxfoundation.org, imx@lists.linux.dev,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 4/5] i3c: slave: func: add tty driver
Date: Thu, 19 Oct 2023 09:21:38 +0200 [thread overview]
Message-ID: <83a0f0a0-56b1-4021-a37d-ef68e7fab712@kernel.org> (raw)
In-Reply-To: <20231018215809.3477437-5-Frank.Li@nxp.com>
On 18. 10. 23, 23:58, Frank Li wrote:
> Add tty over I3C slave function driver.
Many of the master review comments apply also here. Please fix here too.
More below.
> --- /dev/null
> +++ b/drivers/i3c/func/tty.c
> @@ -0,0 +1,548 @@
...
> +static void i3c_slave_tty_rx_complete(struct i3c_request *req)
> +{
> + struct ttyi3c_port *port = req->context;
> +
> + if (req->status == I3C_REQUEST_CANCEL) {
> + i3c_slave_ctrl_free_request(req);
> + return;
> + }
> +
> + for (int i = 0; i < req->actual; i++)
> + tty_insert_flip_char(&port->port, *(u8 *)(req->buf + i), 0);
Maybe I miss something obvious, but req->buf is void *. So why not
simple tty_insert_flip_string()?
> + sport->buffer = (void *)get_zeroed_page(GFP_KERNEL);
> + if (!sport->buffer)
> + return -ENOMEM;
> +
> + sport->xmit.buf = (void *)get_zeroed_page(GFP_KERNEL);
tty_port_alloc_xmit_buf()
> +static int i3c_tty_probe(struct i3c_slave_func *func)
> +{
> + struct device *dev = &func->dev;
> + struct ttyi3c_port *port;
> +
> + port = devm_kzalloc(dev, sizeof(*port), GFP_KERNEL);
> + if (!port)
> + return -ENOMEM;
> +
> + port->i3cdev = func;
> + dev_set_drvdata(&func->dev, port);
> +
> + port->workqueue = alloc_workqueue("%s", 0, 0, dev_name(&func->dev));
Another wq? You'd have to have a strong reason for these. Drop that.
> + if (!port->workqueue)
> + return -ENOMEM;
> +
> + INIT_WORK(&port->work, i3c_slave_tty_i3c_work);
> +
> + return 0;
> +}
> +
> +static void i3c_tty_remove(struct i3c_slave_func *func)
> +{
> + struct ttyi3c_port *port;
> +
> + port = dev_get_drvdata(&func->dev);
That can be on one line.
> +
> + destroy_workqueue(port->workqueue);
> +}
> +static int i3c_open(struct tty_struct *tty, struct file *filp)
> +{
> + struct ttyi3c_port *sport = tty->driver_data;
> + int ret;
> +
> + if (!i3c_slave_ctrl_get_addr(sport->i3cdev->ctrl)) {
> + dev_info(&sport->i3cdev->dev, "No slave addr assigned, try hotjoin");
Should this be a debug print instead?
> + ret = i3c_slave_ctrl_hotjoin(sport->i3cdev->ctrl);
> + if (ret) {
> + dev_err(&sport->i3cdev->dev, "Hotjoin failure, check connection");
> + return ret;
> + }
> + }
> +
> + return tty_port_open(&sport->port, tty, filp);
regards,
--
js
suse labs
next prev parent reply other threads:[~2023-10-19 7:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 21:58 [PATCH 0/5] I3C slave mode support Frank Li
2023-10-18 21:58 ` [PATCH 1/5] i3c: add " Frank Li
2023-10-19 7:00 ` Krzysztof Kozlowski
2023-10-19 15:02 ` Frank Li
2023-10-19 15:46 ` Greg KH
2023-10-19 17:06 ` Greg KH
2023-10-23 1:11 ` kernel test robot
2023-10-23 1:20 ` kernel test robot
2023-10-18 21:58 ` [PATCH 2/5] dt-bindings: i3c: svc: add compatible string i3c: silvaco,i3c-slave Frank Li
2023-10-19 7:00 ` Krzysztof Kozlowski
2023-10-19 12:07 ` Rob Herring
2023-10-18 21:58 ` [PATCH 3/5] i3c: slave: add svc slave controller support Frank Li
2023-10-23 1:29 ` kernel test robot
2023-10-18 21:58 ` [PATCH 4/5] i3c: slave: func: add tty driver Frank Li
2023-10-19 7:21 ` Jiri Slaby [this message]
2023-10-18 21:58 ` [PATCH 5/5] Documentation: i3c: Add I3C slave mode controller and function Frank Li
2023-10-18 22:07 ` Frank Li
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=83a0f0a0-56b1-4021-a37d-ef68e7fab712@kernel.org \
--to=jirislaby@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=conor.culhane@silvaco.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.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+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).