From: "Sagar Dharia" <sdharia@codeaurora.org>
To: Marc Butler <marc@plastictigers.com>
Cc: Sagar Dharia <sdharia@codeaurora.org>,
davidb@codeaurora.org, bryanh@codeaurora.org,
kheitke@codeaurora.org, gclemson@audience.com,
broonie@opensource.wolfsonmicro.com,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rob@landley.net,
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: Wed, 6 Jun 2012 01:13:30 -0700 (PDT) [thread overview]
Message-ID: <dd131f3f86e367a47b3528015cde9dd9.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20120604171344.GA15837@plastictigers.com>
> I understand it is not a 1-to-1 mapping. However it *is* used as such:
>
> wbuf[2] = (u8)((segdist & 0xF00) >> 8) | (slc->prop.prot << 4);
>
> which results in NEXT_DEFINE_CHANNEL messages with an invalid TP
> field.
Yes, thanks for catching this. I will make changes to rectify this.
>
> Yes, my mistake. The driver wouldn't have to poll if there was another
> callback. So I don't see how the completion mechanism is superior: it
> forces a synchronous interface to asynchronous events, or the driver
> developer has to work around it.
The get_logical_address API itself doesn't take completion. Completion is
part of slim_device structure so that the slim_device's driver can wait on
it whenever it needs LA for the first time. (Framework signals completion
on a slim_device when it gets enumerated)
If callback is preferred, I will change it to callback.
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.
WARNING: multiple messages have this Message-ID (diff)
From: sdharia@codeaurora.org (Sagar Dharia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] slimbus: Linux driver framework for SLIMbus.
Date: Wed, 6 Jun 2012 01:13:30 -0700 (PDT) [thread overview]
Message-ID: <dd131f3f86e367a47b3528015cde9dd9.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20120604171344.GA15837@plastictigers.com>
> I understand it is not a 1-to-1 mapping. However it *is* used as such:
>
> wbuf[2] = (u8)((segdist & 0xF00) >> 8) | (slc->prop.prot << 4);
>
> which results in NEXT_DEFINE_CHANNEL messages with an invalid TP
> field.
Yes, thanks for catching this. I will make changes to rectify this.
>
> Yes, my mistake. The driver wouldn't have to poll if there was another
> callback. So I don't see how the completion mechanism is superior: it
> forces a synchronous interface to asynchronous events, or the driver
> developer has to work around it.
The get_logical_address API itself doesn't take completion. Completion is
part of slim_device structure so that the slim_device's driver can wait on
it whenever it needs LA for the first time. (Framework signals completion
on a slim_device when it gets enumerated)
If callback is preferred, I will change it to callback.
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.
next prev parent reply other threads:[~2012-06-06 8:13 UTC|newest]
Thread overview: 38+ 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 1:11 ` Sagar Dharia
2012-05-30 18:13 ` Mark Brown
2012-05-30 18:13 ` Mark Brown
2012-06-04 9:54 ` Sagar Dharia
2012-06-04 9:54 ` Sagar Dharia
2012-06-01 0:16 ` Marc Butler
2012-06-01 0:16 ` Marc Butler
2012-06-01 0:16 ` Marc Butler
2012-06-04 10:21 ` Sagar Dharia
2012-06-04 10:21 ` Sagar Dharia
2012-06-04 10:27 ` Mark Brown
2012-06-04 10:27 ` Mark Brown
2012-06-04 10:36 ` Sagar Dharia
2012-06-04 10:36 ` Sagar Dharia
2012-06-04 10:42 ` Mark Brown
2012-06-04 10:42 ` Mark Brown
2012-06-04 17:13 ` Marc Butler
2012-06-04 17:13 ` Marc Butler
2012-06-06 8:13 ` Sagar Dharia [this message]
2012-06-06 8:13 ` Sagar Dharia
[not found] ` <1338340310-4473-1-git-send-email-sdharia-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2012-06-03 16:34 ` Joe Perches
2012-06-03 16:34 ` Joe Perches
2012-06-03 16:34 ` Joe Perches
2012-06-04 10:25 ` Sagar Dharia
2012-06-04 10:25 ` Sagar Dharia
2012-06-04 3:14 ` Rob Landley
2012-06-04 3:14 ` Rob Landley
2012-06-04 7:29 ` Mark Brown
2012-06-04 7:29 ` Mark Brown
2012-06-04 9:51 ` Sagar Dharia
2012-06-04 9:51 ` Sagar Dharia
2012-06-04 23:41 ` Ryan Mallon
2012-06-04 23:41 ` Ryan Mallon
2012-06-06 8:19 ` Sagar Dharia
2012-06-06 8:19 ` Sagar Dharia
2012-06-05 20:57 ` Marc Butler
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=dd131f3f86e367a47b3528015cde9dd9.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 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.