mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bowen Yu <yubowen8@huawei.com>
To: <linuxarm@huawei.com>, <liudingyuan@h-partners.com>,
	<andi.shyti@kernel.org>, <linux-i2c@vger.kernel.org>,
	<acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<rafael@kernel.org>, <lenb@kernel.org>
Cc: <zhanjie9@hisilicon.com>, <prime.zeng@hisilicon.com>,
	<wanghuiqiang@huawei.com>, <xuwei5@huawei.com>,
	<yubowen8@huawei.com>, <ouyiyong1@huawei.com>
Subject: [PATCH v5 0/2] HiSilicon I2C bus recovery support
Date: Tue, 29 Sep 2026 20:13:46 +0800	[thread overview]
Message-ID: <20260929121348.109556-1-yubowen8@huawei.com> (raw)

Changes since v4:
  - Patch 1 (new): Add a static inline stub for acpi_has_method() in
    <linux/acpi.h> for !CONFIG_ACPI builds. This is the prerequisite
    for dropping the #ifdef in the driver: acpi_has_method() is the
    only ACPI symbol referenced by the recovery code that lacks an
    automatic stub (the ACPICA core helpers already get stubs via
    ACPI_EXTERNAL_RETURN_*).
  - Patch 2: Drop the #ifdef CONFIG_ACPI guard around the recovery
    helpers in i2c-hisi.c. The six recovery functions are now compiled
    unconditionally.

Patch 2 depends on Patch 1 for !CONFIG_ACPI compilation.

Bowen Yu (2):
  ACPI: Add stub for acpi_has_method() for !CONFIG_ACPI
  i2c: hisi: Add I2C bus recovery support

 drivers/i2c/busses/i2c-hisi.c | 142 ++++++++++++++++++++++++++++++++++
 include/linux/acpi.h          |   5 ++
 2 files changed, 147 insertions(+)

-- 
2.33.0


             reply	other threads:[~2026-09-29 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 12:13 Bowen Yu [this message]
2026-09-29 12:13 ` [PATCH v5 1/2] ACPI: Add stub for acpi_has_method() for !CONFIG_ACPI Bowen Yu
2026-09-29 12:28   ` Rafael J. Wysocki (Intel)
2026-09-29 12:13 ` [PATCH v5 2/2] i2c: hisi: Add I2C bus recovery support Bowen Yu
2026-10-13 13:44   ` Jie Zhan
2026-10-27 10:51   ` Andi Shyti
2026-10-30  2:39     ` yubowen (H)

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=20260929121348.109556-1-yubowen8@huawei.com \
    --to=yubowen8@huawei.com \
    --cc=acpi@vger.kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liudingyuan@h-partners.com \
    --cc=ouyiyong1@huawei.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=rafael@kernel.org \
    --cc=wanghuiqiang@huawei.com \
    --cc=xuwei5@huawei.com \
    --cc=zhanjie9@hisilicon.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

all inboxes | Powered by JetHome®