mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@kernel.org>
To: "Ian Abbott" <abbotti@mev.co.uk>,
	"Niklas Schnelle" <schnelle@linux.ibm.com>,
	linux-kernel@vger.kernel.org
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Hartley Sweeten" <hsweeten@visionengravers.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] comedi: Fix driver module dependencies since HAS_IOPORT changes
Date: Mon, 04 Sep 2023 09:34:01 -0400	[thread overview]
Message-ID: <8728313c-997a-46c1-8225-d57369e9292c@app.fastmail.com> (raw)
In-Reply-To: <ab5baa69-ae3c-4973-8563-670395a3c976@mev.co.uk>

On Mon, Sep 4, 2023, at 08:01, Ian Abbott wrote:
> On 04/09/2023 12:23, Niklas Schnelle wrote:
>> On Mon, 2023-09-04 at 11:10 +0100, Ian Abbott wrote:
>
> Thanks for the confirmation.  Will it be safe to assume that anything 
> that selects ISA will also select HAS_IOPORT?  That is trivially the 
> case for arch/{alpha,arm,x86}; arch/mips explicitly selects HAS_IOPORT 
> if ISA is selected; arch/powerpc explicitly selects HAS_IOPORT if PCI is 
> selected and it is only possible to configure ISA if PPC_CHRP is 
> configured which selects FORCE_PCI and therefore selects PCI and 
> therefore selects HAS_IOPORT; arch/um does not select HAS_IOPORT and 
> although it has a 'config ISA', nothing appears to select it.  None of 
> the remaining arch/* have 'select ISA'.

Yes, I think that will always be a safe assumption, ISA without port I/O
is just not a sensible configuration. A few of the later ISA devices use
PCI style memory mapped I/O, but I can't think of any driver that doesn't
also require port I/O, and you wouldn't find ISA slots in a system that
lacks support for port I/O.

      Arnd

  parent reply	other threads:[~2023-09-04 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 19:26 Ian Abbott
2023-09-03 15:49 ` Arnd Bergmann
2023-09-04 10:10   ` Ian Abbott
2023-09-04 11:23     ` Niklas Schnelle
2023-09-04 12:01       ` Ian Abbott
2023-09-04 12:22         ` Ian Abbott
2023-09-04 13:34         ` Arnd Bergmann [this message]
2023-10-10  0:01           ` Maciej W. Rozycki
2023-09-04 13:30     ` Arnd Bergmann
2023-09-04 13:48 ` Ian Abbott

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=8728313c-997a-46c1-8225-d57369e9292c@app.fastmail.com \
    --to=arnd@kernel.org \
    --cc=abbotti@mev.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schnelle@linux.ibm.com \
    --cc=stable@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

all inboxes | Powered by JetHome®