devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chen Wang <unicorn_wang@outlook.com>,
	Inochi Amaoto <inochiama@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	sophgo@lists.linux.dev, Yixun Lan <dlan@gentoo.org>,
	Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH v3 4/4] irqchip/sg2042-msi: Add the Sophgo SG2044 MSI interrupt controller
Date: Wed, 09 Apr 2025 20:52:40 +0200	[thread overview]
Message-ID: <87o6x5tbev.ffs@tglx> (raw)
In-Reply-To: <MA0P287MB2262DBC84878347B78CA50ECFEB42@MA0P287MB2262.INDP287.PROD.OUTLOOK.COM>

On Wed, Apr 09 2025 at 15:53, Chen Wang wrote:

> On 2025/4/8 13:01, Inochi Amaoto wrote:
>> Add support for Sophgo SG2044 MSI interrupt controller.
>>
>> Signed-off-by: Inochi Amaoto <inochiama@gmail.com>
>> Reviewed-by: Chen Wang <unicorn_wang@outlook.com>
>> ---
>>   drivers/irqchip/irq-sg2042-msi.c | 61 ++++++++++++++++++++++++++++++--
>>   1 file changed, 58 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/irqchip/irq-sg2042-msi.c b/drivers/irqchip/irq-sg2042-msi.c
>> index 30a1d2bfd474..2935ca213306 100644
>> --- a/drivers/irqchip/irq-sg2042-msi.c
>> +++ b/drivers/irqchip/irq-sg2042-msi.c
>> @@ -19,8 +19,6 @@
>>   
>>   #include "irq-msi-lib.h"
>>   
>> -#define SG2042_MAX_MSI_VECTOR	32
>> -
>>   struct sg204x_msi_chip_info {
>>   	const struct irq_chip		*irqchip;
>>   	const struct msi_parent_ops	*parent_ops;
>> @@ -44,7 +42,7 @@ struct sg204x_msi_chipdata {
>>   	u32					irq_first;
>>   	u32					num_irqs;
>>   
>> -	DECLARE_BITMAP(msi_map, SG2042_MAX_MSI_VECTOR);
>> +	unsigned long				*msi_map;
>
> Regarding the common parts of SG2042 and SG2044, I noticed that you 
> changed DECLARE_BITMAP back to dynamic application. If there is a next 
> version, I suggest you mention it in the commit information.

Actually that should be part of the previous patch which prepares for
configurable initialization. Then this one just adds the new variant.

Thanks,

        tglx



  reply	other threads:[~2025-04-09 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  5:01 [PATCH v3 0/4] irqchip/sg2042-msi: Add the Sophgo SG2044 MSI interrupt controller Inochi Amaoto
2025-04-08  5:01 ` [PATCH v3 1/4] dt-bindings: interrupt-controller: Add Sophgo SG2044 MSI controller Inochi Amaoto
2025-04-08  5:01 ` [PATCH v3 2/4] irqchip/sg2042-msi: rename generic function and structure Inochi Amaoto
2025-04-09  7:53   ` Chen Wang
2025-04-08  5:01 ` [PATCH v3 3/4] irqchip/sg2042-msi: introduce configurable chipinfo for sg2042 Inochi Amaoto
2025-04-09  7:44   ` Chen Wang
2025-04-08  5:01 ` [PATCH v3 4/4] irqchip/sg2042-msi: Add the Sophgo SG2044 MSI interrupt controller Inochi Amaoto
2025-04-09  7:53   ` Chen Wang
2025-04-09 18:52     ` Thomas Gleixner [this message]
2025-04-10  0:51       ` Inochi Amaoto
2025-04-08  5:04 ` [PATCH v3 0/4] " Inochi Amaoto
2025-04-09  7:58 ` Chen 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=87o6x5tbev.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@gentoo.org \
    --cc=inochiama@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=looong.bin@gmail.com \
    --cc=robh@kernel.org \
    --cc=sophgo@lists.linux.dev \
    --cc=unicorn_wang@outlook.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;
as well as URLs for NNTP newsgroup(s).