From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/dp: Print the number of bytes processed for aux nacks
Date: Thu, 19 Mar 2015 15:51:54 +0100 [thread overview]
Message-ID: <20150319145154.GS31422@phenom.ffwll.local> (raw)
In-Reply-To: <87wq2dus27.fsf@intel.com>
On Thu, Mar 19, 2015 at 01:48:00PM +0200, Jani Nikula wrote:
> On Thu, 19 Mar 2015, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > When doing a native or i2c aux write the sink will indicate the number
> > of bytes written even if it the nacks the transfer. When we receive a
> > nack we just return an error upwards, but it might still be interesting
> > to see how many bytes made it before the nack. So include that information
> > in the debug messages.
> >
> > v2: Also print the message size (Jani)
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Merged to drm-misc, thanks.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-03-19 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 9:44 [PATCH 1/3] drm/dp: Print the number of bytes processed for aux nacks ville.syrjala
2015-03-19 9:44 ` [PATCH 2/3] drm/i915: Send out the full AUX address ville.syrjala
2015-03-19 10:20 ` Jani Nikula
2015-03-19 14:52 ` [Intel-gfx] " Daniel Vetter
2015-03-19 9:44 ` [PATCH 3/3] drm/radeon: " ville.syrjala
2015-03-19 17:42 ` shuang.he
2015-03-19 10:21 ` [PATCH 1/3] drm/dp: Print the number of bytes processed for aux nacks Jani Nikula
2015-03-19 11:38 ` [PATCH v2 " ville.syrjala
2015-03-19 11:48 ` Jani Nikula
2015-03-19 14:51 ` Daniel Vetter [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=20150319145154.GS31422@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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