linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vikash Garodia <vgarodia@codeaurora.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: hverkuil@xs4all.nl, mchehab@kernel.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, acourbot@chromium.org,
	linux-media-owner@vger.kernel.org
Subject: Re: [PATCH v11 0/5] Venus updates - PIL
Date: Wed, 17 Oct 2018 18:51:42 +0530	[thread overview]
Message-ID: <5c098025f136c25f5b0bb14d79866cf8@codeaurora.org> (raw)
In-Reply-To: <a31e499a-fa88-67b8-1853-8ea0d9297aa9@linaro.org>

Hi Stanimir,

Thanks for the review and approvals.
I have just posted v12 with the below comments addressed.

Please check and provide your blessings :)

On 2018-10-17 14:40, Stanimir Varbanov wrote:
> Hi Vikash,
> 
> Thanks for the patches and patience!
> 
> On 10/08/2018 04:32 PM, Vikash Garodia wrote:
>> This version of the series
>> * extends the description of firmware subnode in documentation.
>> * renames the flag suggesting the presence of tz and update code
>>   accordingly.
>> 
>> Stanimir Varbanov (1):
>>   venus: firmware: register separate platform_device for firmware 
>> loader
>> 
>> Vikash Garodia (4):
>>   venus: firmware: add routine to reset ARM9
>>   venus: firmware: move load firmware in a separate function
>>   venus: firmware: add no TZ boot and shutdown routine
>>   dt-bindings: media: Document bindings for venus firmware device
>> 
>>  .../devicetree/bindings/media/qcom,venus.txt       |  14 +-
>>  drivers/media/platform/qcom/venus/core.c           |  24 ++-
>>  drivers/media/platform/qcom/venus/core.h           |   6 +
>>  drivers/media/platform/qcom/venus/firmware.c       | 235 
>> +++++++++++++++++++--
>>  drivers/media/platform/qcom/venus/firmware.h       |  17 +-
>>  drivers/media/platform/qcom/venus/hfi_venus.c      |  13 +-
>>  drivers/media/platform/qcom/venus/hfi_venus_io.h   |   8 +
>>  7 files changed, 274 insertions(+), 43 deletions(-)
>> 
> 
> Tested-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>
> 
> With the comment addressed in 1/5:
> 
> Acked-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>

      reply	other threads:[~2018-10-17 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 13:32 [PATCH v11 0/5] Venus updates - PIL Vikash Garodia
2018-10-08 13:32 ` [PATCH v11 1/5] venus: firmware: add routine to reset ARM9 Vikash Garodia
2018-10-17  8:49   ` Stanimir Varbanov
2018-10-18  1:42     ` Joe Perches
2018-10-18  8:41       ` Stanimir Varbanov
2018-10-08 13:32 ` [PATCH v11 2/5] venus: firmware: move load firmware in a separate function Vikash Garodia
2018-10-08 13:32 ` [PATCH v11 3/5] venus: firmware: register separate platform_device for firmware loader Vikash Garodia
2018-10-08 13:32 ` [PATCH v11 4/5] venus: firmware: add no TZ boot and shutdown routine Vikash Garodia
2018-10-08 13:32 ` [PATCH v11 5/5] dt-bindings: media: Document bindings for venus firmware device Vikash Garodia
2018-10-16 15:55 ` [PATCH v11 0/5] Venus updates - PIL Vikash Garodia
2018-10-17  7:07   ` Stanimir Varbanov
2018-10-17  9:10 ` Stanimir Varbanov
2018-10-17 13:21   ` Vikash Garodia [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=5c098025f136c25f5b0bb14d79866cf8@codeaurora.org \
    --to=vgarodia@codeaurora.org \
    --cc=acourbot@chromium.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media-owner@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stanimir.varbanov@linaro.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;
as well as URLs for NNTP newsgroup(s).