On Tue, Dec 23, 2014 at 03:49:17PM +0200, Mika Westerberg wrote:
> Mark, any comments on this?
Please don't send contentless pings, they just add more e-mail. Resend
if you think something has been lost.
signature.asc
Description: Digital signature
On Mon, Dec 01, 2014 at 11:12:46AM +0200, Mika Westerberg wrote:
> Once the current message is finished, the driver notifies SPI core about
> this by calling spi_finalize_current_message(). This function queues next
> message to be transferred. If there are more messages in the queue, it is
>
On Mon, Dec 01, 2014 at 11:12:46AM +0200, Mika Westerberg wrote:
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be transferred. If there are more messages in the queue, it is
possible
On Tue, Dec 23, 2014 at 03:49:17PM +0200, Mika Westerberg wrote:
Mark, any comments on this?
Please don't send contentless pings, they just add more e-mail. Resend
if you think something has been lost.
signature.asc
Description: Digital signature
Mika Westerberg writes:
> On Thu, Dec 04, 2014 at 10:01:06PM +0100, Robert Jarzmik wrote:
>> So with your change, we have :
>> drv_data->cur_chip = NULL;
>> spi_finalize_current_message(drv_data->master);
>>
>> In that case, if spi_finalize_current_message() queues another message,
On Thu, Dec 04, 2014 at 10:01:06PM +0100, Robert Jarzmik wrote:
> Mika Westerberg writes:
>
> > Once the current message is finished, the driver notifies SPI core about
> > this by calling spi_finalize_current_message(). This function queues next
> > message to be transferred. If there are more
On Thu, Dec 04, 2014 at 10:01:06PM +0100, Robert Jarzmik wrote:
Mika Westerberg mika.westerb...@linux.intel.com writes:
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be
Mika Westerberg mika.westerb...@linux.intel.com writes:
On Thu, Dec 04, 2014 at 10:01:06PM +0100, Robert Jarzmik wrote:
So with your change, we have :
drv_data-cur_chip = NULL;
spi_finalize_current_message(drv_data-master);
In that case, if spi_finalize_current_message() queues
Mika Westerberg writes:
> Once the current message is finished, the driver notifies SPI core about
> this by calling spi_finalize_current_message(). This function queues next
> message to be transferred. If there are more messages in the queue, it is
> possible that the driver is asked to
Mika Westerberg mika.westerb...@linux.intel.com writes:
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be transferred. If there are more messages in the queue, it is
possible that
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be transferred. If there are more messages in the queue, it is
possible that the driver is asked to transfer the next message at this
point.
Once the current message is finished, the driver notifies SPI core about
this by calling spi_finalize_current_message(). This function queues next
message to be transferred. If there are more messages in the queue, it is
possible that the driver is asked to transfer the next message at this
point.
12 matches
Mail list logo
