The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/hwspinlock/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
index 73a401662853
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/irqchip/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
index 00bbec6eca0b..10775b099daa 100644
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/phy/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/phy/Kconfig b/drivers/phy/Kconfig
index 0124d17bd9fe..cfdb3551a675 100644
--- a
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/reset/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
index 0a6408a39c66
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/soc/qcom/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig
index 461b387d03cc..24de48134c15
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/usb/host/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index 8c20ebbc049c..f759a778d606
in
of_syscon_register")
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index aa21dc55eb15..2e5b1e525a1d 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -1034,6 +103
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/staging/media/omap4iss/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/media/omap4iss/Kconfig
b/drivers/staging/media/omap4iss
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/pinctrl/mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pinctrl/mvebu/Kconfig b/drivers/pinctrl/mvebu/Kconfig
index 170602407c0d
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/media/platform/Kconfig| 1 +
drivers/media/platform/exynos4-is/Kconfig | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/media
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 0da40e2e4280..5c530b6b125d 100644
--- a
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/net/ethernet/hisilicon/Kconfig | 1 +
drivers/net/ethernet/stmicro/stmmac/Kconfig | 6 ++
drivers/net/ethernet/ti/Kconfig | 1 +
3 files
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clocksource/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index c346be650892
9 && LPC18XX_DMAMUX && VIDEO_OMAP4 && HWSPINLOCK_QCOM && ATMEL_ST
&& QCOM_GSBI && PHY_HI6220_USB)
selects MFD_SYSCON which has unmet direct dependencies (HAS_IOMEM)
Best regards,
Krzysztof
Krzysztof Kozlowski (15):
clocksource: atmel: Add missing MFD_
The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
direct dependencies.
Signed-off-by: Krzysztof Kozlowski
---
drivers/dma/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index c77f214c9466..7fbf96bff280 100644
--- a
2016-03-03 19:53 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:30 Krzysztof Kozlowski wrote:
>> config ST_IRQCHIP
>> bool
>> select REGMAP
>> + depends on HAS_IOMEM# For MFD_SYSCON
>> select MFD_SYSCON
>>
2016-03-03 19:50 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:41 Krzysztof Kozlowski wrote:
>> Since commit c89c0114955a ("mfd: syscon: Set regmap max_register in
>> of_syscon_register") the syscon uses ioremap so it fails on COMPILE_TEST
>> witho
2016-03-03 21:33 GMT+09:00 Sebastian Reichel :
> Hi,
>
> On Thu, Mar 03, 2016 at 12:00:14PM +0100, Arnd Bergmann wrote:
>> On Thursday 03 March 2016 17:03:37 Krzysztof Kozlowski wrote:
>> > diff --git a/drivers/power/reset/Kconfig b/drivers/power/reset/Kconfig
>> >
2016-03-03 19:57 GMT+09:00 Arnd Bergmann :
> On Thursday 03 March 2016 17:03:35 Krzysztof Kozlowski wrote:
>> diff --git a/drivers/media/platform/Kconfig b/drivers/media/platform/Kconfig
>> index 201f5c296a95..e5931e434fa2 100644
>> --- a/drivers/media/platform/Kconfig
&
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/staging/media/omap4iss/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/soc/qcom/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/pinctrl/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
2016-03-03 17:03 GMT+09:00 Krzysztof Kozlowski :
> The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet
> direct dependencies.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/pinctrl/mvebu/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> d
On Fri, Apr 01, 2016 at 04:59:15PM +0530, Vivek Gautam wrote:
> Adding vendor specific directories in phy to group
> phy drivers under their respective vendor umbrella.
>
> Signed-off-by: Vivek Gautam
> ---
>
> With growing number of phy drivers, it makes sense to
> group these drivers under the
test on X2 and other
configurations and bootloaders.
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
usb: misc: usb3503: Fix HUB mode after bootloader initialization
ARM: dts: exynos: Provide regulator for usb3503 on Odroid to fix
device detection
regulator: max77686: Configure enable tim
The enable time for buck regulators was not configured but actually is
essential: consumers, like usb3503, doing hard reset (regulator off/on)
should wait for the regulator to settle.
Configure the enable time according to datasheet.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator
work for usb3503.
Signed-off-by: Krzysztof Kozlowski
---
Tested on Odroid U3 so far. Please kindly test on X2 or other
configurations and bootloaders.
---
Documentation/devicetree/bindings/usb/usb3503.txt | 1 +
drivers/usb/misc/usb3503.c| 81 +++
2 fil
ovide one - buck8 on Odroid
U3.
Additionally switch the control of buck8 to GPIO mode. It is faster than
I2C/register mode and it is the easiest way to disable it (regulator
state is a logical OR state of GPIO and register value).
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos4
On 04/29/2016 01:30 PM, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 12:59:49PM +0200, Krzysztof Kozlowski wrote:
>
>> +++ b/Documentation/devicetree/bindings/usb/usb3503.txt
>> @@ -24,6 +24,7 @@ Optional properties:
>> pins (optional, if not provided, driver
On Sat, Apr 30, 2016 at 11:43:44AM +0200, Hans Verkuil wrote:
> Hi Krzysztof,
>
> On 04/29/2016 12:59 PM, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Patches are independent, please pick up as you wish.
> >
> > However all of them are needed to solve th
On Sun, May 01, 2016 at 06:01:08PM +0200, Hans Verkuil wrote:
> > Sorry, I meant the hanging issue I got in 4.6, not the ethernet issue.
> > I get the same problem with linux-next. Can you mail me the .config you are
> > using?
>
> Never mind.
>
> > After some more testing I don't think it is ha
On 04/29/2016 06:44 PM, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote:
>> On 04/29/2016 01:30 PM, Mark Brown wrote:
>
>>> Supplies are only optional if they may be physically absent. In this
>>> case it's possible th
On 05/02/2016 11:49 AM, Krzysztof Kozlowski wrote:
> On 04/29/2016 06:44 PM, Mark Brown wrote:
>> On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote:
>>> On 04/29/2016 01:30 PM, Mark Brown wrote:
>>
>>>> Supplies are only optional if the
On 05/02/2016 03:40 PM, Hans Verkuil wrote:
>>> Anyway, after disabling that config option I was finally able to test your
>>> patch
>>> series:
>>>
>>> Tested-by: Hans Verkuil
>
> BTW, one thing I noticed is that to have u-boot detect the network device I
> need to call 'usb reset' twice. This
Hi,
On Odroid XU4 with an external usb2514 hub (evaluation board from SMSC
or TI) connected to the USB2.0 port of EHCI controller, whenever I
plug some USB device into the usb2514 hub I see errors like:
[ 73.969179] exynos-ehci 1211.usb: port 1 resume error -110
[ 74.003259] usb 1-1: USB d
On Thu, Feb 09, 2017 at 11:26:48AM +0100, Richard Genoud wrote:
> I did some tests with XU3 and XU4, playing with USB2 and USB3 quirks
> (snps,dis_u{2,3}_susphy_quirk)
>
> kernel for the tests: next-20170206
> DTBs: exynos5422-odroidxu3-lite.dtb exynos5422-odroidxu4.dtb
>
> USB devices used for t
; @@ -10637,7 +10637,7 @@ RENESAS USB2 PHY DRIVER
> M: Yoshihiro Shimoda
> L: linux-renesas-...@vger.kernel.org
> S: Maintained
> -F: drivers/phy/phy-rcar-gen3-usb2.c
> +F: drivers/phy/renesas/phy-rcar-gen3-usb2.c
>
> RESET CONTROLLER FRAMEWORK
>
--
> drivers/regulator/max77693.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vg
t;regulator-always-on".
3. What about safeout regulator #2? On Trats2 it goes to USB_VBUS of
modem. Shouldn't it be enabled?
I'll test the patchset later at work on my boards.
As for the code:
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
> ---
> arch/arm
es found in nearby code (patches 4-6).
>
> I would like to get those patches merged separately to respective
> subsystem trees:
> patch 1: phy subsystem tree
> patch 2: Samsung Exynos tree
> patch 3: regulator subsystem tree
> patch 4-7: USB gadget subsystem tree
>
&g
On 25.08.2015 08:30, John Youn wrote:
> On 8/18/2015 11:54 AM, Felipe Balbi wrote:
>> this driver has long ago became dwc2.ko with
>> both peripheral and host roles, there's no point
>> in keeping the old function names.
>>
>> Signed-off-by: Felipe Balbi
>> ---
>> arch/arm/mach-s3c64xx/mach-crag6
On 25.08.2015 14:47, Marek Szyprowski wrote:
> Hello,
>
> On 2015-08-21 14:44, Kishon Vijay Abraham I wrote:
>> On Friday 21 August 2015 06:08 PM, Marek Szyprowski wrote:
>>> Exynos USB2 PHY has separate power supply, which is usually provided by
>>> VBUS regulator. This patch adds support for it.
2014-06-25 21:42 GMT+09:00 Vivek Gautam :
> Facilitate getting required 3.3V and 1.0V VDD supply for
> EHCI controller on Exynos.
>
> With the patches for regulators' nodes merged in 3.15:
> c8c253f ARM: dts: Add regulator entries to smdk5420
> 275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
On 07.06.2015 22:20, Anand Moon wrote:
> Facilitate getting required 3.3V and 1.0V VDD supply for
> EHCI controller on Exynos.
>
> With the patches for regulators' nodes merged in 3.15:
> c8c253f ARM: dts: Add regulator entries to smdk5420
> 275dcd2 ARM: dts: add max77686 pmic node for smdk5250,
>
2015-06-08 13:21 GMT+09:00 Anand Moon :
> Hi Krzysztof ,
>
> On 8 June 2015 at 07:40, Krzysztof Kozlowski wrote:
>> On 07.06.2015 22:20, Anand Moon wrote:
>>> Facilitate getting required 3.3V and 1.0V VDD supply for
>>> EHCI controller on Exynos.
>>>
2015-06-08 15:42 GMT+09:00 Javier Martinez Canillas :
> Hello,
>
> On Mon, Jun 8, 2015 at 7:14 AM, Krzysztof Kozlowski
> wrote:
>
> [...]
>
>>
>> To summarize my point of view:
>> 1. Unless Vivek's says otherwise, please give him the credits with
>&
W dniu 08.06.2015 o 19:20, Anand Moon pisze:
> On 8 June 2015 at 10:58, Vivek Gautam wrote:
>> Hi,
>>
(...)
>>
>> On Monday, June 08, 2015 10:44 AM, "Krzysztof Kozlowski"
>> wrote:
>>
>>> Untested code should not go to the kernel. Addit
.html
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
dt-bindings: usb: usb5303: Document new 'phys' property
usb: misc: usb3503: Allow usage of device through phy interface
ARM: dts: Fix usb3503 probe by enabling phy on exynos5250-arndale
Documentation/devicetree/bindings/usb/u
Document new 'phys' and 'phys-names' properties.
Signed-off-by: Krzysztof Kozlowski
Cc: Kevin Hilman
Cc: Arnd Bergmann
Cc: riku.voi...@linaro.org
Cc: Marek Szyprowski
---
Documentation/devicetree/bindings/usb/usb3503.txt | 4
1 file changed, 4 insertions(+)
diff -
. This lead to probe failure if PHY driver was
probed after usb3503 probe.
The patch adds support for generic phy framework so the driver will the
phy reference (if provided) and use it.
Signed-off-by: Krzysztof Kozlowski
Reported-by: Kevin Hilman
Reported-by: Arnd Bergmann
Cc: Kevin Hilman
Cc
On Arndale board (unlike Odroid U3) the USB3503 hub controller is
connected in phy mode (not through I2C). For successful probe it needs
to get reference to proper phy and enable it.
Signed-off-by: Krzysztof Kozlowski
Reported-by: Kevin Hilman
Reported-by: Arnd Bergmann
Cc: Kevin Hilman
Cc
On 07.10.2015 23:26, Marek Szyprowski wrote:
> Hello,
>
> On 2015-10-07 02:30, Krzysztof Kozlowski wrote:
>> Introduction
>>
>> This patchset tries to fix probing of usb3503 on Arndale board
>> if the Samsung PHY driver is probed later (or built as a
W dniu 10.10.2015 o 04:18, Kevin Hilman pisze:
> Hi Krzystof,
>
> Krzysztof Kozlowski writes:
>
>> Introduction
>>
>> This patchset tries to fix probing of usb3503 on Arndale board
>> if the Samsung PHY driver is probed later (or built as a
2015-10-09 22:00 GMT+09:00 Luis de Bethencourt :
> Since hid_connect() only cares about hiddev_connect() succeeding or
> failing, there is no need for this function to return an int and it can
> return a bool instead.
It can return bool but it would not be in line with kernel coding
style. The hid
On 20.10.2015 00:11, Luis de Bethencourt wrote:
> On 13/10/15 02:49, Krzysztof Kozlowski wrote:
>> 2015-10-09 22:00 GMT+09:00 Luis de Bethencourt :
>>> Since hid_connect() only cares about hiddev_connect() succeeding or
>>> failing, there is no need for this function
ed-by: Rob Herring
> Signed-off-by: Marek Szyprowski
> ---
> .../devicetree/bindings/usb/exynos-usb.txt| 41 +++----
> 1 file changed, 14 insertions(+), 27 deletions(-)
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
drivers/usb/host/ehci-exynos.c | 23 +++
> drivers/usb/host/ohci-exynos.c | 23 +++
> 2 files changed, 38 insertions(+), 8 deletions(-)
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On Fri, 26 Jul 2019 at 10:15, Marek Szyprowski wrote:
>
> Move USB PHYs to a standard arrays for Exynos EHCI/OHCI devices. This
> resolves the conflict between Exynos EHCI/OHCI sub-nodes and generic USB
> device bindings. Once the Exynos EHCI/OHCI sub-nodes are removed, the
> boards can finally pr
st regards,
Krzysztof
[1] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1569919.html
Krzysztof Kozlowski (10):
ARM: dts: exynos: Remove Exynos5440
ata: ahci-platform: Remove support for Exynos5440
cpufreq: exynos: Remove support for Exynos5440
clk: samsung: Remove support for
maintenance mode.
Remove all Device Tree sources for Exynos5440, as first step of removal
of the platform to simplify the code and drivers.
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/samsung-boards.txt| 2 -
arch/arm/boot/dts/Makefile | 2
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
---
Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt | 4 +---
drivers/i2c/busses
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
---
drivers/spi/spi-s3c64xx.c | 12
1 file changed, 12 deletions(-)
diff
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
---
drivers/usb/host/ehci-exynos.c | 7 ---
drivers/usb/host/ohci-exynos.c | 6
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
---
arch/arm/mach-exynos/Kconfig | 12
arch/arm/mach-exynos/common.h
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
---
drivers/pinctrl/samsung/Kconfig | 10 +-
drivers/pinctrl/samsung
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
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 1 -
drivers/ata
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
---
.../devicetree/bindings/thermal/exynos-thermal.txt | 14 +-
drivers/thermal
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
---
.../bindings/cpufreq/cpufreq-exynos5440.txt| 28 --
drivers/cpufreq
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
---
.../devicetree/bindings/clock/exynos5440-clock.txt | 28
drivers/clk/samsung
On Tue, Apr 24, 2018 at 10:50:58PM +0200, Arnd Bergmann wrote:
> On Tue, Apr 24, 2018 at 10:32 PM, Krzysztof Kozlowski wrote:
> > Hi,
> >
> >
> > Overview
> >
> > Let's continue the removal of old platforms. We already get rid of
>
. Miller
[krzk: Rebase on v4.4]
Signed-off-by: Krzysztof Kozlowski
---
drivers/net/usb/cdc_ether.c | 10 ++
drivers/net/usb/r8152.c | 2 ++
2 files changed, 12 insertions(+)
diff --git a/drivers/net/usb/cdc_ether.c b/drivers/net/usb/cdc_ether.c
index 6578127db847..f71abe50ea6f 100644
--- a
On Wed, Apr 25, 2018 at 2:49 PM, Sylwester Nawrocki
wrote:
> 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 s
On Thu, Apr 26, 2018 at 2:40 AM, Grant Grundler wrote:
> On Wed, Apr 25, 2018 at 2:54 AM, Krzysztof Kozlowski
> wrote:
>>
>> commit 90841047a01b452cc8c3f9b990698b264143334a upstream
>>
>> This linksys dongle by default comes up in cdc_ether mode.
>> This pa
On Thu, Apr 26, 2018 at 3:41 AM, Chanwoo Choi wrote:
> Hi Krzysztof,
>
> On 2018년 04월 25일 05:32, Krzysztof Kozlowski wrote:
>> The Exynos5440 is not actively developed, there are no development
>> boards available and probably there are no real products with it.
>> R
On Tue, Apr 24, 2018 at 10:32:39PM +0200, 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: Krzy
On Tue, Apr 24, 2018 at 10:32:30PM +0200, Krzysztof Kozlowski wrote:
> The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting
> server platforms but it did not make it to the market really. There are
> no development boards with it and probably there are no real products
On Tue, Apr 24, 2018 at 10:32:36PM +0200, 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: Krzy
On Tue, May 15, 2018 at 9:26 AM, Felipe Balbi wrote:
> Andrzej Hajda writes:
>
>> extcon device is used to detect host/device connection. Since extcon
>> OF property is deprecated, alternative method should be added.
>> This method uses OF graph bindings to locate extcon.
>>
>> Signed-off-by: And
On Tue, May 15, 2018 at 2:12 PM, Andrzej Hajda wrote:
> OF graph describes USB data lanes between USB-PHY and respective MUIC.
> Since graph is present and DWC driver can use it to get extcon, obsolete
> extcon property can be removed.
>
> Signed-off-by: Andrzej Hajda
> ---
> .../dts/exynos/exyn
On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
> OF graph describes USB data lanes between USB-PHY and respective MUIC.
> Since graph is present and DWC driver can use it to get extcon, obsolete
> extcon property can be removed.
>
> Signed-off-by: Andrzej Hajda
> ---
> arch/arm64/boot/dts
On Thu, Feb 1, 2018 at 9:19 AM, Andrzej Hajda wrote:
> On 01.02.2018 08:50, Krzysztof Kozlowski wrote:
>> On Wed, Jan 31, 2018 at 4:57 PM, Andrzej Hajda wrote:
>>> OF graph describes USB data lanes between USB-PHY and respective MUIC.
>>> Since graph is present and D
On Thu, Feb 15, 2018 at 11:39 AM, Andrzej Hajda wrote:
> OF graph describes MHL data lanes between MHL and respective USB
> connector.
>
> Signed-off-by: Andrzej Hajda
> ---
> .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 31
> +++---
> 1 file changed, 28 insertions(+), 3
On Wed, Feb 21, 2018 at 9:55 AM, Andrzej Hajda wrote:
> OF graph describes MHL data lanes between MHL and respective USB
> connector.
>
> Signed-off-by: Andrzej Hajda
> ---
> v4:
> - added missing reg property in connector's port node (Krzysztof)
> ---
> .../boot/dts/exynos/exynos5433-tm2-common
On Tue, Mar 6, 2018 at 1:53 PM, Andrzej Hajda wrote:
> Hi Rob, Chanwoo, Krzysztof,
>
>
> On 27.02.2018 08:11, Andrzej Hajda wrote:
>> Hi,
>>
>> Thanks for reviews of previous iterations.
>>
>> This patchset introduces USB physical connector bindings, together with
>> working example.
>> I have rem
On Tue, Feb 27, 2018 at 08:11:31AM +0100, Andrzej Hajda wrote:
> Since USB connector bindings are available we can describe it on TM2(e).
>
> Signed-off-by: Andrzej Hajda
> ---
> arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 7 +++
> 1 file changed, 7 insertions(+)
>
Thanks, appl
On Tue, Feb 27, 2018 at 08:11:32AM +0100, Andrzej Hajda wrote:
> OF graph describes MHL data lanes between MHL and respective USB
> connector.
>
> Signed-off-by: Andrzej Hajda
> ---
> v5: removed extra parenthesis (kbuild test robot)
> v4: added missing reg property in connector's port node (Krzy
On Wed, Mar 7, 2018 at 12:13 PM, Andrzej Hajda wrote:
> Hi Chanwoo, Archit,
>
> On 07.03.2018 05:48, Chanwoo Choi wrote:
>> On 2018년 03월 07일 11:12, Chanwoo Choi wrote:
>>> Hi Rob and Andrzej,
>>>
>>> On 2018년 03월 06일 21:53, Andrzej Hajda wrote:
Hi Rob, Chanwoo, Krzysztof,
On 27
On Wed, Feb 15, 2017 at 09:38:09AM +0800, Peter Chen wrote:
> On Tue, Feb 14, 2017 at 12:21:48PM +0200, Roger Quadros wrote:
> > Peter,
> >
> > On 11/02/17 03:27, Peter Chen wrote:
> > > Hi all,
> > >
> > > This is a follow-up for my last power sequence framework patch set [1].
> > > According to
On Wed, May 17, 2017 at 12:58:38PM +0200, Richard Leitner wrote:
> Hello,
> due to the fact (all?) the Microchip (former SMSC) USB hubs share the
> same I2C configuration interface, I'm currently working on harmonizing
> those USB Hub drivers. Currently this affects the usb251xb, usb3503 and
> usb4
On Thu, May 18, 2017 at 7:33 AM, Richard Leitner wrote:
>>> 2. What would be a good prefix for common headers/functions/macros/etc.?
>>> I thought of "mcusbhub"... Would that be OK? Or are there any
>>> conventions/better proposals on that?
>>
>>
>> If you are going to develop one driver for entir
ard-h2.c | 2 +-
> arch/arm/mach-omap1/board-h3-mmc.c | 2 +-
> arch/arm/mach-omap1/board-h3.c | 2 +-
> arch/arm/mach-omap1/board-osk.c | 2 +-
> arch/arm/mach-s3c24xx/mach-osiris-dvs.c | 2 +-
> arch/arm/mach-s3c24xx/mach-osiris.c | 2 +-
For s3c24xx:
On Mon, Jun 12, 2017 at 04:45:14PM +0530, Arvind Yadav wrote:
> clk_prepare_enable() can fail here and we must check its return value.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/usb/host/ehci-exynos.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
R
-)
>
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
--
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
Since commit bd8ce544ec35 ("usb: dwc3: exynos: Make provision for vdd
regulators") vdd33-supply and vdd10-supply are required so document them
in bindings.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/usb/exynos-usb.txt | 4
1 file changed, 4 insertion
On Wed, Jul 19, 2017 at 09:13:29PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Anand Moon writes:
> > Hi Krzysztof,
> >
> > Today I tried to compile the latest kernel for Odroid xu4.
> > using exynos_defconfig I build and loaded the kernel.
> > but to my surprise usb 3.0 device and missing.
> >
> > o
On Mon, Sep 18, 2017 at 12:02:13PM +0200, Andrzej Pietrasiewicz wrote:
> Odroid XU4 board does not enumerate SuperSpeed devices.
> This patch makes exynos5 series chips use USB SUSPHY quirk,
> which solves the problem.
>
> Signed-off-by: Andrzej Pietrasiewicz
> ---
> arch/arm/boot/dts/exynos54xx
On Fri, Sep 22, 2017 at 10:18:54AM +0200, Andrzej Pietrasiewicz wrote:
> Hi,
>
> W dniu 19.09.2017 o 20:10, Robin Murphy pisze:
> > On 19/09/17 18:40, Krzysztof Kozlowski wrote:
> > > On Mon, Sep 18, 2017 at 12:02:13PM +0200, Andrzej Pietrasiewicz wrote:
> >
On Tue, Sep 18, 2018 at 10:16:53AM +0200, Marek Szyprowski wrote:
> Update DWC3 hardware modules to Exynos5433 specific variant: change
> compatible name and add all required clocks (both to the glue node and
> DWC3 core node).
>
> Signed-off-by: Marek Szyprowski
> ---
> arch/arm64/boot/dts/exyn
On Fri, Sep 21, 2018 at 03:13:55PM +0200, Andrzej Hajda wrote:
> OF graph describes USB data lanes between USB-PHY and respective MUIC.
> Since graph is present and DWC driver can use it to get extcon, obsolete
> extcon property can be removed.
>
> Signed-off-by: Andrzej Hajda
> ---
> v3:
> - re
On Tue, Sep 18, 2018 at 10:16:53AM +0200, Marek Szyprowski wrote:
> Update DWC3 hardware modules to Exynos5433 specific variant: change
> compatible name and add all required clocks (both to the glue node and
> DWC3 core node).
>
> Signed-off-by: Marek Szyprowski
> ---
> arch/arm64/boot/dts/exyn
101 - 200 of 203 matches
Mail list logo
