From: Jiri Slaby <jirislaby@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Greg KH <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
Ralf Baechle <ralf@linux-mips.org>,
stevel@mvista.com
Subject: Re: [PATCH 3/3] pci: gt96100eth use pci probing
Date: Thu, 25 May 2006 12:34:32 +0159 [thread overview]
Message-ID: <4475884F.1020203@gmail.com> (raw)
In-Reply-To: <447584E8.6050903@garzik.org>
Cc: stevel@mvista.com
Jeff Garzik napsal(a):
> Jiri Slaby wrote:
>> Jiri Slaby napsal(a):
>>> Jeff Garzik napsal(a):
>>>> Jiri Slaby wrote:
>>>>> +static int __init gt96100_probe1(struct pci_dev *pdev, int port_num)
>>>>> {
>>>>> struct gt96100_private *gp = NULL;
>>>>> - struct gt96100_if_t *gtif = >96100_iflist[port_num];
>>>>> + struct gt96100_if_t *gtifs = pci_get_drvdata(pdev);
>>>>> + struct gt96100_if_t *gtif = >ifs[port_num];
>>>>> int phy_addr, phy_id1, phy_id2;
>>>>> u32 phyAD;
>>>>> - int retval;
>>>>> + int retval = -ENOMEM;
>>>>> unsigned char chip_rev;
>>>>> struct net_device *dev = NULL;
>>>>> if (gtif->irq < 0) {
>>>>> - printk(KERN_ERR "%s: irq unknown - probing not supported\n",
>>>>> - __FUNCTION__);
>>>>> + dev_err(&pdev->dev, "irq unknown - probing not supported\n");
>>>>> return -ENODEV;
>>>>> }
>>>>> +
>>>>> + retval = pci_enable_device(pdev);
>>>>> + if (retval) {
>>>>> + dev_err(&pdev->dev, "cannot enable pci device\n");
>>>>> + return retval;
>>>>> + }
>>>> bug #1: please confirm pci_enable_device() is OK on this embedded
>>>> hardware
>>> I do not understand too much, did you mean something like this:
>>> } else
>>> dev_info(..., "pci device is enabled now\n");
>>> or?
>> Or..., aha, I got it now. How can I confirm?
>
> Asking the maintainer would be a good first step.
Hello,
can you confirm, if calling pci_enable_device is safe for this (gt96100eth) device?
thanks,
--
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
next prev parent reply other threads:[~2006-05-25 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060525003151.598EAC7C19@atrey.karlin.mff.cuni.cz>
2006-05-25 0:52 ` [PATCH 3/3] pci: gt96100eth use pci probing Jeff Garzik
2006-05-25 10:13 ` Jiri Slaby
2006-05-25 10:17 ` Jiri Slaby
2006-05-25 10:20 ` Jeff Garzik
2006-05-25 10:35 ` Jiri Slaby [this message]
2006-05-25 10:27 ` Jeff Garzik
2006-05-25 10:32 ` Jiri Slaby
2006-05-25 10:35 ` Jeff Garzik
2006-05-25 10:31 ` Jiri Slaby
2006-05-25 10:41 ` Ralf Baechle
2006-05-25 20:36 ` Jiri Slaby
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=4475884F.1020203@gmail.com \
--to=jirislaby@gmail.com \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=ralf@linux-mips.org \
--cc=stevel@mvista.com \
/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