Re: [PATCH 4/4] sh: machvec: remove custom ioport_{un,}map()
"Arnd Bergmann" <[email protected]>
| Newsgroups | gmane.linux.ports.sh.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Sep 14, 2023, at 08:23, John Paul Adrian Glaubitz wrote: > On Wed, 2023-09-13 at 16:30 +0200, Arnd Bergmann wrote: >> > In the meantime, there is a v2, which I wasn't aware of when I wrote >> > my previous email, so perhaps my comment is no longer valid. >> > "[RFC PATCH v2 00/30] Device Tree support for SH7751 based board" >> > https://lore.kernel.org/linux-sh/[email protected] >> >> Right, it looks like the GENERIC_IOMAP part if gone from that >> series, and I also see that the PCI host bridge does not actually >> map the port I/O window. That's usually fine because very few >> drivers actually need it, and it also means that there should be >> no need for GENERIC_IOMAP or the simpler alternative. >> >> The first version probably only did it accidentally, which is a >> common mistake, and I think the ones for hexagon, m68k, and >> mips can probably be removed as well with some simplifiations. >> >> x86 and ia64 want GENERIC_IOMAP because they require using >> custom instructions for accessing IORESOURCE_IO registers, >> but it's not really generic. > > Would you suggest to apply your series before or after Yoshinori's series to > convert arch/sh to device trees? If you want it to go in before the conversion, > could you rebase your series against v6.6-rc1? > > I'm asking because the current version did not apply against v6.5-rc2. I've rebased and resent the series now, with no other changes added in. I expect that you can apply it in either order now if the other series no longer relies on GENERIC_IOMAP. Arnd