From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: add kerneldoc for i915_audio_component
Date: Fri, 4 Sep 2015 09:54:53 +0200 [thread overview]
Message-ID: <20150904075453.GH22430@phenom.ffwll.local> (raw)
In-Reply-To: <871tee1ycu.fsf@intel.com>
On Fri, Sep 04, 2015 at 09:40:17AM +0300, Jani Nikula wrote:
> On Fri, 04 Sep 2015, "Yang, Libin" <libin.yang@intel.com> wrote:
> >> -----Original Message-----
> >> From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of
> >> Daniel Vetter
> >> Sent: Wednesday, September 02, 2015 8:18 PM
> >> To: Yang, Libin
> >> Cc: intel-gfx@lists.freedesktop.org; daniel.vetter@ffwll.ch;
> >> jani.nikula@linux.intel.com; ville.syrjala@linux.intel.com
> >> Subject: Re: [PATCH] drm/i915: add kerneldoc for
> >> i915_audio_component
> >>
> >> On Wed, Sep 02, 2015 at 02:12:24PM +0800, libin.yang@intel.com
> >> wrote:
> >> > From: Libin Yang <libin.yang@intel.com>
> >> >
> >> > Add the kerneldoc for i915_audio_component in i915_component.h
> >> >
> >> > Signed-off-by: Libin Yang <libin.yang@intel.com>
> >> > ---
> >> > include/drm/i915_component.h | 39 ++++++++++++++++++++++++--
> >> -------------
> >> > 1 file changed, 24 insertions(+), 15 deletions(-)
> >> >
> >> > diff --git a/include/drm/i915_component.h
> >> b/include/drm/i915_component.h
> >> > index 8ad6f1b..187acc8 100644
> >> > --- a/include/drm/i915_component.h
> >> > +++ b/include/drm/i915_component.h
> >> > @@ -24,23 +24,32 @@
> >> > #ifndef _I915_COMPONENT_H_
> >> > #define _I915_COMPONENT_H_
> >> >
> >> > +/**
> >> > + * struct i915_audio_component_ops - callbacks defined in gfx
> >> driver
> >> > + * @owner: the module owner
> >> > + * @get_power: get the POWER_DOMAIN_AUDIO power well
> >> > + * @put_power: put the POWER_DOMAIN_AUDIO power well
> >> > + * @codec_wake_override: Enable/Disable generating the codec
> >> wake signal
> >> > + * @get_cdclk_freq: get the Core Display Clock in KHz
> >> > + * @sync_audio_rate: set n/cts based on the sample rate
> >> > + */
> >> > +struct i915_audio_component_ops {
> >> > + struct module *owner;
> >>
> >> New kerneldoc in 4.3 allows you to split structure documentation up
> >> into
> >> per-member comments. Especially with vtables I think this makes a lot
> >> of
> >> sense, since then you have enough space to document where and how
> >> exactly
> >> a given hook is called (looks, place in the overall sequence).
> >>
> >> Also please include your stancas in the drm.tmpl docbook template,
> >> otherwise it won't be included in the html docs. And finally please add
> >
> > OK, I will add it in drm.tmpl.
> >
> >> a
> >> DOC: overview section which explains at a high level how i915 and
> >> hda-intel corporate for hdmi/dp audio.
> >
> > Where the DOC should be located in?
>
> i915/intel_audio.c already has a "DOC: High Definition Audio over HDMI
> and Display Port" comment. IMO you could just amend that, as there's
> already some references to the audio driver.
Yeah I think that would be a perfect place.
-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-09-04 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 6:12 [PATCH] drm/i915: add kerneldoc for i915_audio_component libin.yang
2015-09-02 12:18 ` Daniel Vetter
2015-09-04 1:52 ` Yang, Libin
2015-09-04 6:40 ` Jani Nikula
2015-09-04 7:54 ` Daniel Vetter [this message]
2015-09-09 1:45 ` Yang, Libin
2015-09-09 15:09 ` Daniel Vetter
2015-09-09 15:10 ` Takashi Iwai
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=20150904075453.GH22430@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--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