From: Daniel Vetter <daniel@ffwll.ch>
To: libin.yang@intel.com
Cc: tiwai@suse.de, daniel.vetter@ffwll.ch,
alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 1/4] drm/i915: Add audio sync_audio_rate callback
Date: Wed, 26 Aug 2015 10:17:35 +0200 [thread overview]
Message-ID: <20150826081735.GZ20434@phenom.ffwll.local> (raw)
In-Reply-To: <1439880714-40931-1-git-send-email-libin.yang@intel.com>
On Tue, Aug 18, 2015 at 02:51:51PM +0800, libin.yang@intel.com wrote:
> From: Libin Yang <libin.yang@intel.com>
>
> Add the sync_audio_rate callback.
>
> With the callback, audio driver can trigger
> i915 driver to set the proper N/CTS or N/M
> based on different sample rates.
>
> Signed-off-by: Libin Yang <libin.yang@intel.com>
> ---
> include/drm/i915_component.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/drm/i915_component.h b/include/drm/i915_component.h
> index c9a8b64..aabebcb 100644
> --- a/include/drm/i915_component.h
> +++ b/include/drm/i915_component.h
> @@ -33,6 +33,7 @@ struct i915_audio_component {
> void (*put_power)(struct device *);
> void (*codec_wake_override)(struct device *, bool enable);
> int (*get_cdclk_freq)(struct device *);
> + int (*sync_audio_rate)(struct device *, int port, int rate);
We're missing kerneldoc for this entire struct here, which isn't great.
This needs to be fixed. Please
- pull out the ops structure so it's not inlined (kerneldoc can't handle
nested ops structures).
- please document all the callbacks with kerneldoc. In 4.3 we can have
kerneldoc in-line in structures right above each member like this
/**
* @put_power:
*
* Longer text explaining this hook.
*/
void (*put_power)(struct device *);
For each hook please explain at least who calls it (gfx or audio) and
where exactly it's called in the overall flow.
- Extended the overview doc section with references to the component/ops
structure would be needed too.
And please make sure it all looks pretty with make htmldocs.
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
next prev parent reply other threads:[~2015-08-26 8:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 6:51 [PATCH v5 1/4] drm/i915: Add audio sync_audio_rate callback libin.yang
2015-08-18 6:51 ` [PATCH v5 2/4] drm/i915: implement " libin.yang
2015-08-21 15:14 ` Ville Syrjälä
2015-08-24 2:38 ` Yang, Libin
2015-08-24 12:53 ` Ville Syrjälä
2015-08-24 12:58 ` Takashi Iwai
2015-08-24 15:35 ` Yang, Libin
2015-08-24 16:27 ` Ville Syrjälä
2015-08-25 1:48 ` Yang, Libin
2015-08-26 12:27 ` Ville Syrjälä
2015-08-27 2:06 ` Yang, Libin
2015-08-18 6:51 ` [PATCH v5 3/4] ALSA: hda - display audio call " libin.yang
2015-08-18 6:51 ` [PATCH v5 4/4] drm/i915: set proper N/CTS in modeset libin.yang
2015-08-21 15:26 ` Ville Syrjälä
2015-08-24 1:53 ` Yang, Libin
2015-08-26 8:17 ` Daniel Vetter [this message]
2015-08-26 8:29 ` [PATCH v5 1/4] drm/i915: Add audio sync_audio_rate callback Yang, Libin
2015-08-26 9:08 ` Daniel Vetter
2015-08-26 11:08 ` Yang, Libin
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=20150826081735.GZ20434@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=libin.yang@intel.com \
--cc=tiwai@suse.de \
/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