From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Ramalingam C <ramalingam.c@intel.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH 2/4] components: multiple components for a device
Date: Fri, 8 Feb 2019 12:52:09 +0100 [thread overview]
Message-ID: <20190208115209.GB19392@kroah.com> (raw)
In-Reply-To: <20190207232759.14553-2-daniel.vetter@ffwll.ch>
On Fri, Feb 08, 2019 at 12:27:57AM +0100, Daniel Vetter wrote:
> Component framework is extended to support multiple components for
> a struct device. These will be matched with different masters based on
> its sub component value.
>
> We are introducing this, as I915 needs two different components
> with different subcomponent value, which will be matched to two
> different component masters(Audio and HDCP) based on the subcomponent
> values.
>
> v2: Add documenation.
>
> v3: Rebase on top of updated documenation.
>
> v4: Review from Rafael:
> - Remove redundant "This" from kerneldoc (also in the previous patch)
> - Streamline the logic in find_component() a bit.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> (v1 code)
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com> (v1 commit message)
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Cc: Rafael J. Wysocki <rafael@kernel.org>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-02-08 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 23:27 [PATCH 1/4] component: Add documentation Daniel Vetter
2019-02-07 23:27 ` [PATCH 2/4] components: multiple components for a device Daniel Vetter
2019-02-07 23:30 ` Rafael J. Wysocki
2019-02-08 10:28 ` Russell King - ARM Linux admin
2019-02-08 15:23 ` Daniel Vetter
2019-02-08 15:36 ` Daniel Vetter
2019-02-08 11:52 ` Greg Kroah-Hartman [this message]
2019-02-07 23:27 ` [PATCH 3/4] drm/doc: document recommended component helper usage Daniel Vetter
2019-02-07 23:27 ` [PATCH 4/4] i915/snd_hdac: I915 subcomponent for the snd_hdac Daniel Vetter
2019-02-08 11:51 ` [PATCH 1/4] component: Add documentation Greg Kroah-Hartman
2019-02-08 15:29 ` Daniel Vetter
2019-02-08 15:45 ` Daniel Vetter
2019-02-18 3:31 ` Randy Dunlap
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=20190208115209.GB19392@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--cc=ramalingam.c@intel.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rodrigo.vivi@intel.com \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).