From: Jani Nikula <jani.nikula@linux.intel.com>
To: Alex Deucher <alexdeucher@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH 1/4] drm/dp: add flags field to drm_dp_aux_msg struct
Date: Fri, 04 Apr 2014 09:09:31 +0300 [thread overview]
Message-ID: <87bnwhbp7o.fsf@intel.com> (raw)
In-Reply-To: <1395447217-1926-1-git-send-email-alexander.deucher@amd.com>
On Sat, 22 Mar 2014, Alex Deucher <alexdeucher@gmail.com> wrote:
> This adds a flags field and a new flag, BARE_ADDRESS,
> which drivers can use for special handling when they
> want to set just the aux address. This is needed
> to properly reset the connection between i2c transactions.
Sorry it took me so long to get to this.
The changes in patches 1-3 look sensible in general, but I think I'd
prefer you dropped the flags field and used size == 0 to mean bare
address. It feels silly to have to set size = 1 and have a dummy one
byte buffer that doesn't get transfered. Without the payload I think it
feels natural only the address is transfered.
BR,
Jani.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> include/drm/drm_dp_helper.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index b7488c9..a006e96 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -403,6 +403,8 @@ drm_dp_enhanced_frame_cap(const u8 dpcd[DP_RECEIVER_CAP_SIZE])
> * DisplayPort AUX channel
> */
>
> +#define DRM_DP_AUX_MSG_FLAGS_BARE_ADDRESS (1 << 0)
> +
> /**
> * struct drm_dp_aux_msg - DisplayPort AUX channel transaction
> * @address: address of the (first) register to access
> @@ -417,6 +419,7 @@ struct drm_dp_aux_msg {
> u8 reply;
> void *buffer;
> size_t size;
> + u32 flags;
> };
>
> /**
> --
> 1.8.3.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-04 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 0:13 [PATCH 1/4] drm/dp: add flags field to drm_dp_aux_msg struct Alex Deucher
2014-03-22 0:13 ` [PATCH 2/4] drm/radeon/dp: handle the new BARE_ADDRESS aux flag Alex Deucher
2014-03-22 0:13 ` [PATCH 3/4] drm/dp/i2c: use new BARE_ADDRESS flags in i2c over aux Alex Deucher
2014-03-22 0:13 ` [PATCH 4/4] drm/radeon/dp: switch to the common i2c over aux code Alex Deucher
2014-04-04 6:09 ` Jani Nikula [this message]
2014-04-04 14:35 ` [PATCH 1/4] drm/dp: add flags field to drm_dp_aux_msg struct Alex Deucher
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=87bnwhbp7o.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.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