From: Qiang Zhang <qiang4.zhang@linux.intel.com>
To: Harald Mommer <Harald.Mommer@opensynergy.com>
Cc: virtio-dev@lists.oasis-open.org,
Haixu Cui <quic_haixcui@quicinc.com>,
Mark Brown <broonie@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_ztu@quicinc.com, Matti Moell <Matti.Moell@opensynergy.com>,
Mikhail Golubev <Mikhail.Golubev@opensynergy.com>
Subject: Re: [PATCH v3 3/3] virtio-spi: Add virtio SPI driver.
Date: Mon, 9 Sep 2024 20:59:38 +0800 [thread overview]
Message-ID: <Zt7xEzOaanKiXLbq@dev-qz> (raw)
In-Reply-To: <20240326112812.31739-4-Harald.Mommer@opensynergy.com>
Hi, Harald
On Tue, Mar 26, 2024 at 12:28:12PM +0100, Harald Mommer wrote:
> From: Harald Mommer <harald.mommer@opensynergy.com>
>
> This is the virtio SPI Linux kernel driver.
>
> Signed-off-by: Harald Mommer <Harald.Mommer@opensynergy.com>
[...]
> +static int virtio_spi_probe(struct virtio_device *vdev)
> +{
> + struct device_node *np = vdev->dev.parent->of_node;
> + struct virtio_spi_priv *priv;
> + struct spi_controller *ctrl;
> + int err;
> + u32 bus_num;
> + u16 csi;
> +
> + ctrl = devm_spi_alloc_host(&vdev->dev, sizeof(*priv));
> + if (!ctrl)
> + return -ENOMEM;
> +
> + priv = spi_controller_get_devdata(ctrl);
> + priv->vdev = vdev;
> + vdev->priv = priv;
> + ctrl->dev.of_node = vdev->dev.of_node;
To support ACPI, ACPI node of the controller needs to be set:
/*
* Setup ACPI node for controlled devices which will be probed through
* ACPI.
*/
ACPI_COMPANION_SET(&vdev->dev, ACPI_COMPANION(vdev->dev.parent));
> + dev_set_drvdata(&vdev->dev, ctrl);
> +
> + init_completion(&priv->spi_req.completion);
> +
> + err = of_property_read_u32(np, "spi,bus-num", &bus_num);
> + if (!err && bus_num <= S16_MAX)
> + ctrl->bus_num = (s16)bus_num;
This is not the right way to fix bus number. You can use OF alias.
Also, to work with ACPI, we should use common API like
device_property_read_u32.
> +
> + virtio_spi_read_config(vdev);
> +
> + ctrl->transfer_one = virtio_spi_transfer_one;
> +
> + err = virtio_spi_find_vqs(priv);
> + if (err) {
> + dev_err(&vdev->dev, "Cannot setup virtqueues\n");
> + return err;
> + }
> +
> + board_info.max_speed_hz = priv->max_freq_hz;
> + board_info.bus_num = (u16)ctrl->bus_num;
> +
> + if (!(priv->mode_func_supported & VIRTIO_SPI_CS_HIGH))
> + board_info.mode = SPI_MODE_0;
> + else
> + board_info.mode = SPI_MODE_0 | SPI_CS_HIGH;
> +
> + err = spi_register_controller(ctrl);
> + if (err) {
> + dev_err(&vdev->dev, "Cannot register controller\n");
> + goto err_return;
> + }
> +
> + if (vdev->dev.of_node) {
> + dev_dbg(&vdev->dev, "Final setup triggered by DT child node\n");
> + return 0;
> + }
How about ACPI path?
> +
> + /* Add chip selects to controller */
> + for (csi = 0; csi < ctrl->num_chipselect; csi++) {
> + dev_dbg(&vdev->dev, "Setting up CS=%u\n", csi);
> + board_info.chip_select = csi;
> +
> + if (!spi_new_device(ctrl, &board_info)) {
> + dev_err(&vdev->dev, "Cannot setup device %u\n", csi);
> + spi_unregister_controller(ctrl);
> + err = -ENODEV;
> + goto err_return;
> + }
> + }
Just enumerate SPI devices via DT/ACPI. And a fixed SPI modalias "spi-virtio"
is no better than match method from DT/ACPI.
Thanks,
Qiang
next prev parent reply other threads:[~2024-09-09 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 11:28 [PATCH v3 0/3] Virtio SPI Linux driver Harald Mommer
2024-03-26 11:28 ` [PATCH v3 1/3] virtio: Add ID for virtio SPI Harald Mommer
2024-08-27 17:15 ` Alex Bennée
2024-03-26 11:28 ` [PATCH v3 2/3] virtio-spi: Add virtio-spi.h Harald Mommer
2024-08-27 17:18 ` Alex Bennée
2024-03-26 11:28 ` [PATCH v3 3/3] virtio-spi: Add virtio SPI driver Harald Mommer
2024-09-09 12:59 ` Qiang Zhang [this message]
2024-12-23 7:34 ` Haixu Cui
2024-12-23 7:42 ` Qiang Zhang
2024-12-23 11:00 ` Hillf Danton
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=Zt7xEzOaanKiXLbq@dev-qz \
--to=qiang4.zhang@linux.intel.com \
--cc=Harald.Mommer@opensynergy.com \
--cc=Matti.Moell@opensynergy.com \
--cc=Mikhail.Golubev@opensynergy.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_haixcui@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.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.