From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Hao Yao <hao.yao@intel.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media: ipu6: Remove workaround for Meteor Lake ES2
Date: Tue, 11 Mar 2025 10:03:32 +0100 [thread overview]
Message-ID: <Z8/8ZNKWo3jU0HEW@linux.intel.com> (raw)
In-Reply-To: <20250311084203.516205-1-hao.yao@intel.com>
On Tue, Mar 11, 2025 at 04:41:55PM +0800, Hao Yao wrote:
> There was a hardware bug which need IPU6 driver to disable the ATS.
> This workaround is not needed anymore as the bug was fixed in
> hardware level.
>
> Signed-off-by: Hao Yao <hao.yao@intel.com>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Regards
Stanislaw
> ---
> drivers/media/pci/intel/ipu6/ipu6.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6.c b/drivers/media/pci/intel/ipu6/ipu6.c
> index 277af7cda8ee..b00d0705fefa 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6.c
> @@ -464,11 +464,6 @@ static int ipu6_pci_config_setup(struct pci_dev *dev, u8 hw_ver)
> {
> int ret;
>
> - /* disable IPU6 PCI ATS on mtl ES2 */
> - if (is_ipu6ep_mtl(hw_ver) && boot_cpu_data.x86_stepping == 0x2 &&
> - pci_ats_supported(dev))
> - pci_disable_ats(dev);
> -
> /* No PCI msi capability for IPU6EP */
> if (is_ipu6ep(hw_ver) || is_ipu6ep_mtl(hw_ver)) {
> /* likely do nothing as msi not enabled by default */
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-03-11 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:41 [PATCH] media: ipu6: Remove workaround for Meteor Lake ES2 Hao Yao
2025-03-11 9:03 ` Stanislaw Gruszka [this message]
2025-04-24 4:18 ` Bingbu Cao
2025-04-24 11:55 ` Sakari Ailus
2025-04-25 3:05 ` Bingbu Cao
2025-04-25 5:40 ` Sakari Ailus
2025-04-25 6:28 ` Hao Yao
2025-04-25 6:30 ` Sakari Ailus
2025-04-25 6:29 ` Bingbu Cao
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=Z8/8ZNKWo3jU0HEW@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hao.yao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.