From: Ludwig Petrosyan <ludwig.petrosyan@desy.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Paulo Fortuna Carvalho <pricardofc@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Hot add a PCIe device driver upon hotplug event
Date: Wed, 28 Jan 2015 08:51:36 +0100 [thread overview]
Message-ID: <54C89508.3080001@desy.de> (raw)
In-Reply-To: <CAErSpo4EeEAA-ci1EfSKNijUJA_4uLMu+WU7ORpQPeR9T9Rr8g@mail.gmail.com>
Hi Bjorn
yes this that are refer, more detailed version was in previous Workshop
https://indico.desy.de/getFile.py/access?contribId=5&sessionId=1&resId=0&materialId=slides&confId=7866
and additionally was presentation about driver part
https://indico.desy.de/getFile.py/access?contribId=32&sessionId=9&resId=0&materialId=slides&confId=10329
I hope this will help and may be I will get some feedback to improve
both and fix bugs
Cheers
Ludwig
On 01/27/2015 05:50 PM, Bjorn Helgaas wrote:
> Hi Ludwig,
>
> Thanks a lot for the pointers to MTCA information. I found
> presentation slides here:
> https://indico.desy.de/getFile.py/access?contribId=33&sessionId=0&resId=1&materialId=slides&confId=10329,
> which I assume is that you're referring to.
>
> On Mon, Jan 26, 2015 at 1:38 AM, Ludwig Petrosyan
> <ludwig.petrosyan@desy.de> wrote:
>> Hello
>>
>> (I have send this email two days ago but got status undeliverable, so try to
>> send it again)
>>
>> We had the same problem on the MTCA system years ago, but now the problem is
>> solved.
>> The MTCA system is a kind of ATCA and I think attention Button problem could
>> be solved in the same way.
>> Ok, now what we have done:
>> First of all the main difference of the ATCA or MTCA PCIe system is what the
>> PCIe Switch which responsible for the HotPlug
>>
>> (I mean Switch which is connected to the crate slots, and hotplug
>> controllers of this are used in hotpluging ) and the Attention Button of the
>>
>> PCIe slot reside on the different boards (usually PCIe Switch is on the
>> Crate Manager board and Attention Button is the AMC module Latch ),
>>
>> So there are no any wired connections between Attention Button and PCIe
>> Switch. Than user pool out the AMC module Latch the PCIe Switch has no idea
>>
>> about that, BUT the AMC module controller (MMC) sends IPMI message to the
>> Crate Management Controller (MCMC)
>> and MCMC starts AMC powering down procedures. The idea was: usually MCMC and
>> PCIe Switch reside on the same board and MCMC getting IPMI message
>>
>> about state change of the AMC Latch (latch polled out or pressed) set
>> appropriate registers of the PCIe Switch or push high appropriate lines of
>> the PCIe Switch
>>
>> and PCIe Switch gets information that Attention Button is pressed and send
>> hotplug interrupt to the hotplug driver.
>> This approach works in our MTCA systems and we have a full working PCIe
>> HotPlug.
> It sounds like you basically have some IPMI glue between the the AMC
> latch and the PCIe Attention Button, and from the point of view of the
> pciehp (PCIe native hotplug) driver, it just sees a normal Attention
> Button. That sounds like a reasonable thing to do.
>
> In Paulo's case, it sounds like there is some sort of switch related
> to the card, but the IPMI or similar glue that could potentially lead
> to the Attention Button line doesn't exist. In that case, pciehp
> doesn't know anything about the switch. If there's some other way,
> e.g., IPMI, to learn about the switch, maybe that could be done via a
> separate driver.
>
>> More detailed information one can get to look documents of the MTCA Workshop
>> (http://mtcaws.desy.de/) in tutorial section was presentation about
>>
>> PCIe Hotplug, or look in PICMIG recommendation (there is new recommendation
>> about PCIe HotPlug for MTC.4)
>>
>> With best regards
>>
>> Ludwig Petrosyan
>>
>>
prev parent reply other threads:[~2015-01-29 1:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 11:42 Hot add a PCIe device driver upon hotplug event Paulo Fortuna Carvalho
2015-01-12 16:58 ` Bjorn Helgaas
2015-01-12 17:26 ` Paulo Fortuna Carvalho
2015-01-12 17:41 ` Bjorn Helgaas
[not found] ` <CAH9N0t-EP9p2V3JMht1F_EyK+bOdiiH1krPLrsTMDQ_961damQ@mail.gmail.com>
2015-01-13 17:29 ` Bjorn Helgaas
[not found] ` <CAH9N0t8s+kcG_Qok0wpoDz9jzwvPk_QmBK_p-qbACZJjrr+iVQ@mail.gmail.com>
2015-01-22 17:41 ` Bjorn Helgaas
[not found] ` <CAH9N0t-+gog9wNFo7hqhzrWuttrRyf5HjjHciFrDGz1rZUiUfw@mail.gmail.com>
2015-01-22 22:20 ` Bjorn Helgaas
2015-01-23 11:35 ` Paulo Fortuna Carvalho
2015-01-23 14:36 ` Bjorn Helgaas
2015-01-27 16:31 ` Paulo Fortuna Carvalho
2015-01-27 16:43 ` Bjorn Helgaas
2015-01-27 16:47 ` Greg Kroah-Hartman
2015-01-27 17:10 ` Paulo Fortuna Carvalho
[not found] ` <CAH9N0t-M2QfW84Jd3fRaLr+NdFvZEkjXzrXsgncoLhtYv-xQ3g@mail.gmail.com>
[not found] ` <CAH9N0t-_JbwtZeU+Kyds8=NX=CBT-+_ecKiUWPKr1zXiLKm0vQ@mail.gmail.com>
2015-01-27 17:11 ` Greg Kroah-Hartman
[not found] ` <54C5EF11.8070604@desy.de>
2015-01-27 16:50 ` Bjorn Helgaas
2015-01-28 7:51 ` Ludwig Petrosyan [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=54C89508.3080001@desy.de \
--to=ludwig.petrosyan@desy.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-pci@vger.kernel.org \
--cc=pricardofc@gmail.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;
as well as URLs for NNTP newsgroup(s).