From: Trilok Soni <tsoni@codeaurora.org>
To: Prakruthi Deepak Heragu <pheragu@codeaurora.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ckadabi@codeaurora.org,
bryanh@codeaurora.org, psodagud@codeaurora.org,
rnayak@codeaurora.org
Subject: Re: [PATCH v1 0/2] Add Embedded USB Debugger (EUD) driver
Date: Fri, 31 Aug 2018 09:03:42 -0700 [thread overview]
Message-ID: <51874c59-46d0-363d-bb53-af9450207194@codeaurora.org> (raw)
In-Reply-To: <1534464348-8227-1-git-send-email-pheragu@codeaurora.org>
On 8/16/2018 5:05 PM, Prakruthi Deepak Heragu wrote:
> This is a series of patches that implements a driver for the control
> peripheral, EUD (Embedded USB Debugger). The EUD is a mini-USB hub
> implemented on chip to support the USB-based debug and trace capabilities.
> Apart from debug capabilities, EUD has a control peripheral. Control
> Peripheral is on when EUD is on and gets signals like USB attach, pet EUD,
> charge phone etc. EUD driver listens to events like USB attach or detach
> and charger enable or disable and then notifies the USB driver or PMIC
> driver respectively about these events via EXTCON. At regular intervals,
> the EUD driver receives an interrupt to pet the driver indicating that
> the software is functional.
Any other review comments on this patch series?
---Trilok Soni
next prev parent reply other threads:[~2018-08-31 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 0:05 Prakruthi Deepak Heragu
2018-08-17 0:05 ` [PATCH v1 1/2] dt-bindings: Documentation for qcom,eud Prakruthi Deepak Heragu
2018-08-17 0:05 ` [PATCH v1 2/2] Embedded USB Debugger (EUD) driver Prakruthi Deepak Heragu
2018-08-17 19:47 ` Trilok Soni
2018-08-20 16:59 ` pheragu
2018-08-31 16:03 ` Trilok Soni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-17 0:01 [PATCH v1 0/2] Add " Prakruthi Deepak Heragu
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=51874c59-46d0-363d-bb53-af9450207194@codeaurora.org \
--to=tsoni@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pheragu@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=rnayak@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
all inboxes | Powered by JetHome®