From: Kishon Vijay Abraham I <kishon@ti.com>
To: Sachin Kamat <spk.linux@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>,
Vivek Gautam <gautam.vivek@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH v2 1/2] phy: Kconfig: Re-organize Exynos USB 2.0 PHY configs
Date: Mon, 14 Jul 2014 14:32:04 +0530 [thread overview]
Message-ID: <53C39C8C.6060604@ti.com> (raw)
In-Reply-To: <CAK5sBcG+UZ86cAFKoAf4Y62yrOafpzBGd-wz=PqWJRg1g8pOFQ@mail.gmail.com>
On Monday 14 July 2014 02:29 PM, Sachin Kamat wrote:
> Hi,
>
> On Mon, Jul 14, 2014 at 2:26 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>> Hi,
>>
>> On Wednesday 09 July 2014 05:19 PM, Sachin Kamat wrote:
>>> Since the USB 2.0 PHYs are required with EHCI/OHCI USB drivers and
>>> USB gadget controller supported by the DWC2 gadget driver, make it
>>> depend on them and default to ARCH_EXYNOS as they are meant for
>>> Exynos platforms. Also, make the sub-drivers silent options enabling
>>> them based on the SoC platforms that they are meant to work with. This
>>> will make life easier for end users who do not have any way knowing the
>>> dependencies.
>>
>> There is a new Exynos PHY in town, Exynos 3250. Can you rebase your patch on
>> top of that?
>
> Sure. But I did not see it in linux-next yet. Is it merged somewhere?
It's in the list. I can push it to my tree if that helps.
-Kishon
>
next prev parent reply other threads:[~2014-07-14 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 11:49 Sachin Kamat
2014-07-09 11:49 ` [PATCH v2 2/2] phy: Kconfig: Update config for Exynos USB DRD Sachin Kamat
2014-07-10 6:51 ` Jingoo Han
2014-07-10 6:50 ` [PATCH v2 1/2] phy: Kconfig: Re-organize Exynos USB 2.0 PHY configs Jingoo Han
2014-07-14 8:56 ` Kishon Vijay Abraham I
2014-07-14 8:59 ` Sachin Kamat
2014-07-14 9:02 ` Kishon Vijay Abraham I [this message]
2014-07-14 9:06 ` Sachin Kamat
2014-07-14 9:09 ` Kishon Vijay Abraham I
2014-07-14 9:11 ` Sachin Kamat
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=53C39C8C.6060604@ti.com \
--to=kishon@ti.com \
--cc=dianders@chromium.org \
--cc=gautam.vivek@samsung.com \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=spk.linux@gmail.com \
--cc=tomasz.figa@gmail.com \
/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
Powered by JetHome