From: Hans Hu <HansHu-oc@zhaoxin.com>
To: Wolfram Sang <wsa@kernel.org>, <andi.shyti@kernel.org>,
<linux-i2c@vger.kernel.org>, <cobechen@zhaoxin.com>,
<TonyWWang@zhaoxin.com>
Subject: Re: [PATCH v2 1/2] i2c: wmt: split out i2c-viai2c-common.{c,h}
Date: Mon, 28 Aug 2023 10:42:36 +0800 [thread overview]
Message-ID: <744e7a46-066f-738f-69cc-9f2374be2fba@zhaoxin.com> (raw)
In-Reply-To: <ZOkI62MZee+3HR6n@shikoro>
On 2023/8/26 04:02, Wolfram Sang wrote:
> Hi!
>
> first of all, thank you for reworking your driver to share common code
> with the WMT driver. This effort is much appreciated and we are close to
> go, I think. But some remarks.
>
>> +config I2C_VIAI2C_COMMON
>> + tristate
>> +
>> config I2C_WMT
>> tristate "Wondermedia WM8xxx SoC I2C bus support"
>> depends on ARCH_VT8500 || COMPILE_TEST
>> + select I2C_VIAI2C_COMMON
>> help
>> Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
>> SoCs.
>> diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
>> index af56fe2c75c0..b7e20c3531b5 100644
>> --- a/drivers/i2c/busses/Makefile
>> +++ b/drivers/i2c/busses/Makefile
>> @@ -120,6 +120,7 @@ obj-$(CONFIG_I2C_TEGRA_BPMP) += i2c-tegra-bpmp.o
>> obj-$(CONFIG_I2C_UNIPHIER) += i2c-uniphier.o
>> obj-$(CONFIG_I2C_UNIPHIER_F) += i2c-uniphier-f.o
>> obj-$(CONFIG_I2C_VERSATILE) += i2c-versatile.o
>> +obj-$(CONFIG_I2C_VIAI2C_COMMON) += i2c-viai2c-common.o
>> obj-$(CONFIG_I2C_WMT) += i2c-wmt.o
>> i2c-octeon-objs := i2c-octeon-core.o i2c-octeon-platdrv.o
>> obj-$(CONFIG_I2C_OCTEON) += i2c-octeon.o
> I'd prefer to link the core object to the driver object like pasemi or
> octeon do. Or is there an argument for having a seperate module?
There are two main reasons:
1. I checked the MAINTAINERS section related to ARM/VT8500,
Found that the entire ARM/VT8500 ARCHITECTURE is currently
unmaintained, maybe one day it will be removed from the kernel.
So I think it might be better as a separate module.
2. In addition, if not separated from wmt, the driver would
become a bit confusing and difficult to maintain.
> Regards!
>
next prev parent reply other threads:[~2023-08-28 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 8:40 [PATCH v2 0/2] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-08-14 8:40 ` [PATCH v2 1/2] i2c: wmt: split out i2c-viai2c-common.{c,h} Hans Hu
2023-08-25 20:02 ` Wolfram Sang
2023-08-28 2:42 ` Hans Hu [this message]
2023-08-28 6:00 ` Wolfram Sang
2023-08-28 7:25 ` Hans Hu
2023-08-28 7:37 ` Wolfram Sang
2023-08-14 8:40 ` [PATCH v2 2/2] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-08-25 20:04 ` Wolfram Sang
2023-08-28 2:50 ` Hans Hu
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=744e7a46-066f-738f-69cc-9f2374be2fba@zhaoxin.com \
--to=hanshu-oc@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=andi.shyti@kernel.org \
--cc=cobechen@zhaoxin.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@kernel.org \
/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