From: matthieu castet <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org, syrjala@sci.fi, jt@hpl.hp.com
Cc: Adam Belay <ambx1@neo.rr.com>
Subject: Re: [PATCH] smsc-ircc2: Add PnP support.
Date: Thu, 18 Nov 2004 19:42:07 +0100 [thread overview]
Message-ID: <419CECFF.2090608@free.fr> (raw)
Hi,
I had also done a pnp patch for the smsc-ircc2 and irport 3 months ago.
Unfortunaly I don't remember where I put the patches, certainly on the
laptop that it is in my parent home.
> On Wed, Nov 17, 2004 at 03:20:47PM -0800, Jean Tourrilhes wrote:
> > Ville wrote :
> > > Add PnP support to smsc-ircc2 driver.
> > > Briefly tested with irdadump on a Dell Inpsiron 7000.
> >
> > OnThanks for the patch. I slightly moved you code around, you'll
> > find my version of your patch on my web page.
> >
> > OnNow, a few comments...
> >
> > On1) I don't have any SmSC chipset around, so I can't do any
> > testing. I would appreciate other people to test your patch. Also,
> > make sure I did not introduce mistakes in my version of the patch.
>
> Your version works fine (irdadump works).
>
> > On2) I tried to apply the same code to NSC. It did not manage to
> > read the ressource properly, and therefore the PnP code disabled the
> > hardware, and I was no longer able to get it running (short of a
> > reboot of the computer). The nsc-ircc has only one i/o region (dumb
> > nsc).
>
try to do an "echo auto > /sys/bus/pnp/device_number/resources"
It will reenable the device.
> I have a machine with nsc-ircc here so I think I'll try that too.
>
> > OnThe issue there is that if a smsc chipset has a valid PnP ID
> > but somehow the pnp_probe fails to set it up, then the regular probe
> > won't be able to configure it. This makes me nervous.
> >
Yes that's the problem this pnp, if the probe failed it disable the
device resource.
When I do my patch I encounter the problem : I called pnp driver after
smsc_ircc_look_for_chips, so all the resources where already reserved,
and the pnp probe failed and it disable the resource, and the device
found with the traditional smsc_ircc_look_for_chips doesn't work.
So in my patch if I register pnp devices, I don't run
smsc_ircc_look_for_chips like it is done for (ircc_fir>0)&&(ircc_sir>0)
case.
> > On3) If the ressources are markes as disabled, you just quit
> > with an error. Compouded with (2), this makes me doubly
> > nervous. Wouldn't it be possible to forcefully enable those
ressources ?
pnp should call automatiquely pnp_activate_dev() before probing the
driver, so the resource should be activated. Have you got an example
where the resource wheren't activated ?
> > OnThe idea there is that more and more IrDA devices are comming
> > disabled in BIOS with no BIOS entry to enable them. Enabling those
> > ressources would fix that and possible make smc-init redundant (I
wish).
>
> pnp_activate_dev() should probably be used to enable the device but
it was
> only used by ISAPNP drivers so I didn't use it in this patch.
>
> I must admit that I really don't know much about the PNP subsystem. I
> used the parport_pc driver as a guide. I've CC'd Adam Belay and
> linux-kernel in the hopes that someone can help with this stuff.
next reply other threads:[~2004-11-19 1:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 18:42 matthieu castet [this message]
2004-11-18 18:55 ` [PATCH] smsc-ircc2: Add PnP support Jean Tourrilhes
2004-11-18 19:49 ` matthieu castet
2004-11-18 20:41 ` Ville Syrjälä
2004-11-18 23:02 ` Adam Belay
2004-11-19 15:27 ` Meelis Roos
2004-11-19 15:53 ` matthieu castet
2004-11-19 15:57 ` matthieu castet
2004-11-19 16:15 ` Meelis Roos
2004-11-19 16:22 ` Meelis Roos
2004-11-19 17:28 ` matthieu castet
2004-11-19 17:34 ` Meelis Roos
[not found] ` <Pine.SOC.4.61.0411191934070.29328-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2004-11-19 18:29 ` matthieu castet
2004-11-19 18:29 ` matthieu castet
[not found] ` <419E3B7A.4000904-GANU6spQydw@public.gmane.org>
2004-11-19 23:09 ` Meelis Roos
2004-11-19 23:09 ` Meelis Roos
2004-11-20 9:50 ` matthieu castet
2004-11-21 17:50 ` Meelis Roos
2004-11-21 18:16 ` matthieu castet
2004-11-21 18:51 ` Meelis Roos
2004-11-21 19:21 ` matthieu castet
2004-11-21 20:20 ` matthieu castet
2004-11-22 1:29 ` Li Shaohua
2004-11-22 8:37 ` Meelis Roos
2004-11-26 16:02 ` matthieu castet
2004-11-26 18:19 ` Meelis Roos
2004-11-27 0:50 ` matthieu castet
2004-11-27 12:15 ` Meelis Roos
2004-11-27 14:02 ` matthieu castet
2004-11-27 18:24 ` Meelis Roos
2004-11-27 18:58 ` matthieu castet
2004-11-27 19:25 ` matthieu castet
2004-11-27 19:39 ` Meelis Roos
2004-11-22 8:39 ` Meelis Roos
2004-11-22 8:42 ` Meelis Roos
2004-11-22 8:38 ` Meelis Roos
[not found] ` <Pine.SOC.4.61.0411200102580.12992-ptEonEWSGqKptlylMvRsHA@public.gmane.org>
2004-11-20 11:43 ` Ville Syrjälä
2004-11-20 11:43 ` [ACPI] " Ville Syrjälä
2004-11-20 11:57 ` matthieu castet
[not found] <20041117232047.GA28061@bougret.hpl.hp.com>
2004-11-18 3:52 ` Ville Syrjälä
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=419CECFF.2090608@free.fr \
--to=castet.matthieu@free.fr \
--cc=ambx1@neo.rr.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syrjala@sci.fi \
/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.