From: David Brown <davidb@codeaurora.org>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: gregkh@linuxfoundation.org, grant.likely@linaro.org,
rob.herring@calxeda.com, rob@landley.net, jslaby@suse.cz,
devicetree-discuss@lists.ozlabs.org,
linux-serial@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
mrana@codeaurora.org, sambley@codeaurora.org
Subject: Re: [PATCH v2] tty: serial: Add initial MSM UART High Speed Lite driver
Date: Fri, 26 Jul 2013 14:50:23 -0700 [thread overview]
Message-ID: <20130726215023.GA1470@codeaurora.org> (raw)
In-Reply-To: <1374476749-12763-1-git-send-email-iivanov@mm-sol.com>
On Mon, Jul 22, 2013 at 10:05:48AM +0300, Ivan T. Ivanov wrote:
>From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
>
>This is a tty driver with console support for Qualcomm's UART
>controllers found in the MSM8974 chipsets. Driver is completely
>based on implementation found in codeaurora.org msm_serial_hs_lite
>with Android dependences removed. Other changes include, moved to
>device managed resources and few cleanups.
>
>Driver functionality was tested in LEGACY_HSUART and BLSP_HSUART mode.
Ivan, do we need this driver with the fixes Stephen Boyd posted that
are supposed to fix the problems with the existing msm_serial.c
driver? If a single driver can correctly support both devices, that
seems like a better solution to me.
David
--
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-07-26 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:05 [PATCH v2] tty: serial: Add initial MSM UART High Speed Lite driver Ivan T. Ivanov
2013-07-26 21:50 ` David Brown [this message]
2013-07-29 9:52 ` 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=20130726215023.GA1470@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@mm-sol.com \
--cc=jslaby@suse.cz \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mrana@codeaurora.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sambley@codeaurora.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 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.