From: Minda Chen <minda.chen@starfivetech.com>
To: Simon Glass <sjg@chromium.org>
Cc: "Heiko Schocher" <hs@denx.de>, "Stefan Roese" <sr@denx.de>,
"Andrew Scull" <ascull@google.com>,
"Pali Rohár" <pali@kernel.org>,
"Mark Kettenis" <kettenis@openbsd.org>,
"Rick Chen" <rick@andestech.com>, Leo <ycliang@andestech.com>,
u-boot@lists.denx.de, "Mason Huo" <mason.huo@starfivetech.com>,
"Leyfoon Tan" <leyfoon.tan@starfivetech.com>,
"Kevin Xie" <kevin.xie@starfivetech.com>
Subject: Re: [PATCH v7 1/4] i2c: designware: Add CONFIG_ACPIGEN limitation to designware_i2c_pci.c
Date: Fri, 21 Jul 2023 09:32:57 +0800 [thread overview]
Message-ID: <fdc64273-4920-eea0-7c3c-fff0ae90d4b2@starfivetech.com> (raw)
In-Reply-To: <CAPnjgZ1MGJtM+Ue207rW+edpk-HrZi6d4RO1_FT=D-hmbkSFfA@mail.gmail.com>
On 2023/7/21 3:42, Simon Glass wrote:
> Hi,
>
> On Thu, 20 Jul 2023 at 05:24, Minda Chen <minda.chen@starfivetech.com> wrote:
>>
>> As the designware_i2c_pci.c uses ACPI APIs, If some SoCs (StarFive
>> JH7110) contain designware i2c and PCI but do not use ACPI,
>> This file will be can't be compiled. So add ACPIGEN to
>> designware_i2c_pci.c
>>
>> Signed-off-by: Minda Chen <minda.chen@starfivetech.com>
>> ---
>> drivers/i2c/Makefile | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/i2c/Makefile b/drivers/i2c/Makefile
>> index 99545df2e5..92b1ec6bc3 100644
>> --- a/drivers/i2c/Makefile
>> +++ b/drivers/i2c/Makefile
>> @@ -18,9 +18,11 @@ obj-$(CONFIG_SYS_I2C_CADENCE) += i2c-cdns.o
>> obj-$(CONFIG_SYS_I2C_CA) += i2c-cortina.o
>> obj-$(CONFIG_SYS_I2C_DAVINCI) += davinci_i2c.o
>> obj-$(CONFIG_SYS_I2C_DW) += designware_i2c.o
>> +ifdef CONFIG_ACPIGEN
>
> You should use Kconfig to see SYS_I2C_DW depends on ACPIGEN. You might
> need a separate I2C_DW_PCI Kconfig.
>
I think so.
I can add Kconfig like this.
config SYS_I2C_DW_PCI
bool "Designware PCI I2C Controller"
depends on SYS_I2C_DW && PCI && APIGEN
default y
> But that sounds bad to me. Why does it have to generate ACPI tables?
> It should work fine without that.
>
designware_i2c_pci.c contain ACPI and lpss related codes.
>> ifdef CONFIG_PCI
>> obj-$(CONFIG_SYS_I2C_DW) += designware_i2c_pci.o
>> endif
>> +endif
>> obj-$(CONFIG_SYS_I2C_FSL) += fsl_i2c.o
>> obj-$(CONFIG_SYS_I2C_IHS) += ihs_i2c.o
>> obj-$(CONFIG_SYS_I2C_INTEL) += intel_i2c.o
>> --
>> 2.17.1
>>
>
> Regards,
> Simon
next prev parent reply other threads:[~2023-07-21 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:23 [PATCH v7 0/4] Add StarFive JH7110 PCIe drvier support Minda Chen
2023-07-20 11:23 ` [PATCH v7 1/4] i2c: designware: Add CONFIG_ACPIGEN limitation to designware_i2c_pci.c Minda Chen
2023-07-20 19:42 ` Simon Glass
2023-07-21 1:32 ` Minda Chen [this message]
2023-07-20 11:23 ` [PATCH v7 2/4] starfive: pci: Add StarFive JH7110 pcie driver Minda Chen
2023-07-25 1:24 ` Leo Liang
2023-07-20 11:23 ` [PATCH v7 3/4] configs: starfive-jh7110: Add support for PCIe host driver Minda Chen
2023-07-25 1:25 ` Leo Liang
2023-07-20 11:23 ` [PATCH v7 4/4] riscv: dts: starfive: Enable PCIe host controller Minda Chen
2023-07-25 1:26 ` Leo Liang
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=fdc64273-4920-eea0-7c3c-fff0ae90d4b2@starfivetech.com \
--to=minda.chen@starfivetech.com \
--cc=ascull@google.com \
--cc=hs@denx.de \
--cc=kettenis@openbsd.org \
--cc=kevin.xie@starfivetech.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=mason.huo@starfivetech.com \
--cc=pali@kernel.org \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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