[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250321014910.4881-1-changhuang.liang@starfivetech.com>
Date: Thu, 20 Mar 2025 18:49:10 -0700
From: Changhuang Liang <changhuang.liang@...rfivetech.com>
To: jirislaby@...nel.org
Cc: aaro.koskinen@....fi,
afaerber@...e.de,
alexandre.belloni@...tlin.com,
alexandre.torgue@...s.st.com,
alim.akhtar@...sung.com,
andreas@...nade.info,
andrew@...econstruct.com.au,
andrew@...n.ch,
angelogioacchino.delregno@...labora.com,
atenart@...nel.org,
baruch@...s.co.il,
bcm-kernel-feedback-list@...adcom.com,
benh@...nel.crashing.org,
changhuang.liang@...rfivetech.com,
chris@...kel.net,
claudiu.beznea@...on.dev,
daniel@...ngy.jp,
eajames@...ux.ibm.com,
festevam@...il.com,
florian.fainelli@...adcom.com,
gregory.clement@...tlin.com,
guoren@...nel.org,
j.neuschaefer@....net,
jcmvbkbc@...il.com,
jernej.skrabec@...il.com,
joel@....id.au,
jonas@...thpole.se,
jonathanh@...dia.com,
kernel@...gutronix.de,
khilman@...libre.com,
kristo@...nel.org,
krzk@...nel.org,
linus.walleij@...aro.org,
linux-kernel@...r.kernel.org,
manivannan.sadhasivam@...aro.org,
mark-pk.tsai@...iatek.com,
matthias.bgg@...il.com,
maz@...nel.org,
mcoquelin.stm32@...il.com,
michal.simek@....com,
miodrag.dinic@...s.com,
nicolas.ferre@...rochip.com,
nm@...com,
paul@...pouillou.net,
piotr.wojtaszczyk@...esys.com,
qinjian@...lus1.com,
rjui@...adcom.com,
rogerq@...nel.org,
ryan_chen@...eedtech.com,
s.hauer@...gutronix.de,
samuel@...lland.org,
sbranden@...adcom.com,
sebastian.hesselbarth@...il.com,
shawnguo@...nel.org,
shorne@...il.com,
ssantosh@...nel.org,
stefan.kristiansson@...nalahti.fi,
talel@...zon.com,
tglx@...utronix.de,
thierry.reding@...il.com,
tony@...mide.com,
tsbogend@...ha.franken.de,
vz@...ia.com,
wens@...e.org
Subject: [PATCH v2 21/57] irqdomain: irqchip: Switch to irq_domain_create_*()
> irq_domain_add_*() interfaces are going away as being obsolete now.
> Switch to the preferred irq_domain_create_*() ones. Those differ in the
> node parameter: They take more generic struct fwnode_handle instead of
> struct device_node. Therefore, of_fwnode_handle() is added around the
> original parameter.
>
> Note some of the users can likely use dev->fwnode directly instead of
> indirect of_fwnode_handle(dev->of_node). But dev->fwnode is not
> guaranteed to be set for all, so this has to be investigated on case to
> case basis (by people who can actually test with the HW).
>
> Signed-off-by: Jiri Slaby (SUSE) <jirislaby@...nel.org>
>
for starfive-jh8100:
Acked-by: Changhuang Liang <changhuang.liang@...rfivetech.com>
Best Regards,
Changhuang
Powered by blists - more mailing lists