linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pheragu@codeaurora.org
To: Trilok Soni <tsoni@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	ckadabi@codeaurora.org, bryanh@codeaurora.org,
	psodagud@codeaurora.org,
	Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
Subject: Re: [PATCH 2/2] Embedded USB Debugger (EUD) driver
Date: Tue, 31 Jul 2018 12:32:05 -0700	[thread overview]
Message-ID: <631fd296787321ce3fa27f9c9b8b3841@codeaurora.org> (raw)
In-Reply-To: <1a34e079-929c-5ac1-c4e9-85ce707c42e0@codeaurora.org>

On 2018-07-31 12:29, Trilok Soni wrote:
> Hi Prakruthi,
> 
> On 7/31/2018 11:22 AM, Prakruthi Deepak Heragu wrote:
>> Add support for control peripheral of EUD (Embedded USB Debugger) to
>> listen to events such as USB attach/detach, charger enable/disable, 
>> pet
>> EUD to indicate software is functional.
> 
> We should CC linux-usb mailing list too?
> 
Sure. Will get the id and do it.
>> +
>> +config QCOM_EUD
>> +	tristate "QTI Embedded USB Debugger (EUD)"
>> +	depends on ARCH_QCOM
>> +	select SERIAL_CORE
> 
> We don't need to select SERIAL_CORE since there is nothing related to
> serial console in this driver.
Yes, I will take it off. Shall I send a version 1?

      reply	other threads:[~2018-07-31 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 18:22 [PATCH 0/2] Add Embedded USB Debugger (EUD) driver Prakruthi Deepak Heragu
2018-07-31 18:22 ` [PATCH 1/2] dt-bindings: Documentation for qcom,eud Prakruthi Deepak Heragu
2018-08-01 14:04   ` Rob Herring
2018-08-02 18:44     ` pheragu
2018-08-02 21:23       ` Rob Herring
2018-07-31 18:22 ` [PATCH 2/2] Embedded USB Debugger (EUD) driver Prakruthi Deepak Heragu
2018-07-31 19:29   ` Trilok Soni
2018-07-31 19:32     ` pheragu [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=631fd296787321ce3fa27f9c9b8b3841@codeaurora.org \
    --to=pheragu@codeaurora.org \
    --cc=bryanh@codeaurora.org \
    --cc=ckadabi@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psodagud@codeaurora.org \
    --cc=satyap@codeaurora.org \
    --cc=tsoni@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 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).