On Thu, Jun 26, 2014 at 11:09:37AM +0530, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
the respective USB configs to
Felipe,
On Fri, Jun 27, 2014 at 8:46 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jun 26, 2014 at 11:09:37AM +0530, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers
On Fri, Jun 27, 2014 at 08:55:31AM -0700, Doug Anderson wrote:
Felipe,
On Fri, Jun 27, 2014 at 8:46 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jun 26, 2014 at 11:09:37AM +0530, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC
Felipe,
On Fri, Jun 27, 2014 at 8:59 AM, Felipe Balbi ba...@ti.com wrote:
I'll admit to not having been involved with the previous discussions,
but this seems strange to me. Are we throwing in the towel and
deciding that it's too hard to get the Kconfigs right and that we'll
just rely on
On Fri, Jun 27, 2014 at 9:32 AM, Doug Anderson diand...@chromium.org wrote:
Felipe,
On Fri, Jun 27, 2014 at 8:59 AM, Felipe Balbi ba...@ti.com wrote:
I'll admit to not having been involved with the previous discussions,
but this seems strange to me. Are we throwing in the towel and
deciding
Hi Sachin,
On Thu, Jun 26, 2014 at 11:09 AM, Sachin Kamat sachin.ka...@samsung.com wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
Hi Vivek,
On Thu, Jun 26, 2014 at 1:39 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Hi Sachin,
On Thu, Jun 26, 2014 at 11:09 AM, Sachin Kamat sachin.ka...@samsung.com
wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers.
Hi Sachin,
On Thursday 26 June 2014 11:09 AM, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
the respective USB
Hi Vivek,
On Thu, Jun 26, 2014 at 1:55 PM, Sachin Kamat sachin.ka...@samsung.com wrote:
Hi Vivek,
On Thu, Jun 26, 2014 at 1:39 PM, Vivek Gautam gautam.vi...@samsung.com
wrote:
Hi Sachin,
On Thu, Jun 26, 2014 at 11:09 AM, Sachin Kamat sachin.ka...@samsung.com
wrote:
EHCI and OHCI
Hi Kishon,
On Thu, Jun 26, 2014 at 2:19 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
Hi Sachin,
On Thursday 26 June 2014 11:09 AM, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
Hi Sachin,
On Thu, Jun 26, 2014 at 2:23 PM, Sachin Kamat sachin.ka...@samsung.com wrote:
Hi Vivek,
On Thu, Jun 26, 2014 at 1:55 PM, Sachin Kamat sachin.ka...@samsung.com
wrote:
Hi Vivek,
On Thu, Jun 26, 2014 at 1:39 PM, Vivek Gautam gautam.vi...@samsung.com
wrote:
Hi Sachin,
On
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
the respective USB configs to make things easier for the end user.
While at it enable 5250 phy
On 06/26/2014 11:09 AM, Sachin Kamat wrote:
EHCI and OHCI drivers on Exynos platforms do not work without their
corresponding SoC specific phy drivers. Hence it makes no sense to
keep these phy drivers as user selectable. Instead select them from
the respective USB configs to make things
13 matches
Mail list logo
