All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ye Zhang <ye.zhang@rock-chips.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, heiko@sntech.de,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	mika.westerberg@linux.intel.com, tao.huang@rock-chips.com,
	finley.xiao@rock-chips.com, tim.chen@rock-chips.com,
	elaine.zhang@rock-chips.com
Subject: Re: [PATCH v2] gpio: rockchip: support new version gpio
Date: Fri, 23 Aug 2024 18:05:09 +0300	[thread overview]
Message-ID: <ZsilJZS2_Kvyhs1S@smile.fi.intel.com> (raw)
In-Reply-To: <20240823034314.62305-9-ye.zhang@rock-chips.com>

On Fri, Aug 23, 2024 at 11:43:11AM +0800, Ye Zhang wrote:
> The next version gpio controller on SoCs like rk3576 which support four
> OS operation and four interrupts

...

>  #define GPIO_TYPE_V2		(0x01000C2B)  /* GPIO Version ID 0x01000C2B */
>  #define GPIO_TYPE_V2_1		(0x0101157C)  /* GPIO Version ID 0x0101157C */
> +#define GPIO_TYPE_V2_2		(0x010219C8)  /* GPIO Version ID 0x010219C8 */

These needs a bit of decoding. As far as I can decipher these it's something like

0x01 00 00 00 ???

0x00 xx 00 00 // seems like a subversion, 2.xx

0x00 00 xx xx // seems like a release which is

3115
5500
6600

in decimal representation.

But again, can you make the comments better explaining these cryptic 4-byte
values?

With that done it might be better approach to check the version of the IP.

...

> +	switch (id) {
> +	case GPIO_TYPE_V2:
> +	case GPIO_TYPE_V2_1:
>  		bank->gpio_regs = &gpio_regs_v2;
>  		bank->gpio_type = GPIO_TYPE_V2;
> -	} else {
> +		break;
> +	case GPIO_TYPE_V2_2:
> +		bank->gpio_regs = &gpio_regs_v2;
> +		bank->gpio_type = GPIO_TYPE_V2_2;
> +		break;
> +	default:
>  		bank->gpio_regs = &gpio_regs_v1;
>  		bank->gpio_type = GPIO_TYPE_V1;
> +		pr_info("Note: Use default GPIO_TYPE_V1!\n");

Missed break;

>  	}

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ye Zhang <ye.zhang@rock-chips.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, heiko@sntech.de,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	mika.westerberg@linux.intel.com, tao.huang@rock-chips.com,
	finley.xiao@rock-chips.com, tim.chen@rock-chips.com,
	elaine.zhang@rock-chips.com
Subject: Re: [PATCH v2] gpio: rockchip: support new version gpio
Date: Fri, 23 Aug 2024 18:05:09 +0300	[thread overview]
Message-ID: <ZsilJZS2_Kvyhs1S@smile.fi.intel.com> (raw)
In-Reply-To: <20240823034314.62305-9-ye.zhang@rock-chips.com>

On Fri, Aug 23, 2024 at 11:43:11AM +0800, Ye Zhang wrote:
> The next version gpio controller on SoCs like rk3576 which support four
> OS operation and four interrupts

...

>  #define GPIO_TYPE_V2		(0x01000C2B)  /* GPIO Version ID 0x01000C2B */
>  #define GPIO_TYPE_V2_1		(0x0101157C)  /* GPIO Version ID 0x0101157C */
> +#define GPIO_TYPE_V2_2		(0x010219C8)  /* GPIO Version ID 0x010219C8 */

These needs a bit of decoding. As far as I can decipher these it's something like

0x01 00 00 00 ???

0x00 xx 00 00 // seems like a subversion, 2.xx

0x00 00 xx xx // seems like a release which is

3115
5500
6600

in decimal representation.

But again, can you make the comments better explaining these cryptic 4-byte
values?

With that done it might be better approach to check the version of the IP.

...

> +	switch (id) {
> +	case GPIO_TYPE_V2:
> +	case GPIO_TYPE_V2_1:
>  		bank->gpio_regs = &gpio_regs_v2;
>  		bank->gpio_type = GPIO_TYPE_V2;
> -	} else {
> +		break;
> +	case GPIO_TYPE_V2_2:
> +		bank->gpio_regs = &gpio_regs_v2;
> +		bank->gpio_type = GPIO_TYPE_V2_2;
> +		break;
> +	default:
>  		bank->gpio_regs = &gpio_regs_v1;
>  		bank->gpio_type = GPIO_TYPE_V1;
> +		pr_info("Note: Use default GPIO_TYPE_V1!\n");

Missed break;

>  	}

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2024-08-23 15:05 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23  3:43 [PATCH v2] gpio: rockchip: Update the GPIO driver Ye Zhang
2024-08-23  3:43 ` Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: avoid division by zero Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  9:27   ` Heiko Stübner
2024-08-23  9:27     ` Heiko Stübner
2024-08-23 14:45   ` Andy Shevchenko
2024-08-23 14:45     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: release reference to device node Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  9:28   ` Heiko Stübner
2024-08-23  9:28     ` Heiko Stübner
2024-08-23 10:52   ` Shawn Lin
2024-08-23 10:52     ` Shawn Lin
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: resolve overflow issues Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  9:34   ` Heiko Stübner
2024-08-23  9:34     ` Heiko Stübner
2024-08-23 10:59   ` Shawn Lin
2024-08-23 10:59     ` Shawn Lin
2024-08-23 14:49     ` Andy Shevchenko
2024-08-23 14:49       ` Andy Shevchenko
2024-08-23 14:48   ` Andy Shevchenko
2024-08-23 14:48     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: resolve underflow issue Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23 14:51   ` Andy Shevchenko
2024-08-23 14:51     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: fix debounce calculate Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: Update debounce config function Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support 'clock-names' from dt nodes Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23 14:56   ` Andy Shevchenko
2024-08-23 14:56     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support new version gpio Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23 13:32   ` Sebastian Reichel
2024-08-23 13:32     ` Sebastian Reichel
2024-08-23 15:05   ` Andy Shevchenko [this message]
2024-08-23 15:05     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: Set input direction when request irq Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23 14:59   ` Andy Shevchenko
2024-08-23 14:59     ` Andy Shevchenko
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: support ACPI Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  5:27   ` Mika Westerberg
2024-08-23  5:27     ` Mika Westerberg
2024-08-23  3:43 ` [PATCH v2] gpio: rockchip: driver works without pinctrl device Ye Zhang
2024-08-23  3:43   ` Ye Zhang
2024-08-23  7:03 ` [PATCH v2] gpio: rockchip: Update the GPIO driver Bartosz Golaszewski
2024-08-23  7:03   ` Bartosz Golaszewski
2024-08-23  7:06 ` Dragan Simic
2024-08-23  7:06   ` Dragan Simic
2024-08-23 15:07   ` Andy Shevchenko
2024-08-23 15:07     ` Andy Shevchenko
2024-08-23  9:33 ` Heiko Stübner
2024-08-23  9:33   ` Heiko Stübner

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=ZsilJZS2_Kvyhs1S@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=elaine.zhang@rock-chips.com \
    --cc=finley.xiao@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tao.huang@rock-chips.com \
    --cc=tim.chen@rock-chips.com \
    --cc=ye.zhang@rock-chips.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.