Re: [PATCH v2 0/3] irqchip/sg2042-msi: Set irq type according to DT configuration

Chen Wang <[email protected]>
Newsgroups dev.linux.lists.sophgo,org.infradead.lists.linux-riscv,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <MAUPR01MB110729FEE220A79D00B52121CFE07A@MAUPR01MB11072.INDPRD01.PROD.OUTLOOK.COM>
Hi, Thomas,

Would you please pick this patchset?

P.S. Since the modification of the DTS part is closely dependent on the 
modification of the driver part, I am not sure whether you are willing 
to pick these three patches together, or just pick the driver part and 
leave the DTS part to me?

Thanks,

Chen

On 8/26/2025 9:09 AM, Chen Wang wrote:
> From: Chen Wang <[email protected]>
>
> The original MSI interrupt type was hard-coded, which was not a good idea.
> Now it is changed to read the device tree configuration and then set the
> interrupt type.
>
> This patchset is based on irq/drivers branch of tip.
>
> ---
>
> Changes in v2:
>    The patch series is based on irq/drivers branch of tip.
>
>    Reverted the change to obtain params of "msi-ranges"; it's better not to
>    assume the value of "#interrupt-cells" is 2, even though it's known to be
>    the case. Thanks to Inochi for the comments.
>
> Changes in v1:
>    The patch series is based on irq/drivers branch of tip. You can simply review
>    or test the patches at the link [1].
>
> Link: https://lore.kernel.org/linux-riscv/[email protected]/ [1]
> ---
>
> Chen Wang (3):
>    irqchip/sg2042-msi: Set irq type according to DT configuration
>    riscv: sophgo: dts: sg2042: change msi irq type to
>      IRQ_TYPE_EDGE_RISING
>    riscv: sophgo: dts: sg2044: change msi irq type to
>      IRQ_TYPE_EDGE_RISING
>
>   arch/riscv/boot/dts/sophgo/sg2042.dtsi | 2 +-
>   arch/riscv/boot/dts/sophgo/sg2044.dtsi | 2 +-
>   drivers/irqchip/irq-sg2042-msi.c       | 7 +++++--
>   3 files changed, 7 insertions(+), 4 deletions(-)
>
>
> base-commit: 8ff1c16c753e293c3ba20583cb64f81ea7b9a451
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.