From: "pankaj.dubey" <pankaj.dubey@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
linux-arm-kernel@lists.infradead.org, balbi@kernel.org,
gregkh@linuxfoundation.org, kgene@kernel.org,
javier@osg.samsung.com, linux-samsung-soc@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling
Date: Wed, 11 Jan 2017 08:13:38 +0530 [thread overview]
Message-ID: <f32657c2-a0b7-b84c-e5d6-eb33f7705880@samsung.com> (raw)
In-Reply-To: <20170110182552.coom4p6dpdqo2ljv@kozik-lap>
Hi Krzysztof,
On Tuesday 10 January 2017 11:55 PM, Krzysztof Kozlowski wrote:
> On Tue, Jan 10, 2017 at 06:09:40PM +0100, Bartlomiej Zolnierkiewicz wrote:
>> BTW What is interesting is that the Exynos7 dts patch [2] has never
>> made it into upstream for some reason. In the meantime however
>> Exynos5433 (similar to Exynos7 to some degree) became the user of
>> susp_clk.
>>
>> [1] https://lkml.org/lkml/2014/11/21/247
>> [2] https://patchwork.kernel.org/patch/5355161/
>>
>
> +Cc Alim and Pankaj,
>
> Anyone would like to resend [2] after rebasing and testing? Interrupt
> flags would have to be fixed and status=disabled added.
>
Thanks for looping us into this thread.
Well I will be taking care of Exynos USB as Vivek has left Samsung.
I am currently working on adding Exynos7 USB support, as soon as patches
are ready for posting will post them. Will take care of review comments
given for Vivek's patchset [1].
Thanks,
Pankaj Dubey
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2017-01-11 2:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 2:21 Shuah Khan
2017-01-10 11:20 ` Sergei Shtylyov
2017-01-10 14:38 ` Shuah Khan
[not found] ` <CGME20170110120605epcas1p1c26f7f90fca4765ab9cc339c51d11347@epcas1p1.samsung.com>
2017-01-10 12:05 ` Bartlomiej Zolnierkiewicz
2017-01-10 14:16 ` Shuah Khan
2017-01-10 14:36 ` Shuah Khan
[not found] ` <CGME20170110160532epcas1p198cef8317dcbc8740366d06b38e7465f@epcas1p1.samsung.com>
2017-01-10 16:05 ` Bartlomiej Zolnierkiewicz
2017-01-10 16:28 ` Shuah Khan
[not found] ` <CGME20170110170942epcas1p3decee28366d7d42b70e7b0669b97326f@epcas1p3.samsung.com>
2017-01-10 17:09 ` Bartlomiej Zolnierkiewicz
2017-01-10 17:49 ` vivek.gautam
2017-01-10 18:25 ` Krzysztof Kozlowski
2017-01-11 2:43 ` pankaj.dubey [this message]
2017-01-10 17:53 ` Anand Moon
[not found] ` <CGME20170110180359epcas1p4729103fd575fe628bfd3ea7966ec4856@epcas1p4.samsung.com>
2017-01-10 18:03 ` Bartlomiej Zolnierkiewicz
[not found] ` <CGME20170110182345epcas1p3112f94aad300625ff1f75860c55a2b7e@epcas1p3.samsung.com>
2017-01-10 18:23 ` Bartlomiej Zolnierkiewicz
2017-01-10 18:37 ` Shuah Khan
2017-01-10 18:59 ` Krzysztof Kozlowski
2017-01-10 19:20 ` Shuah Khan
2017-01-10 18:36 ` Anand Moon
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=f32657c2-a0b7-b84c-e5d6-eb33f7705880@samsung.com \
--to=pankaj.dubey@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=vivek.gautam@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®