linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
	linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] usb: xhci-mtk: add generic compatible string
Date: Thu, 31 Aug 2017 18:03:43 +0200	[thread overview]
Message-ID: <20170831160343.GA11200@kroah.com> (raw)
In-Reply-To: <1503443673.17567.8.camel@mhfsdcap03>

On Wed, Aug 23, 2017 at 07:14:33AM +0800, Chunfeng Yun wrote:
> Hi, Mathias
> 
> On Wed, 2017-08-16 at 14:08 +0800, Chunfeng Yun wrote:
> > The xhci-mtk driver is a generic driver for MediaTek xHCI IP, add
> > a generic compatible to avoid confusion when support new SoCs but
> > use a compatible with specific SoC's name "mt8173".
> > 
> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> > ---
> >  drivers/usb/host/xhci-mtk.c |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c
> > index 67d5dc7..8fb6065 100644
> > --- a/drivers/usb/host/xhci-mtk.c
> > +++ b/drivers/usb/host/xhci-mtk.c
> > @@ -795,6 +795,7 @@ static int __maybe_unused xhci_mtk_resume(struct device *dev)
> >  #ifdef CONFIG_OF
> >  static const struct of_device_id mtk_xhci_of_match[] = {
> >  	{ .compatible = "mediatek,mt8173-xhci"},
> > +	{ .compatible = "mediatek,mtk-xhci"},
> >  	{ },
> >  };
> >  MODULE_DEVICE_TABLE(of, mtk_xhci_of_match);
> 
> Do you have any comment about this patch?
> Thanks.

We need an ack from the device-tree maintainers before we can take
them...

thanks,

greg k-h

  reply	other threads:[~2017-08-31 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  6:08 [PATCH v2 1/4] usb: mtu3: add generic compatible string Chunfeng Yun
2017-08-16  6:08 ` [PATCH v2 2/4] usb: xhci-mtk: " Chunfeng Yun
     [not found]   ` <33fa448238c0d95f0cfd6c2be3bd5c4e657a0cd4.1502854628.git.chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-22 23:14     ` Chunfeng Yun
2017-08-31 16:03       ` Greg Kroah-Hartman [this message]
     [not found]         ` <20170831160343.GA11200-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-08-31 16:08           ` Greg Kroah-Hartman
2017-08-16  6:08 ` [PATCH v2 3/4] dt-bindings: mt8173-mtu3: add generic compatible and rename file Chunfeng Yun
     [not found]   ` <2e43d8152c222264eb6c9d8299a824378c35a5a6.1502854628.git.chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-22  2:02     ` Rob Herring
2017-08-16  6:08 ` [PATCH v2 4/4] dt-bindings: mt8173-xhci: " Chunfeng Yun

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=20170831160343.GA11200@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathias.nyman@intel.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).