pnp_assign_resources() issue

Adam,

I'm having some difficulty understanding why failure to probe for a resource
(in the given case, a DMA channel, but the issue is perhaps more generic) must
always result in failure of the probing of the requesting device. In any case,
the driver is required to call request_dma(), and in many cases the driver may
know how to deal with the device even if that call fails (in the given case,
parport_pc can be used as an example). Shouldn't therefore pnp_assign_dma()
be made never fail, and just mark the resource as unset/disabled if none of
the options were available? I realize drivers may not really look at these flags,
but I'd think this is a driver issue then and shouldn't keep the framework
from supporting as many different systems as possible.

Thanks, Jan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: [PATCH 0/2] Kexec jump: The first step to kexec base hibernation
• Next by Date: Re: [PATCH] lguest: disable SYSENTER for guests
• Previous by thread: Re: [Linux-fbdev-devel] [PATCH 0/4] fbdev: uvesafb
• Next by thread: Re: [Linux-fbdev-devel] [PATCH 1/4] fbdev: make fb_find_mode look for a mode with the highest refresh rate
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]