From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ramalingam C <ramalingam.c@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
seanpaul@chromium.org, tomas.winkler@intel.com,
uma.shankar@intel.com, ville.syrjala@linux.intel.com,
chris@chris-wilson.co.uk,
Kate Stewart <kstewart@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 04/39] component: alloc component_match without any comp to match
Date: Wed, 19 Dec 2018 16:04:59 +0100 [thread overview]
Message-ID: <20181219150459.GA25653@kroah.com> (raw)
In-Reply-To: <20181219134245.GB21184@phenom.ffwll.local>
On Wed, Dec 19, 2018 at 02:42:45PM +0100, Daniel Vetter wrote:
> On Thu, Dec 13, 2018 at 09:31:06AM +0530, Ramalingam C wrote:
> > If all the components associated to a component master is not added
> > to the component framework due to the HW capability or Kconfig
> > selection, component_match will be NULL at
> > component_master_add_with_match().
> >
> > To avoid this, component_match_alloc() is added to the framework,
> > to allcoate the struct component_match with zero associated components.
> > Hence component master can be added with a component_match with zero
> > associated components.
> >
> > This helps the component master bind call to get triggered,
> > even if no component is registered for that particular master.
> >
> > This is meant for big PCI device drivers where small/optional
> > features are external components, and based on usecases different
> > combination of components are build as entire driver.
> >
> > In such PCI device driver Load, if we use the component master for
> > waiting for few components(features) availability, only if they are
> > supported by the underlying HW, then we need to allocate memory for
> > component_match using the API introduced in this change before
> > the call to component_master_add_with_match.
> >
> > v2:
> > No Change.
> >
> > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Kate Stewart <kstewart@linuxfoundation.org>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Philippe Ombredanne <pombredanne@nexb.com>
> > Cc: linux-kernel@vger.kernel.org
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> Greg, I expect the i915 feature that needs this will only land in 4.22.
> I'm also not aware of anyone else using this (all the other component
> users always use components). How do you want to get this landed?
>
> I think either getting this into 4.21, or an ack for merging through drm
> trees would work well for us.
I have no objection to you taking this through the drm tree. As I
really do not know the component code at all (that would be Russell
King), feel free to add my:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
as it looks sane to me.
thanks,
greg k-h
next prev parent reply other threads:[~2018-12-19 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1544673701-6353-1-git-send-email-ramalingam.c@intel.com>
2018-12-13 4:01 ` [PATCH v9 04/39] component: alloc component_match without any comp to match Ramalingam C
2018-12-19 13:42 ` Daniel Vetter
2018-12-19 15:04 ` Greg Kroah-Hartman [this message]
[not found] <1544650998-31192-1-git-send-email-ramalingam.c@intel.com>
2018-12-12 21:42 ` Ramalingam C
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=20181219150459.GA25653@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=ramalingam.c@intel.com \
--cc=seanpaul@chromium.org \
--cc=tglx@linutronix.de \
--cc=tomas.winkler@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@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