On Tue, Oct 06, 2015 at 09:28:50AM +0900, Krzysztof Kozlowski wrote:
> On 05.10.2015 21:47, Thierry Reding wrote:
> > Back when the PWM framework was introduced the concept of PWM lookup
> > tables was added to allow board code to register a table of PWM devices
> > and their association with consu
(add linux-samsung-soc mail list to cc)
On Tue, Oct 6, 2015 at 11:37 AM, Arnd Bergmann wrote:
> On Tuesday 06 October 2015 11:23:58 Pavel Fedin wrote:
>> Exynos platform officially uses "multi-core timer" AKA MCT. However, it
>> also has a possibility to access the same timer using CP15 (AKA
>> a
Hello,
On 2015-10-06 01:27, Felipe Balbi wrote:
John Youn writes:
Hi,
On 10/2/2015 12:45 AM, Marek Szyprowski wrote:
DWC2 module on some platforms needs three additional hardware
resources: phy controller, clock and power supply. All of them must be
enabled/activated to properly initialize
init_mutex is a leftover from the time, when s3c-hsotg driver did not
implement proper pull up/down control and emulated it by enabling
enabling/disabling usb phy. Proper pull up/down control has been added
by commit 5b9451f8c4fbaf0549139755fb45ff2b57975b7f ("usb: dwc2: gadget:
use soft-disconnect
DWC2 module on some platforms needs three additional hardware
resources: phy controller, clock and power supply. All of them must be
enabled/activated to properly initialize and operate. This was initially
handled in s3c-hsotg driver, which has been converted to 'gadget' part
of dwc2 driver. Unfort
Hello!
> My feeling is that is shouldn't be keyed off the presence of the device in DT
> though. Maybe we can find a way that allows you to put the device into DT
> but not have it used by default unless the user explicitly enables it, e.g.
> though
> a kernel command line option like "force_bro
On Tuesday 06 October 2015 12:44:54 Pavel Fedin wrote:
> Hello!
>
> > My feeling is that is shouldn't be keyed off the presence of the device in
> > DT
> > though. Maybe we can find a way that allows you to put the device into DT
> > but not have it used by default unless the user explicitly ena
On 02/10/15 20:37, Stephen Boyd wrote:
> On 10/02, Sylwester Nawrocki wrote:
...
> Thanks, pulled. I put this patch on top though.
Thanks for taking care of this, I'll make sure such issues
are fixed before sending any future pull requests.
--
Regards,
Sylwester
--
To unsubscribe from this list:
W dniu 06.10.2015 o 17:43, Thierry Reding pisze:
> On Tue, Oct 06, 2015 at 09:28:50AM +0900, Krzysztof Kozlowski wrote:
>> On 05.10.2015 21:47, Thierry Reding wrote:
>>> Back when the PWM framework was introduced the concept of PWM lookup
>>> tables was added to allow board code to register a table
On Tuesday 06 October 2015 07:57:33 Kukjin Kim wrote:
> Samsung fixes for v4.3
>
> - fix invalid clock used for FIMD IOMMU
> - fix thermal boot issue smdk5250-smdk5250
> - fix S2R on exynos4412 trats2 boards
> - fix LEDs on exynos5422-odroidxu3-common
> - fix booting of all 8 cores on exynos542x
>
Exynos USB2 PHY has separate power supply, which is usually provided by
VBUS regulator. This patch adds support for it. VBUS regulator is
optional, to keep compatibility with boards, which have VBUS provided
from some always-on power source.
Signed-off-by: Marek Szyprowski
---
This is just a rese
2015-10-06 22:41 GMT+09:00 Marek Szyprowski :
>
> Exynos USB2 PHY has separate power supply, which is usually provided by
> VBUS regulator. This patch adds support for it. VBUS regulator is
> optional, to keep compatibility with boards, which have VBUS provided
> from some always-on power source.
>
Hello,
On 2015-10-06 15:47, Krzysztof Kozlowski wrote:
2015-10-06 22:41 GMT+09:00 Marek Szyprowski :
Exynos USB2 PHY has separate power supply, which is usually provided by
VBUS regulator. This patch adds support for it. VBUS regulator is
optional, to keep compatibility with boards, which have
Hi,
On Tuesday 06 October 2015 07:39 PM, Marek Szyprowski wrote:
> Hello,
>
> On 2015-10-06 15:47, Krzysztof Kozlowski wrote:
>> 2015-10-06 22:41 GMT+09:00 Marek Szyprowski :
>>> Exynos USB2 PHY has separate power supply, which is usually provided by
>>> VBUS regulator. This patch adds support fo
Hello Kishon,
On 10/06/2015 04:29 PM, Kishon Vijay Abraham I wrote:
> On Tuesday 06 October 2015 07:39 PM, Marek Szyprowski wrote:
[snip]
>>
>> This was a pure resend, no changes to the patch has been made. I just
>> noticed
>> that it is over 6 weeks since the initial submission and the patch i
On Mon, Sep 07, 2015 at 03:44:36PM +0200, Hans Verkuil wrote:
> From: Hans Verkuil
>
> The added HDMI CEC framework provides a generic kernel interface for
> HDMI CEC devices.
>
> Signed-off-by: Hans Verkuil
> [k.deb...@samsung.com: Merged CEC Updates commit by Hans Verkuil]
> [k.deb...@samsung
On Mon, Sep 07, 2015 at 03:44:35PM +0200, Hans Verkuil wrote:
> From: Kamil Debski
>
> Add handling of remote control events coming from the HDMI CEC bus.
> This patch includes a new keymap that maps values found in the CEC
> messages to the keys pressed and released. Also, a new protocol has
> b
Gentle ping!
- Tobias
Tobias Jakobi wrote:
> The pinctrl settings in i2c_0 and i2c_1 are already provided
> through the exynos4 dtsi.
>
> Signed-off-by: Tobias Jakobi
> ---
> arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/arch/ar
Gentle ping!
- Tobias
Tobias Jakobi wrote:
> Use 'ldoN_reg: LDON' syntax and drop the deprecated
> 'regulator-compatible' property.
>
> Signed-off-by: Tobias Jakobi
> ---
> arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff -
Hi,
Introduction
This patchset tries to fix probing of usb3503 on Arndale board
if the Samsung PHY driver is probed later (or built as a module).
*The patchset was not tested on Arndale board.*
I don't have that board. Please test it and say if the usb3503 deferred probe
works fine
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 --git a/Documentation/de
The USB3503 hub controller can be connected through I2C interface (e.g.
on Odroid-U3 board) or directly by phy (e.g. on Arndale board). Thus the
usb3503 driver can act as a i2c or platform device.
In the second configuration (phy) the driver did not get a reference to
necessary phy to use it. This
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: Ar
There are different revisions of the same chipset. For example S2MPS13 has
more than 2 revisions. They differ slightly in regulator constraints.
Print the revision number to easily find which PMIC is used on the board.
Signed-off-by: Krzysztof Kozlowski
---
Changs since v1:
None.
---
drivers/m
The WRSTBI bit (disabled by default but enabled by bootloader), when
set, is responsible for resetting voltages to default values of
certain bucks on falling edge of Warm Reset Input pin from AP.
However on some boards (with S2MPS13) the pin is pulled down so any
suspend will effectively trigger t
Document a new Device Tree property 'samsung,s2mps11-wrstbi-ground'
indicating that WRSTBI pin of S2MPS13 PMIC is pulled down so
corresponding buck warm reset function should be disabled.
Signed-off-by: Krzysztof Kozlowski
---
Changs since v1:
None.
---
Documentation/devicetree/bindings/mfd/s2
On 05.10.2015 21:47, Thierry Reding wrote:
> Use a PWM lookup table to provide the PWM to the pwm-backlight device.
> The driver has a legacy code path that is required only because boards
> still use the legacy method of requesting PWMs by global ID. Replacing
> these usages allows that legacy fal
On 05.10.2015 21:47, Thierry Reding wrote:
> Use a PWM lookup table to provide the PWM to the pwm-backlight device.
> The driver has a legacy code path that is required only because boards
> still use the legacy method of requesting PWMs by global ID. Replacing
> these usages allows that legacy fal
On 05.10.2015 21:47, Thierry Reding wrote:
> Use a PWM lookup table to provide the PWM to the pwm-backlight device.
> The driver has a legacy code path that is required only because boards
> still use the legacy method of requesting PWMs by global ID. Replacing
> these usages allows that legacy fal
On 05.10.2015 21:47, Thierry Reding wrote:
> Use a PWM lookup table to provide the PWM to the pwm-backlight device.
> The driver has a legacy code path that is required only because boards
> still use the legacy method of requesting PWMs by global ID. Replacing
> these usages allows that legacy fal
On 10/6/2015 1:56 AM, Marek Szyprowski wrote:
> DWC2 module on some platforms needs three additional hardware
> resources: phy controller, clock and power supply. All of them must be
> enabled/activated to properly initialize and operate. This was initially
> handled in s3c-hsotg driver, which has
Hi all,
Friendly ping. :)
Best regards,
- Yakir
On 09/22/2015 03:20 PM, Yakir Yang wrote:
Hi all,
The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller
share the same IP, so a lot of parts can be re-used. I split the common
code into bridge directory, then rk3288 an
32 matches
Mail list logo
