nel.org>
Reviewed-by: Sylwester Nawrocki <s.nawro...@samsung.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
@kernel.org>
It's good you didn't remove S3C64XX_SPI_QUIRK_POLL entirely as it will
be needed for Exynos5433 ISP SPI controllers.
Reviewed-by: Sylwester Nawrocki <s.nawro...@samsung.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a mess
Cc: Jingoo Han
On 04/24/2018 10:32 PM, Krzysztof Kozlowski wrote:
> The Exynos5440 is not actively developed, there are no development
> boards available and probably there are no real products with it.
> Remove wide-tree support for Exynos5440.
>
> Signed-off-by: Krzysztof Kozlowski
On 10/05/2017 02:11 PM, Andrzej Pietrasiewicz wrote:
> +static int crport_handshake(struct exynos5_usbdrd_phy *phy_drd,
> + u32 val, u32 cmd)
> +{
> + u32 usec = 100;
> + unsigned int result;
> +
> + writel(val | cmd, phy_drd->reg_phy +
Hi,
On 07/21/2017 10:10 AM, Felipe Balbi wrote:
Jochen Sprickerhof writes:
I've send a patch for this some time ago here:
http://marc.info/?l=linux-usb=149945465112440=2
This goes along with the patch in this thread:
http://marc.info/?l=linux-usb=149983203023058=2
...@broadcom.com
Need your ACK for this patch.
For
drivers/media/platform/exynos4-is/Kconfig
drivers/video/fbdev/exynos/Kconfig
Acked-by: Sylwester Nawrocki s.nawro...@samsung.com
--
Thanks,
Sylwester
--
To unsubscribe from this list: send the line unsubscribe linux-usb
Hi Vivek,
On 25/11/14 12:48, Vivek Gautam wrote:
On Sat, Nov 22, 2014 at 8:42 PM, Kukjin Kim kg...@kernel.org wrote:
On 11/22/14 17:40, Kishon Vijay Abraham I wrote:
On Friday 21 November 2014 08:41 PM, Felipe Balbi wrote:
...
I took dwc3 driver patches.
I took the phy patches.
On 04/11/14 20:52, Paul Bolle wrote:
On Tue, 2014-11-04 at 11:42 -0800, Greg KH wrote:
As it's something that no one seemed to ever need before (i.e. it's not
a regression fix), but it would be a new feature, I don't think it's
really a stable fix.
But feel free to convince me
On 04/11/14 00:24, Greg KH wrote:
On Tue, Oct 07, 2014 at 11:12:07AM +0200, Sylwester Nawrocki wrote:
The PLAT_S5P Kconfig symbol was removed in commit d78c16ccde96
(ARM: SAMSUNG: Remove remaining legacy code). There are still
some references left, fix that by replacing them
...@tiscali.nl
Acked-by: Jingoo Han jg1@samsung.com
Cc: sta...@vger.kernel.org[3.17+]
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Changes since v2:
- updated the commit description.
drivers/usb/host/Kconfig |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The PLAT_S5P Kconfig symbol was removed in commit d78c16ccde96
(ARM: SAMSUNG: Remove remaining legacy code). There are still
some references left, fix that by replacing them with ARCH_S5PV210.
Reported-by: Paul Bolle pebo...@tiscali.nl
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
,
--
Sylwester Nawrocki
Samsung RD Institute Poland
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 28/04/14 08:17, Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Thereby, removing old phy-samsung-usb3 driver and related code
used
On 08/04/14 16:36, Vivek Gautam wrote:
diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
b/Documentation/devicetree/bindings/phy/samsung-phy.txt
index 28f9edb..6d99ba9 100644
--- a/Documentation/devicetree/bindings/phy/samsung-phy.txt
+++
Hi Vivek,
On 09/04/14 13:54, Vivek Gautam wrote:
Adding support to enable/disable VBUS hooked to a gpio
to enable vbus supply on the port.
Does the GPIO control a fixed voltage regulator ? If so, shouldn't
it be modelled by the regulator API instead ?
Signed-off-by: Vivek Gautam
On 09/04/14 14:24, Vivek Gautam wrote:
On Wed, Apr 9, 2014 at 5:41 PM, Sylwester Nawrocki
s.nawro...@samsung.com wrote:
On 09/04/14 13:54, Vivek Gautam wrote:
Adding support to enable/disable VBUS hooked to a gpio
to enable vbus supply on the port.
Does the GPIO control a fixed voltage
W dniu 2013-08-13 14:05, Kishon Vijay Abraham I pisze:
On Tuesday 13 August 2013 05:07 PM, Tomasz Figa wrote:
On Tuesday 13 of August 2013 16:14:44 Kishon Vijay Abraham I wrote:
On Wednesday 31 July 2013 11:45 AM, Felipe Balbi wrote:
On Wed, Jul 31, 2013 at 11:14:32AM +0530, Kishon Vijay
On 08/07/2013 07:06 PM, Julius Werner wrote:
This breaks compatibility, both for an old kernel and a new dt and a new
kernel with an old dt. Is anyone using these bindings?
They only affect Samsung SoCs and have only been upstream for half a
year, so I doubt it's heavily used.
It probably
On 07/24/2013 08:32 PM, Arnd Bergmann wrote:
On Tuesday 23 July 2013, Tomasz Figa wrote:
On Tuesday 23 of July 2013 17:14:20 Alan Stern wrote:
On Tue, 23 Jul 2013, Tomasz Figa wrote:
Where would you want to have those phy_address arrays stored? There
are no board files when booting with DT.
On 07/21/2013 05:48 PM, Greg KH wrote:
On Sun, Jul 21, 2013 at 12:22:48PM +0200, Sascha Hauer wrote:
On Sat, Jul 20, 2013 at 07:59:10PM -0700, Greg KH wrote:
On Sat, Jul 20, 2013 at 10:32:26PM -0400, Alan Stern wrote:
On Sat, 20 Jul 2013, Greg KH wrote:
That should be passed using platform
Hi,
On 06/18/2013 11:49 AM, Felipe Balbi wrote:
On Mon, Jun 17, 2013 at 12:16:35PM +0200, Sylwester Nawrocki wrote:
I have already used this API for our MIPI CSI-2/DSIM DPHYs driver,
the RFC patch series can be found at [1].
Thanks,
Sylwester
[1] http://www.spinics.net/lists/arm-kernel
Hi,
On 06/13/2013 10:43 AM, Kishon Vijay Abraham I wrote:
+/**
+ * phy_create() - create a new phy
+ * @dev: device that is creating the new phy
+ * @id: id of the phy
+ * @ops: function pointers for performing phy operations
+ * @label: label given to the phy
+ * @priv: private data from
Hi Kishon,
I've noticed there is a little inconsistency between the code and
documentation.
On 06/13/2013 10:43 AM, Kishon Vijay Abraham I wrote:
+3. Creating the PHY
+
+The PHY driver should create the PHY in order for other peripheral controllers
+to make use of it. The PHY framework
errors when
PHY Subsystem is kept as module and the dependent modules are built-in)
* Added if pm_runtime_enabled check before runtime pm calls.
Looks good, feel free to add:
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com for patches
1...3/9, 5...7/9
and Tested-by: Sylwester Nawrocki
Hi,
On 05/29/2013 07:38 AM, Kishon Vijay Abraham I wrote:
On Wednesday 29 May 2013 04:07 AM, Sylwester Nawrocki wrote:
On 04/29/2013 12:03 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users
On 04/29/2013 12:03 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider*
Hi,
On 06/04/2013 02:26 PM, Kishon Vijay Abraham I wrote:
+static inline int phy_init(struct phy *phy)
+{
+ pm_runtime_get_sync(phy-dev);
Hmm, no need to check return value here ? Also it looks a bit unexpected to
I purposely dint check the return values in order to support platforms
Hi Kishon,
On 04/29/2013 12:03 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY
On 04/15/2013 12:36 PM, Kishon Vijay Abraham I wrote:
On Monday 15 April 2013 03:50 PM, Grant Likely wrote:
On Wed, 20 Mar 2013 14:41:59 +0530, Kishon Vijay Abraham I kis...@ti.com
wrote:
Added a generic PHY framework that provides a set of APIs for the PHY
drivers
to create/destroy a PHY
Hi,
On 04/04/2013 11:21 AM, Kishon Vijay Abraham I wrote:
On Thursday 04 April 2013 03:16 AM, Sylwester Nawrocki wrote:
On 04/03/2013 02:53 PM, Kishon Vijay Abraham I wrote:
+4. Getting a reference to the PHY
+
+Before the controller can make use of the PHY, it has to get a
reference
On 04/03/2013 02:53 PM, Kishon Vijay Abraham I wrote:
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/phy-bindings.txt
@@ -0,0 +1,67 @@
+This document explains only the dt data binding. For general information about
s/dt data/device tree ?
+PHY subsystem refer Documentation/phy.txt
On 04/02/2013 12:38 AM, Stephen Warren wrote:
On 04/01/2013 04:27 PM, Sylwester Nawrocki wrote:
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
+example2:
+phys: phy {
+compatible = xxx;
+reg
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
b/Documentation/devicetree/bindings/phy/phy-bindings.txt
new file mode 100644
index 000..35696b2
--- /dev/null
+++
Hi Kishon,
On 03/20/2013 10:12 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. To obtain a reference to the PHY without
using
Hi,
On 01/23/2013 01:20 PM, Vivek Gautam wrote:
- { .compatible = samsung,exynos-dwc3 },
+ { .compatible = samsung,synopsis-dwc3 }
You're both missing a point here. The synopsys IP driver is called
dwc3.ko and that's compatible with synopsys,dwc3. Your glue layer driver
On 01/22/2013 06:35 AM, Kukjin Kim wrote:
- { .compatible = samsung,exynos-dwc3 },
+ { .compatible = samsung,synopsis-dwc3 },
Or if any version or something, how about following?
+ { .compatible = samsung,dwc-v3 },
Well, yes the newer SoCs with same IP using the chip name can
On 01/11/2013 09:08 AM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Thanks for addressing my all comments,
Reviewed-by: Sylwester Nawrocki s.nawro
Hi,
On 12/28/2012 10:13 AM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
...
--- a/Documentation/devicetree/bindings/usb/samsung-usbphy.txt
+++
On 12/26/2012 01:28 PM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 31
On 12/24/2012 09:13 AM, Vivek Gautam wrote:
These two changes look good to me. For both of them:
Reviewed-by: Doug Andersondiand...@chromium.org
Well, I have another idea. Yes, I know, specific chip name should be used.
But
you know the specific chip name in compatible can cause another
Hi,
On 12/26/2012 02:56 PM, Vivek Gautam wrote:
On Wed, Dec 26, 2012 at 5:58 PM, Vivek Gautamgautam.vi...@samsung.com wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
Hi,
On 12/19/2012 02:44 PM, Vivek Gautam wrote:
--- a/Documentation/devicetree/bindings/usb/samsung-usbphy.txt
+++ b/Documentation/devicetree/bindings/usb/samsung-usbphy.txt
@@ -9,3 +9,15 @@ Required properties:
- compatible : should be samsung,exynos4210-usbphy
- reg : base physical
Hi Vivek,
On 12/18/2012 02:56 PM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
Changes from v1:
- Changed the name of property for phy handler
On 12/18/2012 04:39 PM, Vivek Gautam wrote:
Adding base address information required for enabling
USB 3.0 DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
Hi Vivek,
On 11/06/2012 04:36 PM, Vivek Gautam wrote:
Adding base address information and required platform data
support for enabling USB DRD phy on exynos5250 SOC.
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi|3 ++-
On 11/07/2012 02:35 PM, Vivek Gautam wrote:
@@ -180,10 +273,12 @@ enum samsung_cpu_type {
/*
* struct samsung_usbphy - transceiver driver state
* @phy: transceiver structure
+ * @phy3: transceiver structure for USB 3.0
* @plat: platform data
* @dev: The parent device supplied
Hi,
I have a few comments. Please see below...
On 11/06/2012 04:36 PM, Vivek Gautam wrote:
Adding support for USB3.0 phy for dwc3 controller on
exynso5250 SOC.
exynso - exynos
Signed-off-by: Vivek Gautamgautam.vi...@samsung.com
---
drivers/usb/phy/samsung-usbphy.c| 337
47 matches
Mail list logo