From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, Sanket.Goswami@amd.com,
Patil.Reddy@amd.com
Subject: Re: [PATCH v6 6/8] i2c: amd-asf: Add routine to handle the ASF slave process
Date: Fri, 20 Sep 2024 20:57:56 +0300 [thread overview]
Message-ID: <Zu23pEI5tDRU5BZo@smile.fi.intel.com> (raw)
In-Reply-To: <20240919175913.1895670-7-Shyam-sundar.S-k@amd.com>
On Thu, Sep 19, 2024 at 11:29:11PM +0530, Shyam Sundar S K wrote:
> Add support for handling ASF slave process events as described in the AMD
> ASF databook. This involves implementing the correct programming sequence
> to manage each ASF packet appropriately.
...
> +static void amd_asf_process_target(struct work_struct *work)
> +{
> + struct amd_asf_dev *dev = container_of(work, struct amd_asf_dev, work_buf.work);
> + unsigned short piix4_smba = dev->port_addr->start;
> + u8 data[ASF_BLOCK_MAX_BYTES];
> + u8 bank, reg, cmd;
> + u8 len, idx, val;
> +
> + /* Read target status register */
> + reg = inb_p(ASFSLVSTA);
> +
> + /* Check if no error bits are set in target status register */
> + if (reg & ASF_ERROR_STATUS) {
> + /* Set bank as full */
> + cmd = 0;
> + reg = reg | GENMASK(3, 2);
reg |= ...
> + outb_p(reg, ASFDATABNKSEL);
> + } else {
> + /* Read data bank */
> + reg = inb_p(ASFDATABNKSEL);
> + bank = (reg & BIT(3)) ? 1 : 0;
> + /* Set read data bank */
> + if (bank) {
> + reg = reg | BIT(4);
> + reg = reg & ~BIT(3);
> + } else {
> + reg = reg & ~BIT(4);
> + reg = reg & ~BIT(2);
> + }
/* Set read data bank */
if (bank) {
reg |= BIT(4);
reg &= ~BIT(3);
} else {
reg &= ~BIT(4);
reg &= ~BIT(2);
}
> + /* Read command register */
> + outb_p(reg, ASFDATABNKSEL);
> + cmd = inb_p(ASFINDEX);
> + len = inb_p(ASFDATARWPTR);
> + for (idx = 0; idx < len; idx++)
> + data[idx] = inb_p(ASFINDEX);
> + /* Clear data bank status */
> + if (bank) {
> + reg = reg | BIT(3);
> + outb_p(reg, ASFDATABNKSEL);
> + } else {
> + reg = reg | BIT(2);
> + outb_p(reg, ASFDATABNKSEL);
> + }
/* Clear data bank status */
if (bank) {
reg |= BIT(3);
outb_p(reg, ASFDATABNKSEL);
} else {
reg |= BIT(2);
outb_p(reg, ASFDATABNKSEL);
}
> + }
> +
> + outb_p(0, ASFSETDATARDPTR);
> + if (cmd & BIT(0))
> + return;
> +
> + /*
> + * Although i2c_slave_event() returns an appropriate error code, we
> + * don't check it here because we're operating in the workqueue context.
> + */
> + i2c_slave_event(dev->target, I2C_SLAVE_WRITE_REQUESTED, &val);
> + for (idx = 0; idx < len; idx++) {
> + val = data[idx];
> + i2c_slave_event(dev->target, I2C_SLAVE_WRITE_RECEIVED, &val);
> + }
> + i2c_slave_event(dev->target, I2C_SLAVE_STOP, &val);
> +}
...
Perhaps it's time to have
struct device *dev = &pdev->dev;
> + ret = devm_delayed_work_autocancel(&pdev->dev, &asf_dev->work_buf, amd_asf_process_target);
> + if (ret)
> + return dev_err_probe(&pdev->dev, ret, "failed to create work queue\n");
...and this, in particular, becomes shorter.
ret = devm_delayed_work_autocancel(dev, &asf_dev->work_buf, amd_asf_process_target);
if (ret)
return dev_err_probe(dev, ret, "failed to create work queue\n");
> + irq = platform_get_irq(pdev, 0);
> + if (irq < 0)
> + return dev_err_probe(&pdev->dev, irq, "missing IRQ resources\n");
> +
> + ret = devm_request_irq(&pdev->dev, irq, amd_asf_irq_handler, IRQF_SHARED,
> + "amd_asf", asf_dev);
This even can be one line after proposed change.
> + if (ret)
> + return dev_err_probe(&pdev->dev, ret, "Unable to request irq: %d for use\n", irq);
...
With the above changes being applied
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-20 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 17:59 [PATCH v6 0/8] Introduce initial AMD ASF Controller driver support Shyam Sundar S K
2024-09-19 17:59 ` [PATCH v6 1/8] i2c: piix4: Change the parameter list of piix4_transaction function Shyam Sundar S K
2024-09-19 17:59 ` [PATCH v6 2/8] i2c: piix4: Move i2c_piix4 macros and structures to common header Shyam Sundar S K
2024-09-19 19:51 ` Andy Shevchenko
2024-09-19 17:59 ` [PATCH v6 3/8] i2c: piix4: Export i2c_piix4 driver functions as library Shyam Sundar S K
2024-09-20 16:24 ` Andy Shevchenko
2024-09-19 17:59 ` [PATCH v6 4/8] i2c: amd-asf: Add ACPI support for AMD ASF Controller Shyam Sundar S K
2024-09-20 16:27 ` Andy Shevchenko
2024-09-19 17:59 ` [PATCH v6 5/8] i2c: amd-asf: Add i2c_algorithm operations to support AMD ASF with SMBus Shyam Sundar S K
2024-09-20 17:39 ` Andy Shevchenko
2024-09-19 17:59 ` [PATCH v6 6/8] i2c: amd-asf: Add routine to handle the ASF slave process Shyam Sundar S K
2024-09-20 17:57 ` Andy Shevchenko [this message]
2024-09-19 17:59 ` [PATCH v6 7/8] i2c: amd-asf: Clear remote IRR bit to get successive interrupt Shyam Sundar S K
2024-09-20 17:59 ` Andy Shevchenko
2024-09-19 17:59 ` [PATCH v6 8/8] MAINTAINERS: Add AMD ASF driver entry Shyam Sundar S K
2024-09-20 15:06 ` Andy Shevchenko
2024-09-23 7:31 ` Shyam Sundar S K
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=Zu23pEI5tDRU5BZo@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Patil.Reddy@amd.com \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.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