From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-usb@vger.kernel.org, Fabian Vogt <fabian@ritter-vogt.de>,
Yuan-Hsin Chen <yhchen@faraday-tech.com>,
Felipe Balbi <balbi@kernel.org>
Subject: Re: [PATCH 1/3 v1] usb: fotg210: Collect pieces of dual mode controller
Date: Wed, 9 Nov 2022 12:38:17 +0100 [thread overview]
Message-ID: <Y2uRKeTSOc2ofy4e@kroah.com> (raw)
In-Reply-To: <CACRpkda=nbOcXSMNjnJjhL6KaCk_yYD42tSZ3qcxD2bBDWQ2Ag@mail.gmail.com>
On Mon, Nov 07, 2022 at 12:20:14AM +0100, Linus Walleij wrote:
> On Sun, Oct 23, 2022 at 4:49 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > The Faraday FOTG210 is a dual-mode OTG USB controller that can
> > act as host, peripheral or both. To be able to probe from one
> > hardware description and to follow the pattern of other dual-
> > mode controllers such as MUSB or MTU3 we need to collect the
> > two, currently completely separate drivers in the same
> > directory.
> >
> > After this, users need to select the main symbol USB_FOTG210
> > and then each respective subdriver. We pave the road to
> > compile both drivers into the same kernel and select the
> > one we want to use at probe() time, and possibly add OTG
> > support in the end.
> >
> > This patch doesn't do much more than create the new symbol
> > and collect the drivers in one place. We also add a comment
> > for the section of dual-mode controllers in the Kconfig
> > file so people can see what these selections are about.
> >
> > Also add myself as maintainer as there has been little
> > response on my patches to these drivers.
> >
> > Cc: Fabian Vogt <fabian@ritter-vogt.de>
> > Cc: Yuan-Hsin Chen <yhchen@faraday-tech.com>
> > Cc: Felipe Balbi <balbi@kernel.org>
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
> Greg are these fine to merge? I have some more patches coming
> so I would like to establish these as a base.
Now queued up, sorry for the delay.
greg k-h
prev parent reply other threads:[~2022-11-09 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 14:47 [PATCH 1/3 v1] usb: fotg210: Collect pieces of dual mode controller Linus Walleij
2022-10-23 14:47 ` [PATCH 2/3 v1] usb: fotg210: Compile into one module Linus Walleij
2022-10-23 14:47 ` [PATCH 3/3 v1] usb: fotg210: Select subdriver by mode Linus Walleij
2022-10-23 15:33 ` [PATCH 1/3 v1] usb: fotg210: Collect pieces of dual mode controller Greg Kroah-Hartman
2022-10-23 19:41 ` Linus Walleij
2022-11-06 23:20 ` Linus Walleij
2022-11-09 11:38 ` Greg Kroah-Hartman [this message]
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=Y2uRKeTSOc2ofy4e@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=fabian@ritter-vogt.de \
--cc=linus.walleij@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=yhchen@faraday-tech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.