From: "Kay Sievers" <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: sending uevent form SATA promise driver.
Date: Mon, 27 Oct 2008 22:33:23 +0000 [thread overview]
Message-ID: <ac3eb2510810271533x75475caev1b93d0dc968071e4@mail.gmail.com> (raw)
In-Reply-To: <889538.92627.qm@web33104.mail.mud.yahoo.com>
On Mon, Oct 27, 2008 at 18:35, Padmini Krishnamurthy <krishpm@yahoo.com> wrote:
> Our test device is connected to the promise card which sits on a PCI slot on the PC. Our test SATA driver drives this device. The driver is loaded during bootup. I am seeing output of both udevadm and /var/log/messages when I turn on the device. I see the interrupt handling messages on /var/log/messages but udevadm does not report any event recived.
> So, I ported some of the hotplug support from libata. But there I see that the hotplug event notification is handled in acpi. So, I am not sure, if I have to add this in our driver at the device attach routine?
> How would the uevent be sent to udev when the device is attached?
What kind of devices does this driver create in the kernel? What are
the parent devices of the block devices it offers? SCSI, libata,
whatever?
Your driver should just create devices representing the stuff that is
connected to the controller, the creation of these devices will do the
uevent, you do not create custom events on your own in any usual
driver code.
Kay
prev parent reply other threads:[~2008-10-27 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:42 sending uevent form SATA promise driver Padmini Krishnamurthy
2008-10-27 16:50 ` Kay Sievers
2008-10-27 17:35 ` Padmini Krishnamurthy
2008-10-27 22:33 ` Kay Sievers [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=ac3eb2510810271533x75475caev1b93d0dc968071e4@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).