From: Hannes Reinecke <hare@suse.de>
To: Kristen Carlson Accardi <kristen@linux.intel.com>
Cc: Tejun Heo <tj@kernel.org>, jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ahci: EM supported message type sysfs attribute
Date: Mon, 07 Mar 2011 16:49:38 +0100 [thread overview]
Message-ID: <4D74FE92.3040201@suse.de> (raw)
In-Reply-To: <20110304103956.7360a840@kcaccard-MOBL3>
On 03/04/2011 07:39 PM, Kristen Carlson Accardi wrote:
> On Fri, 04 Mar 2011 09:54:52 +0100
> hare@suse.de (Hannes Reinecke) wrote:
>
>>
>> This patch adds an sysfs attribute 'em_message_supported' to the
>> ahci host device which prints out the supported enclosure management
>> message types.
>
> Is it useful to display the host controllers supported em
> message types when libata only can support LED type?
Yes. libata might only support LED types currently.
However, as other types are defined as per spec
we'll be coming across those types eventually.
But with the current code we don't have any means of detecting them.
libata just prints out 'ems' at module load time, without any hint
which message type is actually supported.
With this patch we can now signal the presence of additional message
types to the user, allowing him to start hacking :-)
Incidentally, if you know of a chipset/board already supporting
different message types I'm all ears :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2011-03-07 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 8:54 [PATCH] ahci: EM supported message type sysfs attribute Hannes Reinecke
2011-03-04 18:39 ` Kristen Carlson Accardi
2011-03-07 15:49 ` Hannes Reinecke [this message]
2011-03-07 17:32 ` Kristen Carlson Accardi
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=4D74FE92.3040201@suse.de \
--to=hare@suse.de \
--cc=jgarzik@pobox.com \
--cc=kristen@linux.intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.