From: Andi Shyti <andi.shyti@kernel.org>
To: ZJVcNIDWEbB6Jq7a@shikoro
Cc: Wolfram Sang <wsa@kernel.org>,
krzk@kernel.org, TonyWWang@zhaoxin.com, cobechen@zhaoxin.com,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v6] i2c: add support for Zhaoxin I2C controller
Date: Fri, 30 Jun 2023 10:01:59 +0200 [thread overview]
Message-ID: <20230630080159.wvt5loiq66tuo24z@intel.intel> (raw)
In-Reply-To: <a12f9bb4-835f-ea18-307f-4aa5ce36f61c@zhaoxin.com>
Hi Hans,
> > > + * registers
> > > + */
> > > +/* I2C MMIO Address Constants */
> > > +#define ZXI2C_CR_L 0x00
> > > +#define ZXI2C_CPU_RDY BIT(3)
> > > +#define ZXI2C_TX_END BIT(2)
> > > +#define ZXI2C_RX_ACK BIT(1)
> > The register layout looks similar to the i2c-wmt driver. Could this
> > driver maybe be reused for your hardware? I'll stop reviewing here
> > because we need to have that clear first.
> >
> > Thank you and happy hacking,
> >
> > Wolfram
> >
>
> I just learned that they are indeed derived from the same VIA I2C IP.
> The relationship between WonderMedia/VIA/Zhaoxin looks like this:
> * The i2c-wmt.c driver is used on the WonderMedia/VT8500 platform,
> an ARM-based SOC from VIA. This SOC hasn't been updated in years.
> Its MAINTAINERS are also Orphan.
> * Lots of VIA IP is now owned by Zhaoxin, including I2C, SMBus, etc.
> Zhaoxin adds some new features on the basis of the original I2C IP,
> such as FIFO mode. And there are plans to continue adding new
> features.
>
> Based on this information, we thought it might be more maintainable
> to create a new driver file.
I think I commented about this some times ago but then forgot.
The two drivers are, indeed, very similar.
We could eventually create a *-common.{c,h} file.
Andi
next prev parent reply other threads:[~2023-06-30 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 3:16 [PATCH v4] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-06-09 9:33 ` Krzysztof Kozlowski
2023-06-12 3:31 ` Hans Hu
2023-06-09 12:24 ` Andi Shyti
2023-06-09 13:11 ` Krzysztof Kozlowski
2023-06-12 8:24 ` Hans Hu
2023-06-09 12:47 ` Andi Shyti
2023-06-14 7:34 ` [PATCH v5] " Hans Hu
2023-06-14 8:21 ` Andi Shyti
2023-06-14 9:48 ` [PATCH v6] " Hans Hu
2023-06-23 8:47 ` Wolfram Sang
2023-06-25 10:57 ` Hans Hu
2023-06-30 8:01 ` Andi Shyti [this message]
[not found] ` <6f3479fb79944d5a8b4a562d67c82a4b@zhaoxin.com>
[not found] ` <1abb34e5cbe74514911598a5a522045b@zhaoxin.com>
2023-07-06 7:25 ` 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=20230630080159.wvt5loiq66tuo24z@intel.intel \
--to=andi.shyti@kernel.org \
--cc=TonyWWang@zhaoxin.com \
--cc=ZJVcNIDWEbB6Jq7a@shikoro \
--cc=cobechen@zhaoxin.com \
--cc=krzk@kernel.org \
--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 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.