linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sagar Dharia" <sdharia@codeaurora.org>
To: "Rob Landley" <rob@landley.net>
Cc: "Sagar Dharia" <sdharia@codeaurora.org>,
	davidb@codeaurora.org, bryanh@codeaurora.org,
	kheitke@codeaurora.org, marc@plastictigers.com,
	gclemson@audience.com, broonie@opensource.wolfsonmicro.com,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, grant.likely@secretlab.ca,
	rob.herring@calxeda.com, ohad@wizery.com,
	gregkh@linuxfoundation.org, linus.walleij@linaro.org,
	rusty@rustcorp.com.au, joerg.roedel@amd.com, trenn@suse.de,
	ak@linux.intel.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] slimbus: Linux driver framework for SLIMbus.
Date: Mon, 4 Jun 2012 02:51:49 -0700 (PDT)	[thread overview]
Message-ID: <53f16b8f6198e1adb9cc54bb8b9d80cb.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <4FCC280C.6030103@landley.net>

>
> Slim?
>
SLIMbus is MIPI alliance specification. Since word "bus" is part of the
specification, I thought it will be good to keep it that way.

The specification is available to all MIPI members.
Some more info here:
http://mipi.org/specifications/serial-low-power-inter-chip-media-bus-slimbussm-specification

>> +and the messages can be of unicast and broadcast type. E.g.
>> reading/writing
>> +device specific values is typically a unicast message. A data channel
>> +reconfiguration sequence is announced to all devices using a broadcast
>> message.
>
> Unicast messages are seen by all devices?
>
I was trying to give example of each type of both message. I will reword
it to be more clear.

>> +Slimbus specification has different types of device classifications
>> based on
>> +their capabilities.
>
> I'm trying to figure out if that sentence conveys any information at all.
>
I will reword this to say: "has following type of device classifications
based on capabilities:".

> So each slimbus has 1 manager device that enumerates configures, and
> allocates channels for the other devices on the bus. The rest are
> "framer" devices that transmit data packets?
>
Typically there is 1 framer per bus, but if there are multiple framers
then manager is responsible for doing handoff between framers.
>
> However, I expect some example code would be far more useful than this
> document...
>
Please refer to slimbus.c for slimbus framework.

Thank you for your comments. I will address all the comments in the next
patch.

Regards
Sagar

Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.


  parent reply	other threads:[~2012-06-04  9:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  1:11 [PATCH] slimbus: Linux driver framework for SLIMbus Sagar Dharia
2012-05-30 18:13 ` Mark Brown
2012-06-04  9:54   ` Sagar Dharia
2012-06-01  0:16 ` Marc Butler
2012-06-04 10:21   ` Sagar Dharia
2012-06-04 10:27     ` Mark Brown
2012-06-04 10:36       ` Sagar Dharia
2012-06-04 10:42         ` Mark Brown
2012-06-04 17:13     ` Marc Butler
2012-06-06  8:13       ` Sagar Dharia
2012-06-03 16:34 ` Joe Perches
2012-06-04 10:25   ` Sagar Dharia
2012-06-04  3:14 ` Rob Landley
2012-06-04  7:29   ` Mark Brown
2012-06-04  9:51   ` Sagar Dharia [this message]
2012-06-04 23:41 ` Ryan Mallon
2012-06-06  8:19   ` Sagar Dharia
2012-06-05 20:57 ` Marc Butler

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=53f16b8f6198e1adb9cc54bb8b9d80cb.squirrel@www.codeaurora.org \
    --to=sdharia@codeaurora.org \
    --cc=ak@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gclemson@audience.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=kheitke@codeaurora.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@plastictigers.com \
    --cc=ohad@wizery.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    --cc=trenn@suse.de \
    /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).