Re: [PATCH v2 00/57] irqdomain: Cleanups and Documentation

Andy Shevchenko <[email protected]>
Newsgroups gmane.linux.kernel.iio,gmane.linux.kernel,gmane.comp.freedesktop.amd-gfx,gmane.comp.video.dri.devel,gmane.linux.ports.arm.kernel,gmane.linux.ports.arm.msm,gmane.linux.documentation,gmane.linux.kernel.gpio,gmane.linux.drivers.i2c,gmane.linux.ports.arm.mediatek,gmane.linux.ports.mips,gmane.linux.ports.arm.omap,gmane.linux.kernel.pci,gmane.linux.ports.ppc64.devel,gmane.linux.ports.riscv,gmane.linux.kernel.rpi,gmane.linux.ports.sh.devel,gmane.linux.kernel.arc,gmane.linux.sound,gmane.linux.uml.devel,gmane.linux.kernel.wireless.general,gmane.linux.network,gmane.linux.drivers.platform.x86.devel
Message-ID <CAHp75VfJPgaGyERBaSxSGap+Daeuy8kOjyjg+QkCtzxUydzHiQ@mail.gmail.com>
On Wed, Mar 19, 2025 at 11:30 AM Jiri Slaby (SUSE) <[email protected]> wrote:
>
> Hi,
>
> tl;dr if patches are agreed upon, I ask subsys maintainers to take the
> respective ones via their trees (as they are split per subsys), so that
> the IRQ tree can take only the rest. That would minimize churn/conflicts
> during merges.
>
> ===
>
> While I was reading through the irqdomain code and headers, I found some
> naming and documentation hard to follow or incomplete. Especially the
> naming of _add/_create/_instantiate functions.
>
> I tried to come up with a better state with this patchset:
> * only irq _domain_ (not host),
> * only irq_domain_create*() functions, all taking fwnode uniformly,
>
> Finally, all the irqdomain stuff is now plugged (and generated) into
> Documentation. So that everyone can walk through it at
> https://www.kernel.org/doc/ (once applied, of course).

I am all to support the idea, but in some cases I would think of a bit
more work to be done to get rid of the of_fwnode_handle(np) in favour
of dev_fwnode(dev). Note, this is based on a brief look, I haven't any
example at hand right now.

-- 
With Best Regards,
Andy Shevchenko
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.