All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Tejun Heo <tj@kernel.org>, Herbert Poetzl <herbert@13thfloor.at>,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: PMP and SEMB messages to SEP
Date: Mon, 17 Jan 2011 13:55:15 -0500	[thread overview]
Message-ID: <4D349093.6070902@garzik.org> (raw)
In-Reply-To: <1295281131.3015.44.camel@mulgrave.site>

On 01/17/2011 11:18 AM, James Bottomley wrote:
> On Mon, 2011-01-17 at 16:40 +0100, Tejun Heo wrote:
>>> - the SiI3726 supports GPIO pins, which can be reached via
>>>    the General Status and Control Register [130] and accoring
>>>    to the docu, the Read/Write Port Multiplier command can
>>>    be used to read/write that register.
>>>
>>>    + how would I go about issuing such a command and where
>>>      should it be done? i.e. what about interference with
>>>      other commands? what about retrieving return values?
>>
>> The problem is that the PMP device itself is currently not allocated a
>> userland visible device, so it doesn't have any /dev/* node.  Hmmm...
>
> So perhaps it should be.  If you look at the equivalent topology on SAS,
> our expanders have a bsg device node precisely so that we can do this.
>
> That said, SAS expanders have a defined protocol (SAS Management
> Protocol) to talk to the outside world, so they are real visible objects
> always in our topology ... I'm not sure PMP has this ... it seems that
> all PMP visibility is an extension to the standard?

Yes, we do need a way to address these devices.

	Jeff




      parent reply	other threads:[~2011-01-17 18:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 19:25 PMP and SEMB messages to SEP Herbert Poetzl
2011-01-14 14:20 ` Tejun Heo
2011-01-14 16:59   ` Herbert Poetzl
2011-01-14 17:04     ` Tejun Heo
2011-01-14 17:37       ` Herbert Poetzl
2011-01-17 15:40         ` Tejun Heo
2011-01-17 16:18           ` James Bottomley
2011-01-17 17:13             ` Herbert Poetzl
2011-01-17 17:20               ` Tejun Heo
2011-01-17 17:34                 ` Herbert Poetzl
2011-01-17 17:39                   ` Tejun Heo
2011-01-17 17:48                     ` Herbert Poetzl
2011-01-17 18:05                       ` James Bottomley
2011-01-17 18:21                         ` Herbert Poetzl
2011-01-17 18:27                           ` Herbert Poetzl
2011-01-17 17:18             ` Tejun Heo
2011-01-17 17:21               ` James Bottomley
2011-01-17 17:24                 ` Tejun Heo
2011-01-25  3:07                   ` Herbert Poetzl
2011-01-25 14:14                     ` James Bottomley
2011-04-03 17:39                       ` Herbert Poetzl
2011-04-03 18:38                         ` James Bottomley
2011-01-17 18:55             ` Jeff Garzik [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=4D349093.6070902@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@suse.de \
    --cc=herbert@13thfloor.at \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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.