From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
jsd@semihalf.com, linux-i2c@vger.kernel.org,
Rajesh1.Kumar@amd.com, Sanath S <Sanath.S@amd.com>
Subject: Re: [PATCH] i2c: designware-pci: Add new PCI IDs for AMD NAVI GPU
Date: Mon, 2 Jan 2023 19:29:29 +0200 [thread overview]
Message-ID: <Y7MUeRqYJ6peB3eh@smile.fi.intel.com> (raw)
In-Reply-To: <20230102170955.1750734-1-Basavaraj.Natikar@amd.com>
On Mon, Jan 02, 2023 at 10:39:55PM +0530, Basavaraj Natikar wrote:
> Add additional supported PCI IDs for latest AMD NAVI GPU card which
> has an integrated Type-C controller and designware I2C with PCI
> interface.
Obviously looks correct from the code and style perspectives.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> Tested-by: Sanath S <Sanath.S@amd.com>
> ---
> drivers/i2c/busses/i2c-designware-pcidrv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-pcidrv.c b/drivers/i2c/busses/i2c-designware-pcidrv.c
> index e499f96506c5..782fe1ef3ca1 100644
> --- a/drivers/i2c/busses/i2c-designware-pcidrv.c
> +++ b/drivers/i2c/busses/i2c-designware-pcidrv.c
> @@ -396,6 +396,8 @@ static const struct pci_device_id i2_designware_pci_ids[] = {
> { PCI_VDEVICE(ATI, 0x73a4), navi_amd },
> { PCI_VDEVICE(ATI, 0x73e4), navi_amd },
> { PCI_VDEVICE(ATI, 0x73c4), navi_amd },
> + { PCI_VDEVICE(ATI, 0x7444), navi_amd },
> + { PCI_VDEVICE(ATI, 0x7464), navi_amd },
> { 0,}
> };
> MODULE_DEVICE_TABLE(pci, i2_designware_pci_ids);
> --
> 2.25.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-02 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 17:09 [PATCH] i2c: designware-pci: Add new PCI IDs for AMD NAVI GPU Basavaraj Natikar
2023-01-02 17:29 ` Andy Shevchenko [this message]
2023-01-03 9:27 ` Jarkko Nikula
2023-01-09 15:24 ` Wolfram Sang
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=Y7MUeRqYJ6peB3eh@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Rajesh1.Kumar@amd.com \
--cc=Sanath.S@amd.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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