From: Rashmica Gupta <rashmica.g@gmail.com>
To: "Joel Stanley" <joel@jms.id.au>, "Cédric Le Goater" <clg@kaod.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 3/3] hw: aspeed_gpio: Clarify GPIO controller name
Date: Tue, 13 Jul 2021 17:48:09 +1000 [thread overview]
Message-ID: <92f6c1442cb2397a02b288fbcdf0cb7a760a86c6.camel@gmail.com> (raw)
In-Reply-To: <20210713065854.134634-4-joel@jms.id.au>
On Tue, 2021-07-13 at 16:28 +0930, Joel Stanley wrote:
> There are two GPIO controllers in the ast2600; one is 3.3V and the
> other
> is 1.8V.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
Thanks for picking this up.
Reviewed-by: Rashmica Gupta <rashmica.g@gmail.com>
> ---
> hw/gpio/aspeed_gpio.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/hw/gpio/aspeed_gpio.c b/hw/gpio/aspeed_gpio.c
> index dc721aec5da7..dfa6d6cb40a9 100644
> --- a/hw/gpio/aspeed_gpio.c
> +++ b/hw/gpio/aspeed_gpio.c
> @@ -164,12 +164,12 @@
> #define GPIO_YZAAAB_DIRECTION (0x1E4 >> 2)
> #define GPIO_AC_DATA_VALUE (0x1E8 >> 2)
> #define GPIO_AC_DIRECTION (0x1EC >> 2)
> -#define GPIO_3_6V_MEM_SIZE 0x1F0
> -#define GPIO_3_6V_REG_ARRAY_SIZE (GPIO_3_6V_MEM_SIZE >> 2)
> +#define GPIO_3_3V_MEM_SIZE 0x1F0
> +#define GPIO_3_3V_REG_ARRAY_SIZE (GPIO_3_3V_MEM_SIZE >> 2)
>
> /* AST2600 only - 1.8V gpios */
> /*
> - * The AST2600 two copies of the GPIO controller: the same 3.6V
> gpios as the
> + * The AST2600 two copies of the GPIO controller: the same 3.3V
> gpios as the
> * AST2400 (memory offsets 0x0-0x198) and a second controller with
> 1.8V gpios
> * (memory offsets 0x800-0x9D4).
> */
> @@ -380,7 +380,7 @@ static uint32_t
> update_value_control_source(GPIOSets *regs, uint32_t old_value,
> return new_value;
> }
>
> -static const AspeedGPIOReg
> aspeed_3_6v_gpios[GPIO_3_6V_REG_ARRAY_SIZE] = {
> +static const AspeedGPIOReg
> aspeed_3_3v_gpios[GPIO_3_3V_REG_ARRAY_SIZE] = {
> /* Set ABCD */
> [GPIO_ABCD_DATA_VALUE] = { 0, gpio_reg_data_value },
> [GPIO_ABCD_DIRECTION] = { 0, gpio_reg_direction },
> @@ -800,7 +800,7 @@ static const GPIOSetProperties
> ast2500_set_props[] = {
> [7] = {0x000000ff, 0x000000ff, {"AC"} },
> };
>
> -static GPIOSetProperties ast2600_3_6v_set_props[] = {
> +static GPIOSetProperties ast2600_3_3v_set_props[] = {
> [0] = {0xffffffff, 0xffffffff, {"A", "B", "C", "D"} },
> [1] = {0xffffffff, 0xffffffff, {"E", "F", "G", "H"} },
> [2] = {0xffffffff, 0xffffffff, {"I", "J", "K", "L"} },
> @@ -927,7 +927,7 @@ static void
> aspeed_gpio_ast2400_class_init(ObjectClass *klass, void *data)
> agc->nr_gpio_pins = 216;
> agc->nr_gpio_sets = 7;
> agc->gap = 196;
> - agc->reg_table = aspeed_3_6v_gpios;
> + agc->reg_table = aspeed_3_3v_gpios;
> }
>
> static void aspeed_gpio_2500_class_init(ObjectClass *klass, void
> *data)
> @@ -938,17 +938,17 @@ static void
> aspeed_gpio_2500_class_init(ObjectClass *klass, void *data)
> agc->nr_gpio_pins = 228;
> agc->nr_gpio_sets = 8;
> agc->gap = 220;
> - agc->reg_table = aspeed_3_6v_gpios;
> + agc->reg_table = aspeed_3_3v_gpios;
> }
>
> -static void aspeed_gpio_ast2600_3_6v_class_init(ObjectClass *klass,
> void *data)
> +static void aspeed_gpio_ast2600_3_3v_class_init(ObjectClass *klass,
> void *data)
> {
> AspeedGPIOClass *agc = ASPEED_GPIO_CLASS(klass);
>
> - agc->props = ast2600_3_6v_set_props;
> + agc->props = ast2600_3_3v_set_props;
> agc->nr_gpio_pins = 208;
> agc->nr_gpio_sets = 7;
> - agc->reg_table = aspeed_3_6v_gpios;
> + agc->reg_table = aspeed_3_3v_gpios;
> }
>
> static void aspeed_gpio_ast2600_1_8v_class_init(ObjectClass *klass,
> void *data)
> @@ -984,10 +984,10 @@ static const TypeInfo aspeed_gpio_ast2500_info
> = {
> .instance_init = aspeed_gpio_init,
> };
>
> -static const TypeInfo aspeed_gpio_ast2600_3_6v_info = {
> +static const TypeInfo aspeed_gpio_ast2600_3_3v_info = {
> .name = TYPE_ASPEED_GPIO "-ast2600",
> .parent = TYPE_ASPEED_GPIO,
> - .class_init = aspeed_gpio_ast2600_3_6v_class_init,
> + .class_init = aspeed_gpio_ast2600_3_3v_class_init,
> .instance_init = aspeed_gpio_init,
> };
>
> @@ -1003,7 +1003,7 @@ static void aspeed_gpio_register_types(void)
> type_register_static(&aspeed_gpio_info);
> type_register_static(&aspeed_gpio_ast2400_info);
> type_register_static(&aspeed_gpio_ast2500_info);
> - type_register_static(&aspeed_gpio_ast2600_3_6v_info);
> + type_register_static(&aspeed_gpio_ast2600_3_3v_info);
> type_register_static(&aspeed_gpio_ast2600_1_8v_info);
> }
>
next prev parent reply other threads:[~2021-07-13 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 6:58 [PATCH v2 0/3] hw: aspeed_gpio: MMIO region fix and cleanups Joel Stanley
2021-07-13 6:58 ` [PATCH v2 1/3] hw: aspeed_gpio: Fix memory size Joel Stanley
2021-07-13 7:41 ` Rashmica Gupta
2021-07-19 16:02 ` [SPAM] " Cédric Le Goater
2021-07-27 8:02 ` Joel Stanley
2021-07-27 9:58 ` Peter Maydell
2021-07-13 6:58 ` [PATCH v2 2/3] hw: aspeed_gpio: Simplify 1.8V defines Joel Stanley
2021-07-13 7:46 ` Rashmica Gupta
2021-07-19 16:02 ` [SPAM] " Cédric Le Goater
2021-07-19 22:05 ` Philippe Mathieu-Daudé
2021-07-13 6:58 ` [PATCH v2 3/3] hw: aspeed_gpio: Clarify GPIO controller name Joel Stanley
2021-07-13 7:48 ` Rashmica Gupta [this message]
2021-07-19 16:02 ` [SPAM] " Cédric Le Goater
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=92f6c1442cb2397a02b288fbcdf0cb7a760a86c6.camel@gmail.com \
--to=rashmica.g@gmail.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).