mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Delevoryas <pdel@fb.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	OpenBMC List <openbmc@lists.ozlabs.org>,
	BMC-SW <BMC-SW@aspeedtech.com>,
	"ryan_chen@aspeedtech.com" <ryan_chen@aspeedtech.com>,
	Peter Delevoryas <pdel@fb.com>
Subject: Re: [PATCH v3 0/3] Add ASPEED AST2600 I2C new controller driver
Date: Fri, 20 May 2022 03:01:39 +0000	[thread overview]
Message-ID: <A553E632-F534-4823-BC50-89408294DB5F@fb.com> (raw)
In-Reply-To: <SEZPR06MB52697491CF6D06ECB85F0FB7F2D39@SEZPR06MB5269.apcprd06.prod.outlook.com>



> On May 19, 2022, at 7:46 PM, Ryan Chen <ryan_chen@aspeedtech.com> wrote:
> 
> Hello,
> 
>> -----Original Message-----
>> From: Peter Delevoryas <pdel@fb.com>
>> Sent: Friday, May 20, 2022 3:56 AM
>> Cc: Joel Stanley <joel@jms.id.au>; Andrew Jeffery <andrew@aj.id.au>; Philipp
>> Zabel <p.zabel@pengutronix.de>; linux-arm-kernel@lists.infradead.org;
>> linux-aspeed@lists.ozlabs.org; linux-kernel@vger.kernel.org; OpenBMC List
>> <openbmc@lists.ozlabs.org>; BMC-SW <BMC-SW@aspeedtech.com>; Peter
>> Delevoryas <pdel@fb.com>; Ryan Chen <ryan_chen@aspeedtech.com>
>> Subject: Re: [PATCH v3 0/3] Add ASPEED AST2600 I2C new controller driver
>> 
>> 
>> 
>>> On May 15, 2022, at 11:48 PM, ryan_chen <ryan_chen@aspeedtech.com>
>> wrote:
>>> 
>>> This series add AST2600 i2c new register set driver. The i2c new
>>> register set have new clock divider option for more flexiable generation.
>>> And also have separate i2c master and slave register set for control.
>> 
>> Hey Ryan, thanks for this work! This is a little bit off-topic, but are you or
>> anyone else at Aspeed working on an equivalent QEMU patch series? Without
>> it, I don’t think QEMU will work with this series right? I think QEMU only
>> supports the old register set right now.
>> 
> No, there are two submit in QEMU about i2c new register mode.
> One is ASPEED submit : https://patchwork.kernel.org/project/qemu-devel/list/?series=626028&archive=both
> Another is GOOGLE : https://patchwork.kernel.org/project/qemu-devel/list/?series=627706&archive=both

Oh great, thanks. I just tried the Aspeed QEMU series and it worked for me with Zephyr, very helpful!

> 
>> 
>>> 
>>> v3:
>>> -fix i2c global clock divide default value -remove i2c slave no used
>>> dev_dbg info.
>>> 
>>> v2:
>>> -add i2c global ymal file commit
>>> -rename file name from new to ast2600.
>>> aspeed-i2c-new-global.c -> i2c-ast2600-global.c
>>> aspeed-i2c-new-global.h -> i2c-ast2600-global.h i2c-new-aspeed.c ->
>>> i2c-ast2600.c -rename all driver function name to ast2600
>>> 
>>> ryan_chen (3):
>>> dt-bindings: i2c-ast2600: Add bindings for AST2600 i2C global register
>>> controller
>>> dt-bindings: i2c-ast2600: Add bindings for AST2600 i2C driver
>>> i2c:aspeed:support ast2600 i2c new register mode driver
>>> 
>>> .../i2c/aspeed,i2c-ast2600-global.ymal | 44 +
>>> .../bindings/i2c/aspeed,i2c-ast2600.ymal | 78 +
>>> drivers/i2c/busses/Kconfig | 11 +
>>> drivers/i2c/busses/Makefile | 1 +
>>> drivers/i2c/busses/i2c-ast2600-global.c | 94 +
>>> drivers/i2c/busses/i2c-ast2600-global.h | 19 +
>>> drivers/i2c/busses/i2c-ast2600.c | 1703
>> +++++++++++++++++
>>> 7 files changed, 1950 insertions(+)
>>> create mode 100644
>>> Documentation/devicetree/bindings/i2c/aspeed,i2c-ast2600-global.ymal
>>> create mode 100644
>>> Documentation/devicetree/bindings/i2c/aspeed,i2c-ast2600.ymal
>>> create mode 100644 drivers/i2c/busses/i2c-ast2600-global.c
>>> create mode 100644 drivers/i2c/busses/i2c-ast2600-global.h
>>> create mode 100644 drivers/i2c/busses/i2c-ast2600.c
>>> 
>>> --
>>> 2.17.1


  reply	other threads:[~2022-05-20  3:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  6:48 ryan_chen
2022-05-16  6:48 ` [PATCH v3 1/3] dt-bindings: i2c-ast2600: Add bindings for AST2600 i2C global register controller ryan_chen
2022-05-16  6:48 ` [PATCH v3 2/3] dt-bindings: i2c-ast2600: Add bindings for AST2600 i2C driver ryan_chen
2022-07-29  2:28   ` Andrew Jeffery
2022-07-29  3:03     ` Ryan Chen
2022-07-29  3:13       ` Andrew Jeffery
2022-08-02  9:04         ` Ryan Chen
2022-08-09  0:34           ` Andrew Jeffery
2022-08-09  0:59             ` Ryan Chen
2022-05-16  6:49 ` [PATCH v3 3/3] i2c:aspeed:support ast2600 i2c new register mode driver ryan_chen
2022-05-19 19:56 ` [PATCH v3 0/3] Add ASPEED AST2600 I2C new controller driver Peter Delevoryas
2022-05-20  2:46   ` Ryan Chen
2022-05-20  3:01     ` Peter Delevoryas [this message]
2022-05-20  3:15       ` Ryan Chen

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=A553E632-F534-4823-BC50-89408294DB5F@fb.com \
    --to=pdel@fb.com \
    --cc=BMC-SW@aspeedtech.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=p.zabel@pengutronix.de \
    --cc=ryan_chen@aspeedtech.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®