From: Jamin Lin <jamin_lin@aspeedtech.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Troy Lee" <troy_lee@aspeedtech.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Alistair Francis" <alistair@alistair23.me>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"open list:STM32F205" <qemu-arm@nongnu.org>,
"Joel Stanley" <joel@jms.id.au>, "Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH v5 0/9] Add support for AST1030 SoC
Date: Mon, 11 Apr 2022 10:07:29 +0800 [thread overview]
Message-ID: <20220411020727.GA2461@aspeedtech.com> (raw)
In-Reply-To: <66783c6a-4942-23c5-1052-0dcab389e177@kaod.org>
The 04/05/2022 16:12, Cédric Le Goater wrote:
Hi Cedric,
> Hello Jamin,
>
> On 4/1/22 10:38, Jamin Lin wrote:
> > Changes from v5:
> > - remove TYPE_ASPEED_MINIBMC_MACHINE and ASPEED_MINIBMC_MACHINE
> > - remove ast1030_machine_instance_init function
> >
> > Changes from v4:
> > - drop the ASPEED_SMC_FEATURE_WDT_CONTROL flag in hw/ssi/aspeed_smc.c
> >
> > Changes from v3:
> > - remove AspeedMiniBmcMachineState state structure and
> > AspeedMiniBmcMachineClass class
> > - remove redundant new line in hw/arm/aspeed_ast10xx.c
>
> Do we want to be in sync with the zephyr naming and use ast10x0.c ?
>
> https://github.com/zephyrproject-rtos/zephyr/tree/main/soc/arm/aspeed
>
We used aspeed_ast10xx.c to support minibmc family such as ast1030 and
may support ast1060 in the future.
If need, I can submit the new patch to change its filename to aspeed_ast10x0.c.
Thanks-Jamin
> This is just a question. Don't resend for this.
>
> Thanks,
>
> C.
next prev parent reply other threads:[~2022-04-11 2:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 8:38 [PATCH v5 0/9] Add support for AST1030 SoC Jamin Lin
2022-04-01 8:38 ` [PATCH v5 1/9] aspeed/adc: Add AST1030 support Jamin Lin
2022-04-01 8:38 ` [PATCH v5 2/9] aspeed/smc: " Jamin Lin
2022-04-01 8:38 ` [PATCH v5 3/9] aspeed/wdt: Fix ast2500/ast2600 default reload value Jamin Lin
2022-04-01 8:38 ` [PATCH v5 4/9] aspeed/wdt: Add AST1030 support Jamin Lin
2022-04-01 8:38 ` [PATCH v5 5/9] aspeed/timer: " Jamin Lin
2022-04-01 8:38 ` [PATCH v5 6/9] aspeed/scu: " Jamin Lin
2022-04-01 8:38 ` [PATCH v5 7/9] aspeed/soc : " Jamin Lin
2022-12-29 11:16 ` Philippe Mathieu-Daudé
2023-02-23 10:44 ` Philippe Mathieu-Daudé
2023-02-24 4:06 ` Troy Lee
2022-04-01 8:38 ` [PATCH v5 8/9] aspeed: Add an AST1030 eval board Jamin Lin
2022-04-01 8:47 ` Cédric Le Goater
2022-04-01 8:38 ` [PATCH v5 9/9] test/avocado/machine_aspeed.py: Add ast1030 test case Jamin Lin
2022-04-01 8:55 ` [PATCH v5 0/9] Add support for AST1030 SoC Cédric Le Goater
2022-04-01 9:23 ` Jamin Lin
2022-04-01 9:47 ` Jamin Lin
2022-04-01 13:13 ` Cédric Le Goater
2022-04-01 13:25 ` Cédric Le Goater
2022-04-11 1:49 ` Jamin Lin
2022-04-05 16:12 ` Cédric Le Goater
2022-04-11 2:07 ` Jamin Lin [this message]
2022-04-11 8:23 ` Cédric Le Goater
2022-04-11 8:58 ` Jamin Lin
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=20220411020727.GA2461@aspeedtech.com \
--to=jamin_lin@aspeedtech.com \
--cc=alistair@alistair23.me \
--cc=andrew@aj.id.au \
--cc=bleal@redhat.com \
--cc=clg@kaod.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.com \
--cc=troy_lee@aspeedtech.com \
--cc=wainersm@redhat.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 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.