All of lore.kernel.org
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: tedheadster <tedheadster@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems
Date: Fri, 2 Dec 2016 16:24:36 +0000	[thread overview]
Message-ID: <20161202162436.3631a367@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAP8WD_bPns6hGPWUUGbRd_20+bHX460p5szrfCP4bKr9k76wsQ@mail.gmail.com>

On Fri, 2 Dec 2016 08:37:04 -0500
tedheadster <tedheadster@gmail.com> wrote:

> Alan,
> 
> >> Alan,
> >>   on my hardware it grabbed all those interrupts, showing up in
> >> /proc/interrupts very clearly.  
> >
> > Do you have a dmesg of the boot ?
> >  
> 
> Here is the relevant dmesg information and also the /proc/interrupts results:

That's very strange. The legacy code should be seeing that no devices are
present and then dropping the controller

        /* Nothing found means we drop the port as its probably not there */

        ret = -ENODEV;
        ata_for_each_dev(dev, &ap->link, ALL) {
                if (!ata_dev_absent(dev)) {
                        legacy_host[probe->slot] = host;
                        ld->platform_dev = pdev;
                        return 0;
                }
        }
        ata_host_detach(host);


so this ought to be triggered and free up the interface and the IRQ

Alan

  reply	other threads:[~2016-12-02 16:24 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 17:53 [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems Matthew Whitehead
2016-11-29 19:41 ` Tejun Heo
2016-11-29 20:12   ` tedheadster
2016-11-29 20:46     ` Tejun Heo
2016-11-30 13:06       ` Bartlomiej Zolnierkiewicz
2016-11-30 17:13         ` tedheadster
2016-11-30 13:11 ` Sergei Shtylyov
2016-11-30 14:53   ` One Thousand Gnomes
2016-11-30 15:03     ` tedheadster
2016-11-30 18:15       ` One Thousand Gnomes
2016-12-02 13:37         ` tedheadster
2016-12-02 16:24           ` One Thousand Gnomes [this message]
2016-11-30 20:22       ` Tejun Heo
     [not found]         ` <CAP8WD_bZWeLBhLXqJG5uDwBe+zBubw+A+ecSuaihOuwvw9QoCQ@mail.gmail.com>
2016-12-02 17:07           ` Tejun Heo
2016-12-05 14:19             ` tedheadster
2016-12-05 19:23               ` Tejun Heo
     [not found]                 ` <CAP8WD_becq+h2=-g7t-6Pp1psmkCCvdB0YUcg+wYPocUP4dYdw@mail.gmail.com>
2016-12-12 17:01                   ` Tejun Heo
     [not found]                     ` <CAP8WD_YMtnsuYmJHGz1eLmrQNemsB1Z6Soyb6f72brAfMNUNeg@mail.gmail.com>
2016-12-20  2:12                       ` tedheadster
2016-12-22 16:37                         ` Tejun Heo
2016-12-22 17:14                           ` tedheadster
2016-12-22 17:19                             ` Tejun Heo
2016-12-22 18:30                             ` tedheadster
2016-12-22 19:22                               ` Tejun Heo
2017-01-03 17:34                                 ` One Thousand Gnomes
     [not found]                                   ` <CAP8WD_bS61spyQkd7cvktFf_dPc0wgNZ8qEa7GVrXgUobHQdvw@mail.gmail.com>
2017-01-19 21:37                                     ` Tejun Heo
2017-01-20 17:08                                       ` tedheadster
2017-01-20 19:19                                         ` Tejun Heo
2017-01-20 19:38                                           ` Tejun Heo
2017-01-23 23:36                                             ` Gwendal Grignou
2017-01-23 23:57                                               ` tedheadster
2017-01-24 16:19                                                 ` Tejun Heo
2017-01-27  3:01                                                   ` tedheadster
2017-02-07 20:21                                                     ` Gwendal Grignou
2017-02-08 19:43                                                       ` Tejun Heo
2017-02-09 23:49                                                         ` Gwendal Grignou
2017-02-10  0:36                                                           ` tedheadster
2017-02-10 13:19                                                             ` Tejun Heo
2017-02-23 19:26                                                               ` tedheadster
2017-03-03 17:00                                                                 ` [PATCH] libata: transport: Remove circular dependency at free time Gwendal Grignou
2017-03-03 18:28                                                                   ` Sergei Shtylyov
2017-03-03 18:36                                                                     ` Tejun Heo
2017-03-06 20:09                                                                   ` Tejun Heo
2017-03-06 20:11                                                                     ` Sergei Shtylyov
2017-03-06 20:26                                                                       ` Tejun Heo
2017-01-24 15:57                                               ` [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems Tejun Heo
2016-12-12 12:21               ` Bartlomiej Zolnierkiewicz
2016-11-30 13:12 ` Bartlomiej Zolnierkiewicz
2016-11-30 13:15 ` Sergei Shtylyov

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=20161202162436.3631a367@lxorguk.ukuu.org.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=tedheadster@gmail.com \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.