[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1392744420.17130.24.camel@iivanov-dev>
Date: Tue, 18 Feb 2014 19:27:00 +0200
From: "Ivan T. Ivanov" <iivanov@...sol.com>
To: Josh Cartwright <joshc@...eaurora.org>
Cc: Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Rob Landley <rob@...dley.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
David Brown <davidb@...eaurora.org>,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 1/3] usb: chipidea: msm: Add device tree binding
information
Hi,
On Tue, 2014-02-18 at 10:13 -0600, Josh Cartwright wrote:
> On Tue, Feb 18, 2014 at 03:21:19PM +0200, Ivan T. Ivanov wrote:
> > From: "Ivan T. Ivanov" <iivanov@...sol.com>
> >
> > Document device tree binding information as required by
> > the Qualcomm USB controller.
> >
> > Signed-off-by: Ivan T. Ivanov <iivanov@...sol.com>
> > ---
> > .../devicetree/bindings/usb/msm-hsusb.txt | 17 +++++++++++++++++
>
> Is this really the appropriate place to document this? It seems like
> this binding doc should be merged with the i.MX ci13xxx binding in a
> common ci13xxx doc.
>
This driver is a "glue" layer driver which control Qualcomm
specific logic around Chipidea IP core. It is supposed to
hold "non standard" Chipidea properties, but I suppose that
ci-hdrc-qcom.txt will be better name and will be similar to
i.MX chosen name.
What do you think?
Regards,
Ivan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists