public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.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 v7 4/8] i2c: amd-asf: Add ACPI support for AMD ASF Controller
Date: Mon, 23 Sep 2024 14:31:46 +0530	[thread overview]
Message-ID: <8b175ba3-ceec-4ced-a1e0-620fb800752b@amd.com> (raw)
In-Reply-To: <ZvEqZF7Ijn7XUAQL@smile.fi.intel.com>



On 9/23/2024 14:14, Andy Shevchenko wrote:
> On Mon, Sep 23, 2024 at 01:33:57PM +0530, Shyam Sundar S K wrote:
>> The AMD ASF controller is presented to the operating system as an ACPI
>> device. The AMD ASF driver can use ACPI to obtain information about the
>> ASF controller's attributes, such as the ASF address space and interrupt
>> number, and to handle ASF interrupts.
>>
>> Currently, the piix4 driver assumes that a specific port address is
>> designated for AUX operations. However, with the introduction of ASF, the
>> same port address may also be used by the ASF controller. Therefore, a
>> check needs to be added to ensure that if ASF is advertised and enabled in
>> ACPI, the AUX port should not be configured.
> 
> ...
> 
>> +static int amd_asf_probe(struct platform_device *pdev)
>> +{
>> +	struct device *dev = &pdev->dev;
>> +	struct amd_asf_dev *asf_dev;
>> +
>> +	asf_dev = devm_kzalloc(dev, sizeof(*asf_dev), GFP_KERNEL);
>> +	if (!asf_dev)
>> +		return dev_err_probe(dev, -ENOMEM, "Failed to allocate memory\n");
>> +
>> +	asf_dev->mmio_cfg.use_mmio = true;
>> +	asf_dev->port_addr = platform_get_resource(pdev, IORESOURCE_IO, 0);
>> +	if (!asf_dev->port_addr)
>> +		return dev_err_probe(dev, -EINVAL, "missing IO resources\n");
>> +
>> +	asf_dev->adap.owner = THIS_MODULE;
> 
>> +	asf_dev->adap.dev.parent = &pdev->dev;
> 
> Now can also be
> 
> 	asf_dev->adap.dev.parent = dev;
> 
> (no need to resend for this only thing, perhaps Andi can amend whilst applying).
> 

OK. Thank you for all the valuable feedback and time in reviewing this
series.

Hi Andi,

Please let me if the series needs a respin if the amend fails for you.

Thanks,
Shyam

>> +	i2c_set_adapdata(&asf_dev->adap, asf_dev);
>> +	snprintf(asf_dev->adap.name, sizeof(asf_dev->adap.name), "AMD ASF adapter");
>> +
>> +	return devm_i2c_add_adapter(dev, &asf_dev->adap);
>> +}
> 

  reply	other threads:[~2024-09-23  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23  8:03 [PATCH v7 0/8] Introduce initial AMD ASF Controller driver support Shyam Sundar S K
2024-09-23  8:03 ` [PATCH v7 1/8] i2c: piix4: Change the parameter list of piix4_transaction function Shyam Sundar S K
2024-09-23  8:03 ` [PATCH v7 2/8] i2c: piix4: Move i2c_piix4 macros and structures to common header Shyam Sundar S K
2024-09-23  8:03 ` [PATCH v7 3/8] i2c: piix4: Export i2c_piix4 driver functions as library Shyam Sundar S K
2024-09-23  8:03 ` [PATCH v7 4/8] i2c: amd-asf: Add ACPI support for AMD ASF Controller Shyam Sundar S K
2024-09-23  8:44   ` Andy Shevchenko
2024-09-23  9:01     ` Shyam Sundar S K [this message]
2024-09-23 21:24       ` Andi Shyti
2024-09-23  8:03 ` [PATCH v7 5/8] i2c: amd-asf: Add i2c_algorithm operations to support AMD ASF with SMBus Shyam Sundar S K
2024-09-23  8:03 ` [PATCH v7 6/8] i2c: amd-asf: Add routine to handle the ASF slave process Shyam Sundar S K
2024-09-23  8:04 ` [PATCH v7 7/8] i2c: amd-asf: Clear remote IRR bit to get successive interrupt Shyam Sundar S K
2024-09-23  8:04 ` [PATCH v7 8/8] MAINTAINERS: Add AMD ASF driver entry Shyam Sundar S K
2024-09-25  7:57   ` Andi Shyti
2024-09-25 10:17 ` [PATCH v7 0/8] Introduce initial AMD ASF Controller driver support Andi Shyti

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=8b175ba3-ceec-4ced-a1e0-620fb800752b@amd.com \
    --to=shyam-sundar.s-k@amd.com \
    --cc=Patil.Reddy@amd.com \
    --cc=Sanket.Goswami@amd.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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