From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Eduardo Valentin <eduval@amazon.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Haiyue Wang <haiyue.wang@linux.intel.com>,
jarkko.nikula@linux.intel.com, brendanhiggins@google.com,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] i2c: slave-mqueue: add a slave backend to receive and queue messages
Date: Tue, 4 Jun 2019 20:16:11 +0300 [thread overview]
Message-ID: <20190604171611.GS9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190531043347.4196-3-eduval@amazon.com>
On Thu, May 30, 2019 at 09:33:46PM -0700, Eduardo Valentin wrote:
> From: Haiyue Wang <haiyue.wang@linux.intel.com>
>
> Some protocols over I2C are designed for bi-directional transferring
> messages by using I2C Master Write protocol. Like the MCTP (Management
> Component Transport Protocol) and IPMB (Intelligent Platform Management
> Bus), they both require that the userspace can receive messages from
> I2C dirvers under slave mode.
>
> This new slave mqueue backend is used to receive and queue messages, it
> will exposes these messages to userspace by sysfs bin file.
>
> Note: DT interface and a couple of minor fixes here and there
> by Eduardo, so I kept the original authorship here.
> +#define MQ_MSGBUF_SIZE CONFIG_I2C_SLAVE_MQUEUE_MESSAGE_SIZE
> +#define MQ_QUEUE_SIZE CONFIG_I2C_SLAVE_MQUEUE_QUEUE_SIZE
> +#define MQ_QUEUE_NEXT(x) (((x) + 1) & (MQ_QUEUE_SIZE - 1))
Also possible ((x + 1) % ..._SIZE)
> + mq = dev_get_drvdata(container_of(kobj, struct device, kobj));
kobj_to_dev()
> +static int i2c_slave_mqueue_probe(struct i2c_client *client,
> + const struct i2c_device_id *id)
> +{
> + struct device *dev = &client->dev;
> + struct mq_queue *mq;
> + int ret, i;
> + void *buf;
> +
> + mq = devm_kzalloc(dev, sizeof(*mq), GFP_KERNEL);
> + if (!mq)
> + return -ENOMEM;
> +
> + BUILD_BUG_ON(!is_power_of_2(MQ_QUEUE_SIZE));
Perhaps start function with this kind of assertions?
> +
> + buf = devm_kmalloc_array(dev, MQ_QUEUE_SIZE, MQ_MSGBUF_SIZE,
> + GFP_KERNEL);
> + if (!buf)
> + return -ENOMEM;
> +
> + for (i = 0; i < MQ_QUEUE_SIZE; i++)
> + mq->queue[i].buf = buf + i * MQ_MSGBUF_SIZE;
Just wondering if kfifo API can bring an advantage here?
> + return 0;
> +}
> +static const struct of_device_id i2c_slave_mqueue_of_match[] = {
> + {
> + .compatible = "i2c-slave-mqueue",
> + },
> + { },
No need for comma here.
> +};
> +
> +static struct i2c_driver i2c_slave_mqueue_driver = {
> + .driver = {
> + .name = "i2c-slave-mqueue",
> + .of_match_table = of_match_ptr(i2c_slave_mqueue_of_match),
Wouldn't compiler warn you due to unused data?
Perhaps drop of_match_ptr() for good...
> + },
> + .probe = i2c_slave_mqueue_probe,
> + .remove = i2c_slave_mqueue_remove,
> + .id_table = i2c_slave_mqueue_id,
> +};
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-06-04 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 4:33 [PATCH 0/3] introduce i2c-slave-mqueue Eduardo Valentin
2019-05-31 4:33 ` [PATCH 1/3] dt-bindings: i2c: document bindings for i2c-slave-mqueue Eduardo Valentin
2019-05-31 4:33 ` [PATCH 2/3] i2c: slave-mqueue: add a slave backend to receive and queue messages Eduardo Valentin
2019-06-04 17:16 ` Andy Shevchenko [this message]
2019-06-05 3:27 ` Eduardo Valentin
2019-06-05 8:25 ` Andy Shevchenko
2019-06-05 14:31 ` Eduardo Valentin
2019-06-05 15:20 ` Andy Shevchenko
2019-06-05 15:31 ` Eduardo Valentin
2019-06-05 15:58 ` Andy Shevchenko
2019-05-31 4:33 ` [PATCH 3/3] Documentation: ABI: Add i2c-slave-mqueue sysfs documentation Eduardo Valentin
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=20190604171611.GS9224@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=eduval@amazon.com \
--cc=haiyue.wang@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).