Hello,
On 2014-10-25 03:23, Paul Zimmerman wrote:
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Monday, October 20, 2014 3:46 AM
This patch adds a call to s3c_hsotg_disconnect() from 'end session'
interrupt (GOTGINT_SES_END_DET) to correctly notify gadget subsystem
about
On pią, 2014-10-31 at 12:31 +0900, Alexandre Courbot wrote:
On Fri, Oct 31, 2014 at 12:03 AM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
On czw, 2014-10-30 at 22:56 +0900, Alexandre Courbot wrote:
Hi, and thanks for bringing this issue to us!
On Wed, Oct 29, 2014 at 7:49 PM,
This patch adds a call to s3c_hsotg_disconnect() from 'end session'
interrupt (GOTGINT_SES_END_DET) to correctly notify gadget subsystem
about unplugged usb cable. 'disconnected' interrupt (DISCONNINT) might
look a bit more suitable for this event, but it is asserted only in
host mode, so in
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
Changes in v3:
-Rework the entire intermediate step which was suggested in v2.
That means solving the race condition, but also cope with PM domains
that are
On 30 October 2014 21:47, Kevin Hilman khil...@kernel.org wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
To sucessfully probe some devices their corresponding PM domains may
need to be powered.
Isn't that what pm_runtime_get*() is supposed to be doing? Why isn't
that working?
Let stay
On 31 October 2014 01:07, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
On Thu, Oct 30, 2014 at 01:47:27PM -0700, Kevin Hilman wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
To sucessfully probe some devices their corresponding PM domains may
need to be powered.
Isn't that what
On 28/10/14 05:09, Kukjin Kim wrote:
Sylwester Nawrocki wrote:
On 27/10/14 02:11, Chanwoo Choi wrote:
Chanwoo Choi (2):
clk: samsung: exynos4415: Add clocks using common clock framework
clk: samsung: Document binding for Exynos4415 clock controller
[...]
Can you please provide a topic
Hello,
On 2014-10-27 08:18, Marek Szyprowski wrote:
On 2014-10-25 03:16, Paul Zimmerman wrote:
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Monday, October 20, 2014 3:46 AM
Suspend/resume code assumed that the gadget was always enabled and
connected to usb bus. This means
This patch adds mutex, which protects initialization and
deinitialization procedures against suspend/resume methods.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
drivers/usb/dwc2/core.h | 1 +
drivers/usb/dwc2/gadget.c | 20
2 files changed, 21
Suspend/resume code assumed that the gadget was always enabled and
connected to usb bus. This means that the actual state of the gadget
(soft-enabled/disabled or connected/disconnected) was not correctly
preserved on suspend/resume cycle. This patch fixes this issue.
Signed-off-by: Marek
On Fri, Oct 31, 2014 at 08:51:38AM +0100, Krzysztof Kozlowski wrote:
However new DT style parsing (regulator_of_get_init_data()) does the
basic parsing stuff and this removes a lot of code from driver. The
driver no longer parses all regulaotrs but the regulator core does it.
Unfortunately
On pią, 2014-10-31 at 10:32 +, Mark Brown wrote:
On Fri, Oct 31, 2014 at 08:51:38AM +0100, Krzysztof Kozlowski wrote:
However new DT style parsing (regulator_of_get_init_data()) does the
basic parsing stuff and this removes a lot of code from driver. The
driver no longer parses all
On Fri, Oct 31, 2014 at 12:45:47PM +0100, Krzysztof Kozlowski wrote:
Then I'll add it.
Mark, what device should be assigned to config.dev during registration
of regulators? The regulator driver's device or its parent (MFD main
driver)?
Various drivers do this differently.
Normally the
On Thu, Oct 30, 2014 at 12:20:40PM +0100, Krzysztof Kozlowski wrote:
Add of_compatible fields for max77686 and max77802 regulator drivers.
The driver's node should be the same as voltage-regulators node. This
simplifies parsing of regulators init data from DTS.
No, this is broken. You're
On Wed, Oct 29, 2014 at 12:14:52PM +0100, Krzysztof Kozlowski wrote:
Some LDOs of Maxim 77686 PMIC support disabling during system suspend
(LDO{2,6,7,8,10,11,12,14,15,16}). This was already implemented as part
of set_suspend_mode function. In that case the mode was one of:
Applied, thanks.
On pią, 2014-10-31 at 12:23 +, Mark Brown wrote:
On Thu, Oct 30, 2014 at 12:20:40PM +0100, Krzysztof Kozlowski wrote:
Add of_compatible fields for max77686 and max77802 regulator drivers.
The driver's node should be the same as voltage-regulators node. This
simplifies parsing of
This series is tested with V3 of Heikki's patches for simpliefied phy lookup
table:
[PATCHv3 0/6] phy: simplified phy lookup [1] on 'usb-next' branch.
V4 of this series is giving some issue, which i have already pointed out in the
patch: [PATCHv4 2/6] phy: improved lookup method
Changes since
Adding phy calibration sequence for USB 3.0 DRD PHY present on
Exynos5420/5800 systems.
This calibration facilitates setting certain PHY parameters viz.
the Loss-of-Signal (LOS) Detector Threshold Level, as well as
Tx-Vboost-Level for Super-Speed operations.
Additionally we also set proper time to
The host controller by itself may sometimes need to handle PHY
and re-initialize it to re-configure some of the PHY parameters
to get full support out of the PHY controller.
Therefore, facilitate getting the two possible PHYs, viz.
USB 2.0 type (UTMI+) and USB 3.0 type (PIPE3), and initialize
Assign proper FIMC-IS UART gate clock in the device DT node and not
use the SRC_MASK gate. This fixes regression introduced in commit
a37c82a3b3c0910019abfd22a97be1f (clk: samsung: exynos4: Remove
SRC_MASK_ISP gates).
Without this change exynos4 fimc-is driver fails to probe with an
error log:
[
Hello.
On 10/31/2014 4:26 PM, Vivek Gautam wrote:
The host controller by itself may sometimes need to handle PHY
and re-initialize it to re-configure some of the PHY parameters
to get full support out of the PHY controller.
Therefore, facilitate getting the two possible PHYs, viz.
USB 2.0 type
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Re-declare struct is not a good practice, let's use the original
drm declarations.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 4 +---
1 file changed, 1 insertion(+), 3
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Re-declare struct is not a good practice, let's use the original
drm and exynos declarations.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_crtc.h | 5 +
1 file changed, 1
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Save a few bytes by compiling them all in the same byte.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
They are not implemented anywhere, so wipe them out.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 11 ---
1 file changed, 11 deletions(-)
diff --git
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
It is not even used in this header anymore.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_iommu.h | 1 -
1 file changed, 1 deletion(-)
diff --git
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
Description of the @create_connector callback was missing,
and the @manager was no longer needed.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 3 +--
1 file changed, 1
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The struct is defined in the same file, declare it here is just
unnecessary.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_encoder.h | 2 --
1 file changed, 2 deletions(-)
diff --git
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
The struct is defined in the same file, declare it here is just
unnecessary
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 -
1 file changed, 1 deletion(-)
diff --git
From: Gustavo Padovan gustavo.pado...@collabora.co.uk
This is a leftover, all code using this macro have been removed/
changed already.
Signed-off-by: Gustavo Padovan gustavo.pado...@collabora.co.uk
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 14 --
1 file changed, 14 deletions(-)
On Wed, Oct 29, 2014 at 10:14:37AM +0100, Thierry Reding wrote:
On Wed, Oct 29, 2014 at 09:57:02AM +0100, Daniel Vetter wrote:
That makes the entire thing a bit non-trivial, which is why I think it
would be better as some generic helper. Which then gets embedded or
instantiated for specific
On Thu, Oct 30, 2014 at 10:09:28AM +, Russell King - ARM Linux wrote:
On Thu, Oct 30, 2014 at 11:01:02AM +0100, Andrzej Hajda wrote:
On 10/29/2014 10:14 AM, Thierry Reding wrote:
On Wed, Oct 29, 2014 at 09:57:02AM +0100, Daniel Vetter wrote:
I think we nee try_get_module for the code
On Wed, Oct 29, 2014 at 10:16:49AM +0100, Thierry Reding wrote:
On Wed, Oct 29, 2014 at 08:51:27AM +0100, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 03:29:47PM +0100, Thierry Reding wrote:
On Mon, Oct 27, 2014 at 11:20:31PM +0100, Daniel Vetter wrote:
On Mon, Oct 27, 2014 at 8:58 PM,
On Wed, Oct 29, 2014 at 10:09:04AM +0100, Andrzej Hajda wrote:
On 10/29/2014 08:58 AM, Daniel Vetter wrote:
On Tue, Oct 28, 2014 at 04:05:34PM +0100, Thierry Reding wrote:
On Tue, Oct 28, 2014 at 08:16:44PM +0530, Ajay kumar wrote:
On Tue, Oct 28, 2014 at 8:11 PM, Thierry Reding
Hi Mike,
I've collected Exynos clk patches in this pull request, as Tomasz has
been busy recently.
This includes addition of clock controller drivers for Exynos4415 and
Exynos7 SoCs and related refactoring of the Samsung common clk API.
As I mentioned in my other e-mail, it might be sensible
On Wed, Sep 17, 2014 at 5:39 PM, Kevin Hilman khil...@kernel.org wrote:
Thomas Abraham ta.oma...@gmail.com writes:
On Thu, Sep 11, 2014 at 12:16 AM, Kevin Hilman khil...@kernel.org wrote:
Tyler Baker tyler.ba...@linaro.org writes:
Exynos5420-based Arndale octa boards have recently started
On Fri, Oct 31, 2014 at 02:07:54PM +0100, Krzysztof Kozlowski wrote:
On pią, 2014-10-31 at 12:23 +, Mark Brown wrote:
I'm getting very frustrated with what's going on with these drivers,
there seem to be a lot of rather large sets of patches spawning lots of
discussion but also
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Friday, October 31, 2014 1:04 AM
To: linux-...@vger.kernel.org; linux-samsung-soc@vger.kernel.org
Cc: Marek Szyprowski; Kyungmin Park; Robert Baldyga; Paul Zimmerman;
Krzysztof Kozlowski; Felipe Balbi
Subject: [PATCH v3] usb:
From: Marek Szyprowski [mailto:m.szyprow...@samsung.com]
Sent: Friday, October 31, 2014 3:13 AM
This patch adds mutex, which protects initialization and
deinitialization procedures against suspend/resume methods.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
From: Kevin Hilman khil...@linaro.org
The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
during boot testing, causing various userspace startup failures.
Disable until it has gotten more testing.
Cc: Kukjin Kim kgene@samsung.com,
Cc: Javier Martinez Canillas
Hello Kukjin,
On Mon, Aug 25, 2014 at 10:45 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
Many Exynos devices have a display panel. Most of them just have
a simple panel while others have more complex configurations that
requires an embedded DisplayPort (eDP) to LVDS
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
Changes in v3:
-Rework the entire intermediate step which was suggested in v2.
That means solving the race
On Friday, October 31, 2014 10:23:00 AM Ulf Hansson wrote:
On 31 October 2014 01:07, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
On Thu, Oct 30, 2014 at 01:47:27PM -0700, Kevin Hilman wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
To sucessfully probe some devices their
On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
[cut]
1)
It's bad practice to use pm_runtime_get_sync() in the -probe() path,
Honestly, I'm
On Saturday, November 01, 2014 02:08:57 AM Rafael J. Wysocki wrote:
On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
[cut]
1)
It's bad
On Fri, Oct 31, 2014 at 4:51 PM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
On pią, 2014-10-31 at 12:31 +0900, Alexandre Courbot wrote:
On Fri, Oct 31, 2014 at 12:03 AM, Krzysztof Kozlowski
k.kozlow...@samsung.com wrote:
On czw, 2014-10-30 at 22:56 +0900, Alexandre Courbot wrote:
46 matches
Mail list logo
