From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Peter Chen <peter.chen@freescale.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 0/3] usb: chipidea: msm: Clean and fix glue layer driver
Date: Thu, 24 Apr 2014 17:31:31 +0300 [thread overview]
Message-ID: <1398349891.4724.233.camel@iivanov-dev> (raw)
In-Reply-To: <20140424003854.GA25407@shlinux1.ap.freescale.net>
Hi Peter,
On Thu, 2014-04-24 at 08:38 +0800, Peter Chen wrote:
> On Wed, Apr 23, 2014 at 03:28:01PM +0300, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
> >
> > This series intend to fix driver, which was broken for a while.
> > It is used to create peripheral role device, which in coordination
> > with phy-usb-msm driver could provide USB2.0 gadget support for
> > Qualcomm targets.
> >
> > Changes since version 3.
> >
> > - Fix typo in devicetree description file.
> >
> > Previews version can be found here:
>
> Since in your phy's patchset, you also access portsc which is in
> chipidea register region, it is not a standard way.
> In case, you will change something at chipidea driver in future
> when you re-work your next revision phy's patchset, I do not
> send this patchset to Greg right now.
>
Did you see problems with _this_ particular patch set? There is no
direct dependency between PHY patches and these changes.
Regards,
Ivan
> Once your phy's patchset has accepted, notify me. I will send
> this patchset to Greg.
>
> Peter
>
> >
> > https://lkml.org/lkml/2014/4/22/195
> >
> > Ivan T. Ivanov (3):
> > usb: chipidea: msm: Add device tree binding information
> > usb: chipidea: msm: Add device tree support
> > usb: chipidea: msm: Initialize offset of the capability registers
> >
> > .../devicetree/bindings/usb/ci-hdrc-qcom.txt | 17 +++++++++++++++
> > drivers/usb/chipidea/ci_hdrc_msm.c | 24 +++++++++++++++++++++-
> > 2 files changed, 40 insertions(+), 1 deletion(-)
> > create mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-qcom.txt
> >
> > --
> > 1.8.3.2
> >
> >
> >
>
next prev parent reply other threads:[~2014-04-24 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 12:28 [PATCH v4 0/3] usb: chipidea: msm: Clean and fix glue layer driver Ivan T. Ivanov
2014-04-23 12:28 ` [PATCH v4 2/3] usb: chipidea: msm: Add device tree support Ivan T. Ivanov
2014-04-23 12:28 ` [PATCH v4 3/3] usb: chipidea: msm: Initialize offset of the capability registers Ivan T. Ivanov
[not found] ` <1398256084-6815-1-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2014-04-23 12:28 ` [PATCH v4 1/3] usb: chipidea: msm: Add device tree binding information Ivan T. Ivanov
2014-04-23 12:28 ` Ivan T. Ivanov
2014-04-24 0:38 ` [PATCH v4 0/3] usb: chipidea: msm: Clean and fix glue layer driver Peter Chen
2014-04-24 0:38 ` Peter Chen
2014-04-24 14:31 ` Ivan T. Ivanov [this message]
2014-04-25 3:10 ` Peter Chen
2014-04-25 3:10 ` Peter Chen
2014-04-28 14:03 ` Ivan T. Ivanov
2014-04-29 0:45 ` Peter Chen
2014-04-29 6:40 ` Ivan T. Ivanov
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=1398349891.4724.233.camel@iivanov-dev \
--to=iivanov@mm-sol.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@freescale.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.