Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Miao Wang <shankerwangmiao@gmail.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Yinbo Zhu <zhuyinbo@loongson.cn>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	linux-gpio@vger.kernel.org
Subject: Re: [PATCH RFC 3/4] gpio: loongson-64bit: Add shared interrupt support
Date: Fri, 2 Oct 2026 12:03:06 +0800	[thread overview]
Message-ID: <1E8C13A3-5203-4516-987C-867690208D09@gmail.com> (raw)
In-Reply-To: <CAD++jLn54ts=136H2SXtOfx2n7PukYCQJY9VyKm_h+uxR4=gDw@mail.gmail.com>

Hi,

> 2026年10月2日 03:43,Linus Walleij <linusw@kernel.org> 写道:
> 
> On Thu, Oct 1, 2026 at 7:47 PM Miao Wang <shankerwangmiao@gmail.com> wrote:
> 
>>>>> +       unsigned int usedby : 31;
>>>> 
>>>> Is this a bitmap? Then use a bitmap abstraction.
>>> 
>>> When exclusive is 1, it is a pure number while when exclusive is 0,
>>> it is a bitmap.
>> 
>> To correct my self, usedby is not a bitmap. When exclusive is 1, it stores the using pin
>> id, while when exclusive is zero, it is a counter which stores the number of using pins.
> 
> But what is this mess with using 31 bits for the pin ID?
> 
> How many bits does it *actually* need, using 31 bits looks
> like some way to try to help the compiler to optimize the struct
> which is pointless because the struct isn't even suffixed with
> __packed...

Ah, you are right about it. I intended to reduce the memory that
is needed to hold the struct. However I realized that by using
bit fields, the memory cannot be saved due to the alignment. Will
change in next version.

Cheers,

Miao Wang


  reply	other threads:[~2026-10-02  4:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 16:28 [PATCH RFC 0/4] gpio: loongson-64bit: add interrupt support for more models Miao Wang via B4 Relay
2026-09-25 16:28 ` [PATCH RFC 1/4] gpio: loongson-64bit: Support for irq controller on 2k2000 and 7a2000 Miao Wang via B4 Relay
2026-09-25 16:28 ` [PATCH RFC 2/4] gpio: loongson-64bit: Generalize interrupt controller initialization Miao Wang via B4 Relay
2026-09-25 16:28 ` [PATCH RFC 3/4] gpio: loongson-64bit: Add shared interrupt support Miao Wang via B4 Relay
2026-10-01  8:33   ` Linus Walleij
2026-10-01  8:59     ` Miao Wang
2026-10-01 11:54       ` Linus Walleij
2026-10-01 17:47       ` Miao Wang
2026-10-01 19:43         ` Linus Walleij
2026-10-02  4:03           ` Miao Wang [this message]
2026-09-25 16:28 ` [PATCH RFC 4/4] gpio: loongson-64bit: remove gpio_to_irq() handler Miao Wang via B4 Relay
2026-09-29 13:01 ` [PATCH RFC 0/4] gpio: loongson-64bit: add interrupt support for more models Bartosz Golaszewski
2026-09-29 13:18   ` Miao Wang

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=1E8C13A3-5203-4516-987C-867690208D09@gmail.com \
    --to=shankerwangmiao@gmail.com \
    --cc=brgl@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=zhuyinbo@loongson.cn \
    /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