From: Samuel Zou <zou_wei@huawei.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: <linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] i2c: Fix missing pci_disable_device() on error in ali1535_setup()
Date: Tue, 8 Jun 2021 19:30:38 +0800 [thread overview]
Message-ID: <f88681e2-8156-5824-8d03-f5004dc489f3@huawei.com> (raw)
In-Reply-To: <20210608114636.65512e28@endymion>
Hi Jean,
Thanks for your review and detailed explanation.
On 2021/6/8 17:46, Jean Delvare wrote:
> Hi Wei,
>
> On Mon, 07 Jun 2021 11:21:08 +0800, Zou Wei wrote:
>> Fix the missing pci_disable_device() before return
>> from ali1535_setup() in the error handling case.
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Zou Wei <zou_wei@huawei.com>
>> ---
>> drivers/i2c/busses/i2c-ali1535.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/i2c/busses/i2c-ali1535.c b/drivers/i2c/busses/i2c-ali1535.c
>> index fb93152..bdbaf79 100644
>> --- a/drivers/i2c/busses/i2c-ali1535.c
>> +++ b/drivers/i2c/busses/i2c-ali1535.c
>> @@ -206,6 +206,7 @@ static int ali1535_setup(struct pci_dev *dev)
>> exit_free:
>> release_region(ali1535_smba, ALI1535_SMB_IOSIZE);
>> exit:
>> + pci_disable_device(dev);
>> return retval;
>> }
>>
>
> We don't actually want to disable the PCI device. Maybe it was already
> enabled before the driver was loaded, and maybe the BIOS needs the
> device when the system is being shut down. You'll notice that we do not
> call pci_disable_device(dev) in ali1535_remove(), so there's no reason
> to do it in the error path.
>
> As a matter of fact the i2c-i801 driver, which is used on the same kind
> of hardware, has the following note in its remove function:
>
> /*
> * do not call pci_disable_device(dev) since it can cause hard hangs on
> * some systems during power-off (eg. Fujitsu-Siemens Lifebook E8010)
> */
>
> So this is a nack from me, sorry.
>
prev parent reply other threads:[~2021-06-08 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 3:21 Zou Wei
2021-06-08 9:46 ` Jean Delvare
2021-06-08 11:30 ` Samuel Zou [this message]
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=f88681e2-8156-5824-8d03-f5004dc489f3@huawei.com \
--to=zou_wei@huawei.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®