From: Sanjay R Mehta <sanmehta@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Sanjay R Mehta <sanju.mehta@amd.com>
Cc: wsa+renesas@sang-engineering.com, jarkko.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com, jdelvare@suse.de,
Sergey.Semin@baikalelectronics.ru, kblaiech@mellanox.com,
loic.poulain@linaro.org, rppt@kernel.org,
bjorn.andersson@linaro.org, linux@roeck-us.net,
vadimp@mellanox.com, tali.perry1@gmail.com,
linux-i2c@vger.kernel.org,
Nehal Bakulchandra Shah <Nehal-Bakulchandra.Shah@amd.com>
Subject: Re: [PATCH v2] i2c: add i2c bus driver for amd navi gpu
Date: Tue, 8 Dec 2020 18:32:13 +0530 [thread overview]
Message-ID: <8fd4f648-9672-7e26-12df-4d0b953c1949@amd.com> (raw)
In-Reply-To: <20201208124724.GA29797@kozik-lap>
On 12/8/2020 6:17 PM, Krzysztof Kozlowski wrote:
> [CAUTION: External Email]
>
> On Tue, Dec 08, 2020 at 06:37:41AM -0600, Sanjay R Mehta wrote:
>> From: Sanjay R Mehta <Sanju.Mehta@amd.com>
>>
>> Latest amdgpu card has USB Type-C interface. There is a Type-C controller
>> which can be accessed over I2C.
>>
>> This driver adds I2C bus driver to communicate with Type-C controller. I2C
>> client driver will be part of USB Type-C UCSI driver.
>>
>> Signed-off-by: Sanjay R Mehta <Sanju.Mehta@amd.com>
>> Signed-off-by: Nehal Bakulchandra Shah <Nehal-Bakulchandra.Shah@amd.com>
>> ---
>>
>> Changes in v2:
>>
>> - converted the code to use regmap, read_poll_timeout and made some cosmetic
>> changes as suggested by Andy Shevchenko.
>> ---
>> MAINTAINERS | 7 +
>> drivers/i2c/busses/Kconfig | 9 +
>> drivers/i2c/busses/Makefile | 1 +
>> drivers/i2c/busses/i2c-amdgpu-navi.c | 345 +++++++++++++++++++++++++++
>> 4 files changed, 362 insertions(+)
>> create mode 100644 drivers/i2c/busses/i2c-amdgpu-navi.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 190c7fa2ea01..93894459a4c8 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8119,6 +8119,13 @@ L: linux-acpi@vger.kernel.org
>> S: Maintained
>> F: drivers/i2c/i2c-core-acpi.c
>>
>> +I2C CONTROLLER DRIVER FOR AMD GPU
>> +M: Nehal Bakulchandra Shah <Nehal-Bakulchandra.Shah@amd.com>
>> +M: Sanjay R Mehta <sanju.mehta@amd.com>
>> +L: linux-i2c@vger.kernel.org
>> +S: Maintained
>> +F: drivers/i2c/busses/i2c-amdgpu-navi.*
>> +
>> I2C CONTROLLER DRIVER FOR NVIDIA GPU
>> M: Ajay Gupta <ajayg@nvidia.com>
>> L: linux-i2c@vger.kernel.org
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 293e7a0760e7..0ff369c0f41f 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -88,6 +88,15 @@ config I2C_AMD_MP2
>> This driver can also be built as modules. If so, the modules will
>> be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
>>
>> +config I2C_AMDGPU_NAVI
>> + tristate "AMDGPU NAVI I2C controller"
>> + depends on PCI
>> + help
>> + If you say yes to this option, support will be included for the
>> + NAVI I2C controller which is used to communicate with the GPU's
>> + Type-C controller. This driver can also be built as a module called
>> + i2c-amdgpu-navi.
>> +
>> config I2C_HIX5HD2
>> tristate "Hix5hd2 high-speed I2C driver"
>> depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
>> diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
>> index 19aff0e45cb5..f599473a8ad9 100644
>> --- a/drivers/i2c/busses/Makefile
>> +++ b/drivers/i2c/busses/Makefile
>> @@ -13,6 +13,7 @@ obj-$(CONFIG_I2C_ALI15X3) += i2c-ali15x3.o
>> obj-$(CONFIG_I2C_AMD756) += i2c-amd756.o
>> obj-$(CONFIG_I2C_AMD756_S4882) += i2c-amd756-s4882.o
>> obj-$(CONFIG_I2C_AMD8111) += i2c-amd8111.o
>> +obj-$(CONFIG_I2C_AMDGPU_NAVI) += i2c-amdgpu-navi.o
>> obj-$(CONFIG_I2C_CHT_WC) += i2c-cht-wc.o
>> obj-$(CONFIG_I2C_I801) += i2c-i801.o
>> obj-$(CONFIG_I2C_ISCH) += i2c-isch.o
>> diff --git a/drivers/i2c/busses/i2c-amdgpu-navi.c b/drivers/i2c/busses/i2c-amdgpu-navi.c
>> new file mode 100644
>> index 000000000000..3922b8aebc26
>> --- /dev/null
>> +++ b/drivers/i2c/busses/i2c-amdgpu-navi.c
>> @@ -0,0 +1,345 @@
>> +// SPDX-License-Identifier: GPL-2.0+
>> +//
>> +// AMD I2C Controller Driver for Navi GPU's
>> +//
>> +// Copyright (c) 2020, Advanced Micro Devices, Inc.
>> +//
>> +// Authors:
>> +// Nehal Bakulchandra Shah <Nehal-Bakulchandra.Shah@amd.com>
>> +// Sanjay R Mehta <Sanju.Mehta@amd.com>
>> +
>> +#include <linux/bits.h>
>> +#include <linux/delay.h>
>> +#include <linux/i2c.h>
>> +#include <linux/interrupt.h>
>> +#include <linux/module.h>
>> +#include <linux/pci.h>
>> +#include <linux/platform_device.h>
>> +#include <linux/pm.h>
>> +#include <linux/regmap.h>
>> +#include <asm/unaligned.h>
>> +#include "i2c-designware-core.h"
>> +
>> +#define AMD_UCSI_INTR_EN 0xD
>> +#define AMD_UCSI_INTR_REG 0x474
>> +#define AMD_MASTERCFG_MASK GENMASK(15, 0)
>> +
>> +struct amdgpu_i2c_dev {
>> + void __iomem *regs;
>> + struct regmap *map;
>> + struct device *dev;
>> + u32 master_cfg;
>> + u32 slave_adr;
>> + u32 tx_fifo_depth;
>> + u32 rx_fifo_depth;
>> + u16 ss_hcnt;
>> + u16 ss_lcnt;
>> + struct i2c_adapter adapter;
>> + struct i2c_board_info *gpu_ccgx_ucsi;
>> + struct i2c_client *ccgx_client;
>> +};
>> +
>> +static int amdgpu_i2c_read(void *context, unsigned int reg, unsigned int *val)
>> +{
>> + struct amdgpu_i2c_dev *i2cd = context;
>> +
>> + *val = readl_relaxed(i2cd->regs + reg);
>
> It's quite confusing calling it "i2c_read" function. What is more
> important - why do you need it? It's a simple MMIO on PCI, so why regmap
> MMIO cannot be used?
>
Thanks Krzysztof.
I am new to using regmap based API's and had referred to designware code for this.
(https://elixir.bootlin.com/linux/latest/source/drivers/i2c/busses/i2c-designware-common.c#L61)
Any specific API you recommend me to use or any driver you want me to refer will be helpful.
Thanks & Regards,
Sanjay
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2020-12-08 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 12:37 [PATCH v2] i2c: add i2c bus driver for amd navi gpu Sanjay R Mehta
2020-12-08 12:47 ` Krzysztof Kozlowski
2020-12-08 13:02 ` Sanjay R Mehta [this message]
2020-12-08 16:48 ` Sanjay R Mehta
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=8fd4f648-9672-7e26-12df-4d0b953c1949@amd.com \
--to=sanmehta@amd.com \
--cc=Nehal-Bakulchandra.Shah@amd.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=kblaiech@mellanox.com \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=loic.poulain@linaro.org \
--cc=rppt@kernel.org \
--cc=sanju.mehta@amd.com \
--cc=tali.perry1@gmail.com \
--cc=vadimp@mellanox.com \
--cc=wsa+renesas@sang-engineering.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