diff options
author | Dominik Brodowski <linux@dominikbrodowski.net> | 2010-07-29 09:50:55 -0400 |
---|---|---|
committer | Dominik Brodowski <linux@dominikbrodowski.net> | 2010-09-29 11:20:21 -0400 |
commit | e8405f0f617856de0ceb7d04e65b663051451544 (patch) | |
tree | 06e9cd27419a40587bcec19b71010e52b7dfcba4 /drivers/net/wireless/hostap | |
parent | fb49fa533f9d211994c33efb752ffa5b30033729 (diff) |
pcmcia: move Vpp setup to struct pcmcia_device
Some drivers prefer to explicitly set Vpp. Instead of passing the
voltage inside config_req_t, store it in struct pcmcia_device.
CC: linux-ide@vger.kernel.org
CC: netdev@vger.kernel.org
CC: linux-mtd@lists.infradead.org
CC: linux-wireless@vger.kernel.org
CC: linux-serial@vger.kernel.org
CC: linux-usb@vger.kernel.org
CC: linux-scsi@vger.kernel.org
Acked-by: Gustavo F. Padovan <padovan@profusion.mobi> (for drivers/bluetooth)
Tested-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Diffstat (limited to 'drivers/net/wireless/hostap')
-rw-r--r-- | drivers/net/wireless/hostap/hostap_cs.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/drivers/net/wireless/hostap/hostap_cs.c b/drivers/net/wireless/hostap/hostap_cs.c index ba54d1b04d22..3f35dd4438ca 100644 --- a/drivers/net/wireless/hostap/hostap_cs.c +++ b/drivers/net/wireless/hostap/hostap_cs.c | |||
@@ -508,9 +508,9 @@ static int prism2_config_check(struct pcmcia_device *p_dev, | |||
508 | } | 508 | } |
509 | 509 | ||
510 | if (cfg->vpp1.present & (1 << CISTPL_POWER_VNOM)) | 510 | if (cfg->vpp1.present & (1 << CISTPL_POWER_VNOM)) |
511 | p_dev->conf.Vpp = cfg->vpp1.param[CISTPL_POWER_VNOM] / 10000; | 511 | p_dev->vpp = cfg->vpp1.param[CISTPL_POWER_VNOM] / 10000; |
512 | else if (dflt->vpp1.present & (1 << CISTPL_POWER_VNOM)) | 512 | else if (dflt->vpp1.present & (1 << CISTPL_POWER_VNOM)) |
513 | p_dev->conf.Vpp = dflt->vpp1.param[CISTPL_POWER_VNOM] / 10000; | 513 | p_dev->vpp = dflt->vpp1.param[CISTPL_POWER_VNOM] / 10000; |
514 | 514 | ||
515 | /* Do we need to allocate an interrupt? */ | 515 | /* Do we need to allocate an interrupt? */ |
516 | p_dev->conf.Attributes |= CONF_ENABLE_IRQ; | 516 | p_dev->conf.Attributes |= CONF_ENABLE_IRQ; |
@@ -605,9 +605,9 @@ static int prism2_config(struct pcmcia_device *link) | |||
605 | /* Finally, report what we've done */ | 605 | /* Finally, report what we've done */ |
606 | printk(KERN_INFO "%s: index 0x%02x: ", | 606 | printk(KERN_INFO "%s: index 0x%02x: ", |
607 | dev_info, link->conf.ConfigIndex); | 607 | dev_info, link->conf.ConfigIndex); |
608 | if (link->conf.Vpp) | 608 | if (link->vpp) |
609 | printk(", Vpp %d.%d", link->conf.Vpp / 10, | 609 | printk(", Vpp %d.%d", link->vpp / 10, |
610 | link->conf.Vpp % 10); | 610 | link->vpp % 10); |
611 | if (link->conf.Attributes & CONF_ENABLE_IRQ) | 611 | if (link->conf.Attributes & CONF_ENABLE_IRQ) |
612 | printk(", irq %d", link->irq); | 612 | printk(", irq %d", link->irq); |
613 | if (link->resource[0]) | 613 | if (link->resource[0]) |