From: sdharia@codeaurora.org (Sagar Dharia)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] slimbus message encoding/decoding
Date: Fri, 09 Mar 2012 12:50:24 -0700 [thread overview]
Message-ID: <4F5A5F00.70508@codeaurora.org> (raw)
In-Reply-To: <20120309002106.GA605@plastictigers.com>
On 03/08/2012 05:21 PM, Marc Butler wrote:
> All,
>
> This patch provides generic functions for encoding/decoding SLIMbus
> messages (Section 8 of the specification).
Thanks for providing this patch. My understanding is that this patch
provides helper functions for h/w controllers which rely on s/w to
provide the exact message to be sent out on the bus.
> No CRC generator is included for the PI and MI fields. The OMAP4430
> chip this is being tested on generates and populates these fields in
> h/w. However, I have include a general (and untested) callback
> mechanism.
Just like CRC, some other fields may be populated by HW. e.g. Qualcomm
chip also populates Arbitration priority, Arbitration Extension fields.
So it expects SW to only program a few fields, a.k.a logical/elemental
address, MT,MC, DT etc.(that too, SW programs this based on software
interface manual). The hardware will convert this information to actual
slimbus-compliant message and send it on the bus.
Being said that, I am not aware of how majority of h/w controllers work
and will be open to have this patch if other hardwares rely on s/w to
provide the exact message as well.
-Sagar
> -m
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-03-09 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 0:21 [RFC PATCH] slimbus message encoding/decoding Marc Butler
2012-03-09 19:50 ` Sagar Dharia [this message]
2012-03-09 22:39 ` 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=4F5A5F00.70508@codeaurora.org \
--to=sdharia@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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