dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <a.hajda@samsung.com>
To: YoungJun Cho <yj44.cho@samsung.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/dsi: Make mipi_dsi_dcs_write() return ssize_t
Date: Tue, 22 Jul 2014 12:05:57 +0200	[thread overview]
Message-ID: <53CE3785.5080407@samsung.com> (raw)
In-Reply-To: <53CE33F7.6020204@samsung.com>

On 07/22/2014 11:50 AM, YoungJun Cho wrote:
> Hi,
>
> On 07/22/2014 04:28 PM, Andrzej Hajda wrote:
>> Hi Thierry,
>>
>> Thanks for the patch.
>>
>> On 07/22/2014 09:12 AM, Thierry Reding wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> This function returns the value of the struct mipi_dsi_host_ops'
>>> .transfer() so make sure the return types are consistent.
>>>
>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>> Acked-by: Andrzej Hajda <a.hajda@samsung.com>
>> --
>> Regards
>> Andrzej
>>> ---
>>>   drivers/gpu/drm/drm_mipi_dsi.c        | 4 ++--
>>>   drivers/gpu/drm/panel/panel-s6e8aa0.c | 4 ++--
>>>   include/drm/drm_mipi_dsi.h            | 4 ++--
>>>   3 files changed, 6 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_dsi.c
>>> index e633df2f68d8..6d2fd2077dae 100644
>>> --- a/drivers/gpu/drm/drm_mipi_dsi.c
>>> +++ b/drivers/gpu/drm/drm_mipi_dsi.c
>>> @@ -205,8 +205,8 @@ EXPORT_SYMBOL(mipi_dsi_detach);
>>>    * @data: pointer to the command followed by parameters
>>>    * @len: length of @data
>>>    */
>>> -int mipi_dsi_dcs_write(struct mipi_dsi_device *dsi, unsigned int channel,
>>> -		       const void *data, size_t len)
>>> +ssize_t mipi_dsi_dcs_write(struct mipi_dsi_device *dsi, unsigned int channel,
>>> +			   const void *data, size_t len)
>>>   {
>>>   	const struct mipi_dsi_host_ops *ops = dsi->host->ops;
>>>   	struct mipi_dsi_msg msg = {
>>> diff --git a/drivers/gpu/drm/panel/panel-s6e8aa0.c b/drivers/gpu/drm/panel/panel-s6e8aa0.c
>>> index 06e57a26db7a..beb43492b649 100644
>>> --- a/drivers/gpu/drm/panel/panel-s6e8aa0.c
>>> +++ b/drivers/gpu/drm/panel/panel-s6e8aa0.c
>>> @@ -133,14 +133,14 @@ static int s6e8aa0_clear_error(struct s6e8aa0 *ctx)
>>>   static void s6e8aa0_dcs_write(struct s6e8aa0 *ctx, const void *data, size_t len)
>>>   {
>>>   	struct mipi_dsi_device *dsi = to_mipi_dsi_device(ctx->dev);
>>> -	int ret;
>>> +	ssize_t ret;
>>>
>>>   	if (ctx->error < 0)
>>>   		return;
>>>
>>>   	ret = mipi_dsi_dcs_write(dsi, dsi->channel, data, len);
>>>   	if (ret < 0) {
>>> -		dev_err(ctx->dev, "error %d writing dcs seq: %*ph\n", ret, len,
>>> +		dev_err(ctx->dev, "error %zd writing dcs seq: %*ph\n", ret, len,
>>>   			data);
>>>   		ctx->error = ret;
> One more thing!
> This 'ctx->error' type is 'int'. So it should be changed from int to 
> ssize_t in struct s6e8aa0.
I do not think so. ctx->error contains always error code, and this is
guarded here
by 'if (ret < 0)'  clause.

Regards
Andrzej
>
> Thank you.
> Best regards YJ
>
>>>   	}
>>> diff --git a/include/drm/drm_mipi_dsi.h b/include/drm/drm_mipi_dsi.h
>>> index efa1b552adc5..4b0112781910 100644
>>> --- a/include/drm/drm_mipi_dsi.h
>>> +++ b/include/drm/drm_mipi_dsi.h
>>> @@ -127,8 +127,8 @@ struct mipi_dsi_device {
>>>
>>>   int mipi_dsi_attach(struct mipi_dsi_device *dsi);
>>>   int mipi_dsi_detach(struct mipi_dsi_device *dsi);
>>> -int mipi_dsi_dcs_write(struct mipi_dsi_device *dsi, unsigned int channel,
>>> -		       const void *data, size_t len);
>>> +ssize_t mipi_dsi_dcs_write(struct mipi_dsi_device *dsi, unsigned int channel,
>>> +			   const void *data, size_t len);
>>>   ssize_t mipi_dsi_dcs_read(struct mipi_dsi_device *dsi, unsigned int channel,
>>>   			  u8 cmd, void *data, size_t len);
>>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>

  reply	other threads:[~2014-07-22 10:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  7:12 [PATCH 1/4] drm/dsi: Make mipi_dsi_dcs_write() return ssize_t Thierry Reding
2014-07-22  7:12 ` [PATCH 2/4] drm/dsi: Use peripheral's channel for DCS commands Thierry Reding
2014-07-22  7:30   ` Andrzej Hajda
2014-07-22  7:12 ` [PATCH 3/4] drm/dsi: Make mipi_dsi_dcs_{read,write}() symmetrical Thierry Reding
2014-07-22  7:32   ` [PATCH 3/4] drm/dsi: Make mipi_dsi_dcs_{read, write}() symmetrical Andrzej Hajda
2014-07-22  8:12     ` Thierry Reding
2014-07-22  9:33       ` Andrzej Hajda
2014-07-23  7:51         ` Thierry Reding
2014-07-23 10:59           ` Andrzej Hajda
2014-07-23 13:37             ` Thierry Reding
2014-07-24  7:57               ` Andrzej Hajda
2014-07-24  9:31                 ` Thierry Reding
2014-07-22 11:20   ` Daniel Vetter
2014-07-23  6:32     ` Andrzej Hajda
2014-07-22  7:12 ` [PATCH 4/4] drm/panel: s6e8aa0: Use static inline for upcasting Thierry Reding
2014-07-22  7:33   ` Andrzej Hajda
2014-07-22  7:28 ` [PATCH 1/4] drm/dsi: Make mipi_dsi_dcs_write() return ssize_t Andrzej Hajda
2014-07-22  9:50   ` YoungJun Cho
2014-07-22 10:05     ` Andrzej Hajda [this message]
2014-07-22 10:23       ` Andrzej Hajda
2014-07-23  7:27         ` Thierry Reding
2014-07-23  8:18           ` Andrzej Hajda

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=53CE3785.5080407@samsung.com \
    --to=a.hajda@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thierry.reding@gmail.com \
    --cc=yj44.cho@samsung.com \
    /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