From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3] i2c: designware: add a new bit check for IC_CON control
Date: Tue, 24 Jan 2023 12:27:36 +0200 [thread overview]
Message-ID: <Y8+ymCM3nQ0/b6sH@smile.fi.intel.com> (raw)
In-Reply-To: <20230124100650.1327656-1-Shyam-sundar.S-k@amd.com>
On Tue, Jan 24, 2023 at 03:36:50PM +0530, Shyam Sundar S K wrote:
> On some AMD platforms, based on the new designware datasheet,
> BIOS sets the BIT(11) within the IC_CON register to advertise
> the "bus clear feature capability".
>
> AMD/Designware datasheet says:
>
> Bit(11) BUS_CLEAR_FEATURE_CTRL. Read-write,Volatile. Reset: 0.
> Description: In Master mode:
> - 1'b1: Bus Clear Feature is enabled.
> - 1'b0: Bus Clear Feature is Disabled.
> In Slave mode, this register bit is not applicable.
>
> On AMD platform designs:
> 1. BIOS programs the BUS_CLEAR_FEATURE_CTRL and enables the detection
> of SCL/SDA stuck low.
> 2. Whenever the stuck low is detected, the SMU FW shall do the bus
> recovery procedure.
>
> Currently, the way in which the "master_cfg" is built in the driver, it
> overrides the BUS_CLEAR_FEATURE_CTRL advertised by BIOS and the SMU FW
> cannot initiate the bus recovery if the stuck low is detected.
>
> Hence add a check in i2c_dw_probe_master() that if the BIOS
> advertises the bus clear feature, let driver not ignore it and
> adapt accordingly.
Fine with me (see one nit-pick below)
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> ---
> v2->v3:
> - Use regmap_read() instead of ioread32()
> - Move the proposed changes to i2c_dw_probe_master() and protect the
> regmap read calls with acquire/release lock calls.
>
> v1->v2:
> - Update the commit message
>
> drivers/i2c/busses/i2c-designware-core.h | 1 +
> drivers/i2c/busses/i2c-designware-master.c | 19 +++++++++++++++++++
> 2 files changed, 20 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-core.h b/drivers/i2c/busses/i2c-designware-core.h
> index 95ebc5eaa5d1..a7ec8d5d0e72 100644
> --- a/drivers/i2c/busses/i2c-designware-core.h
> +++ b/drivers/i2c/busses/i2c-designware-core.h
> @@ -37,6 +37,7 @@
> #define DW_IC_CON_STOP_DET_IFADDRESSED BIT(7)
> #define DW_IC_CON_TX_EMPTY_CTRL BIT(8)
> #define DW_IC_CON_RX_FIFO_FULL_HLD_CTRL BIT(9)
> +#define DW_IC_CON_BUS_CLEAR_CTRL BIT(11)
>
> #define DW_IC_DATA_CMD_DAT GENMASK(7, 0)
>
> diff --git a/drivers/i2c/busses/i2c-designware-master.c b/drivers/i2c/busses/i2c-designware-master.c
> index 45f569155bfe..5db71e0a424a 100644
> --- a/drivers/i2c/busses/i2c-designware-master.c
> +++ b/drivers/i2c/busses/i2c-designware-master.c
> @@ -865,6 +865,7 @@ int i2c_dw_probe_master(struct dw_i2c_dev *dev)
> {
> struct i2c_adapter *adap = &dev->adapter;
> unsigned long irq_flags;
> + u32 ic_con;
> int ret;
>
> init_completion(&dev->cmd_complete);
> @@ -884,6 +885,24 @@ int i2c_dw_probe_master(struct dw_i2c_dev *dev)
> if (ret)
> return ret;
> + /*
> + * On AMD platforms BIOS advertises the bus clear feature
> + * and enables the SCL/SDA stuck low. SMU FW does the
> + * bus recovery process. Driver should not ignore this BIOS
> + * advertisement of bus clear feature.
> + */
Move this comment closer to the actual regmap_read() call.
Perhaps you may add here the following
/* Lock the bus for accessing DW_IC_CON */
> + ret = i2c_dw_acquire_lock(dev);
> + if (ret)
> + return ret;
> +
> + ret = regmap_read(dev->map, DW_IC_CON, &ic_con);
> + i2c_dw_release_lock(dev);
> + if (ret)
> + return ret;
> +
> + if (ic_con & DW_IC_CON_BUS_CLEAR_CTRL)
> + dev->master_cfg |= DW_IC_CON_BUS_CLEAR_CTRL;
> +
> ret = dev->init(dev);
> if (ret)
> return ret;
> --
> 2.25.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-24 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 10:06 [PATCH v3] i2c: designware: add a new bit check for IC_CON control Shyam Sundar S K
2023-01-24 10:27 ` Andy Shevchenko [this message]
2023-01-24 10:29 ` Andy Shevchenko
[not found] ` <a0d42cac-b39a-f59c-950f-94bcb660472a@amd.com>
2023-01-24 11:12 ` Andy Shevchenko
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=Y8+ymCM3nQ0/b6sH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Shyam-sundar.S-k@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