From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Brian Cain <bcain@quicinc.com>
Cc: "linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>,
Arnd Bergmann <arnd@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without HAS_IOPORT support
Date: Tue, 01 Oct 2024 10:04:13 +0200 [thread overview]
Message-ID: <72bafe6a2520b976ee99250dd2548a74082796b6.camel@linux.ibm.com> (raw)
In-Reply-To: <CH3PR02MB1024732DF7A1A1FF81535A7D0B8762@CH3PR02MB10247.namprd02.prod.outlook.com>
On Mon, 2024-09-30 at 16:35 +0000, Brian Cain wrote:
>
> > -----Original Message-----
> > From: Niklas Schnelle <schnelle@linux.ibm.com>
> > Sent: Monday, September 30, 2024 10:51 AM
> > To: Brian Cain <bcain@quicinc.com>
> > Cc: linux-hexagon@vger.kernel.org; Arnd Bergmann <arnd@kernel.org>; Heiko
> > Carstens <hca@linux.ibm.com>; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without
> > HAS_IOPORT support
> >
> > WARNING: This email originated from outside of Qualcomm. Please be wary of
> > any links or attachments, and do not enable macros.
> >
> > On Wed, 2024-04-03 at 15:37 +0000, Brian Cain wrote:
> > >
> > > > -----Original Message-----
> > > > From: Niklas Schnelle <schnelle@linux.ibm.com>
> > > > Sent: Wednesday, April 3, 2024 10:22 AM
> > > > To: Brian Cain <bcain@quicinc.com>
> > > > Cc: linux-hexagon@vger.kernel.org; Arnd Bergmann <arnd@kernel.org>;
> > > > Heiko Carstens <hca@linux.ibm.com>; linux-kernel@vger.kernel.org
> > > > Subject: Re: [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without
> > > > HAS_IOPORT support
> > > >
> > > > WARNING: This email originated from outside of Qualcomm. Please be wary
> > > > of any links or attachments, and do not enable macros.
> > > >
> > > > On Wed, 2024-04-03 at 14:51 +0000, Brian Cain wrote:
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Niklas Schnelle <schnelle@linux.ibm.com>
> > > > > > Sent: Wednesday, April 3, 2024 8:25 AM
> > > > > > To: Brian Cain <bcain@quicinc.com>
> > > > > > Cc: linux-hexagon@vger.kernel.org; Arnd Bergmann <arnd@kernel.org>;
> > > > > > Heiko Carstens <hca@linux.ibm.com>; linux-kernel@vger.kernel.org;
> > > > Niklas
> > > > > > Schnelle <schnelle@linux.ibm.com>
> > > > > > Subject: [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without
> > > > > > HAS_IOPORT support
> > > > > >
> > > > > > WARNING: This email originated from outside of Qualcomm. Please be
> > > > wary
> > > > > > of any links or attachments, and do not enable macros.
> > > > > >
> > > > > > In a future patch HAS_IOPORT=n will disable inb()/outb() and friends at
> > > > > > compile time. As hexagon does not support I/O port access it also
> > > > > > the GENERIC_IOMAP mechanism of dynamically choosing between I/O
> > > > port
> > > > > > and
> > > > > > MMIO access doesn't work so don't select it.
> > > > > >
> > > > > > Co-developed-by: Arnd Bergmann <arnd@kernel.org>
> > > > > > Signed-off-by: Arnd Bergmann <arnd@kernel.org>
> > > > > > Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
> > > > > > ---
> > > > > > arch/hexagon/Kconfig | 1 -
> > > > > > 1 file changed, 1 deletion(-)
> > > > > >
> > > > > > diff --git a/arch/hexagon/Kconfig b/arch/hexagon/Kconfig
> > > > > > index e233b5efa276..5ea1bf4b7d4f 100644
> > > > > > --- a/arch/hexagon/Kconfig
> > > > > > +++ b/arch/hexagon/Kconfig
> > > > > > @@ -31,7 +31,6 @@ config HEXAGON
> > > > > > select HAVE_ARCH_TRACEHOOK
> > > > > > select NEED_SG_DMA_LENGTH
> > > > > > select NO_IOPORT_MAP
> > > > > > - select GENERIC_IOMAP
> > > > > > select GENERIC_IOREMAP
> > > > > > select GENERIC_SMP_IDLE_THREAD
> > > > > > select STACKTRACE_SUPPORT
> > > > >
> > > > > Reviewed-by: Brian Cain <bcain@quicinc.com>
> > > > >
> > > >
> > > > Thanks for the R-b, which tree should take this? If you have other
> > > > hexagon changes for v6.10 I think it would be easiest to take this
> > > > together with those. As mentioned in the cover letter the per-subsystem
> > >
> > > I don't have other changes planned for v6.10 but I'm happy to take the
> > change in my tree.
> > >
> > > > changes are all independent until HAS_IOPORT=n actually disables
> > > > inb()/outb() which Arnd will take once all the subsystems are covered.
> > > >
> > > > Thanks,
> > > > Niklas
> >
> > Hi Brian,
> >
> > With 2 more of my HAS_IOPORT patches having gone into v6.12-rc1 I just
> > noticed that this one seems to have fallen into the cracks. This is
> > probably my fault for not properly confirming that I'd be happy for you
> > to take it. Do you want me to resend a new version rebased on v6.12-
> > rc1?
>
> Oh, sorry! Yes, if you could resend a rebased one I'll make sure I am able to land it.
>
> -Brian
Hi Brian,
I just tried with
b4 shazam '<20240403132447.719833-2-schnelle@linux.ibm.com>'
and this patch actually still applies cleanly and matches the result I
got rebasing the whole series[0]. So on second thought taking it from
here directly might still be the easiest. That said I'll have to send
out the other 4 outstanding patches required for the final inb()
compile time switch, so if you prefer I can still resend too.
Thanks
Niklas
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/niks/linux.git/log/?h=has_ioport
next prev parent reply other threads:[~2024-10-01 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:24 [PATCH 0/1] hexagon: Handle HAS_IOPORT dependencies Niklas Schnelle
2024-04-03 13:24 ` [PATCH 1/1] hexagon: Don't select GENERIC_IOMAP without HAS_IOPORT support Niklas Schnelle
2024-04-03 14:51 ` Brian Cain
2024-04-03 15:22 ` Niklas Schnelle
2024-04-03 15:37 ` Brian Cain
2024-09-30 15:50 ` Niklas Schnelle
2024-09-30 16:35 ` Brian Cain
2024-10-01 8:04 ` Niklas Schnelle [this message]
2024-10-02 9:34 ` Arnd Bergmann
2024-10-02 11:54 ` Niklas Schnelle
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=72bafe6a2520b976ee99250dd2548a74082796b6.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=arnd@kernel.org \
--cc=bcain@quicinc.com \
--cc=hca@linux.ibm.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).