From: "Raj, Ashok" <ashok.raj@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
james puthukattukaran <james.puthukattukaran@oracle.com>,
Yinghai Lu <yinghai.lu@oracle.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
ashok.raj@intel.com
Subject: Re: [PATCH] PCI, pciehp: Reuse set_slot_off()
Date: Fri, 24 Feb 2017 09:17:43 -0800 [thread overview]
Message-ID: <20170224171743.GA4964@otc-nc-03> (raw)
In-Reply-To: <20170224065435.14954-1-yinghai@kernel.org>
Hi Yinghai
On Thu, Feb 23, 2017 at 10:54:35PM -0800, Yinghai Lu wrote:
> +++ linux-2.6/drivers/pci/hotplug/pciehp_ctrl.c
> @@ -71,9 +71,6 @@ static void set_slot_off(struct controll
> */
> msleep(1000);
> }
> -
> - pciehp_green_led_off(pslot);
> - pciehp_set_attention_status(pslot, 1);
Re using set_slot_off() in remove_board() make sense.. but i'm not sure
why these are pulled out? It seems to be functionally complete
when these are done in set_slot_off().
> }
>
> /**
> @@ -126,6 +123,8 @@ static int board_added(struct slot *p_sl
>
> err_exit:
> set_slot_off(ctrl, p_slot);
> + pciehp_green_led_off(p_slot);
> + pciehp_set_attention_status(p_slot, 1);
> return retval;
> }
>
> @@ -142,16 +141,7 @@ static int remove_board(struct slot *p_s
> if (retval)
> return retval;
>
> - if (POWER_CTRL(ctrl)) {
> - pciehp_power_off_slot(p_slot);
> -
> - /*
> - * After turning power off, we must wait for at least 1 second
> - * before taking any action that relies on power having been
> - * removed from the slot/adapter.
> - */
> - msleep(1000);
> - }
> + set_slot_off(ctrl, p_slot);
>
> /* turn off Green LED */
> pciehp_green_led_off(p_slot);
Don't we need the pciehp_set_attention_status() here?
Cheers,
Ashok
next prev parent reply other threads:[~2017-02-24 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 6:54 Yinghai Lu
2017-02-24 17:17 ` Raj, Ashok [this message]
2017-02-24 18:39 ` Yinghai Lu
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=20170224171743.GA4964@otc-nc-03 \
--to=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=james.puthukattukaran@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai.lu@oracle.com \
--cc=yinghai@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®