Hi,
On 09/16/2014 08:35 AM, Daniel Vetter wrote:
On Mon, Sep 15, 2014 at 12:52:17PM -0600, Daniel Drake wrote:
Pageflipping currently causes some inconsistencies that lead to
crashes. Just run an app that causes a CRTC pageflip in a raw X session
and check that it exits cleanly and can be
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system
On 2014년 09월 17일 15:35, Andrzej Hajda wrote:
Hi,
On 09/16/2014 08:35 AM, Daniel Vetter wrote:
On Mon, Sep 15, 2014 at 12:52:17PM -0600, Daniel Drake wrote:
Pageflipping currently causes some inconsistencies that lead to
crashes. Just run an app that causes a CRTC pageflip in a raw X session
Hi,
On 09/17/2014 03:49 PM, Inki Dae wrote:
On 2014년 09월 17일 15:35, Andrzej Hajda wrote:
Hi,
On 09/16/2014 08:35 AM, Daniel Vetter wrote:
On Mon, Sep 15, 2014 at 12:52:17PM -0600, Daniel Drake wrote:
Pageflipping currently causes some inconsistencies that lead to
crashes. Just run an app
Hello Doug,
On Wed, Sep 17, 2014 at 12:15 AM, Doug Anderson diand...@chromium.org wrote:
I think you can turn off CONFIG_COMMON_CLK_MAX77686 and then this
clock will be left at whatever the bootloader set it to, right? Then
there will be no auto-disabling by the CCF and the RTC will work.
Hi,
On Wed, Sep 17, 2014 at 8:52 AM, Jonghwa Lee jonghwa3@samsung.com wrote:
Add rtc alarm and tick irq to wakeup sources in exynos3250.
Signed-off-by: Jonghwa Lee jonghwa3@samsung.com
Acked-by : Chanwoo choi cw00.c...@samsung.com
---
arch/arm/mach-exynos/pm.c |9 -
1
Hi Laurent,
On Mon, Sep 15, 2014 at 11:07 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Ajay,
Thank you for the patch.
I think we're moving in the right direction, but we're not there yet.
On Saturday 26 July 2014 00:52:08 Ajay Kumar wrote:
This patch tries to seperate
Before the introduction of the component framework I would have said this is
the way to go. Now, I think bridges should register themselves as components,
and the DRM master driver should use the component framework to get a
reference to the bridges it needs.
Well, I have modified the bridge
Hi Ajay,
On Wednesday 17 September 2014 14:37:30 Ajay kumar wrote:
On Mon, Sep 15, 2014 at 11:07 PM, Laurent Pinchart wrote:
Hi Ajay,
Thank you for the patch.
I think we're moving in the right direction, but we're not there yet.
On Saturday 26 July 2014 00:52:08 Ajay Kumar
On Tue, Sep 16, 2014 at 6:14 PM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
[adding Laurent Pinchart to cc who had concerns with a previous
version of this patch-set]
Hello Ajay,
On Wed, Aug 27, 2014 at 4:29 PM, Ajay Kumar ajaykumar...@samsung.com wrote:
This series is based on
Hi Thierry,
On Wednesday 30 July 2014 11:40:54 Thierry Reding wrote:
On Wed, Jul 30, 2014 at 11:54:00AM +0530, Ajay kumar wrote:
On Tue, Jul 29, 2014 at 5:17 PM, Thierry Reding wrote:
On Tue, Jul 29, 2014 at 01:42:09PM +0200, Andreas Färber wrote:
Am 29.07.2014 13:36, schrieb Thierry
On Wed, Sep 17, 2014 at 12:01:50PM +0530, Pankaj Dubey wrote:
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface
Hi Laurent,
Please find the latest series here:
http://www.spinics.net/lists/dri-devel/msg66740.html
On Wed, Sep 17, 2014 at 3:23 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Thierry,
On Wednesday 30 July 2014 11:40:54 Thierry Reding wrote:
On Wed, Jul 30, 2014 at
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
Hi,
On Wednesday, September 17, 2014, Dong Aisheng Wrote,
+static struct syscon *of_syscon_register(struct device_node *np) {
+ struct syscon *syscon;
+ struct regmap *regmap;
+ void __iomem *base;
+
+ if (!of_device_is_compatible(np, syscon))
+ return
Cleaning up the phy getting sequence in ehci-exynos and ohci-exynos
drivers.
Hi Alan, Jingoo,
I have not imported the Acked-by and Reviewed-by from you guys, from V2 version
of this patch series, since this version is now rebased on the already available
commit in usb-next - usb:
On 2014년 09월 09일 22:16, Andrzej Hajda wrote:
This set of patches contains fixes of initialization and deinitialization
code of exynos_drm core and components.
It is based on exynos-drm-next branch.
Patchset has been tested on trats and universal_c210 platforms.
Applied all patches except
Hello Kukjin,
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as
its source clock but this breaks the s3c RTC on Exynos Chromebooks
because the
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as its
source clock. In the case of the Exynos5250 based Snow board, the Maxim
77686 32kHz AP
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses the RTC as its
source clock. In the case of the Peach Pit and Pi machines, the Maxim
77802 32kHz AP
On 27/08/14 17:39, Ajay Kumar wrote:
Add documentation for DT properties supported by ps8622/ps8625
eDP-LVDS converter.
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
---
.../devicetree/bindings/video/bridge/ps8622.txt| 20
1 file changed, 20 insertions(+)
On Wednesday, September 17, 2014 8:18 PM, Vivek Gautam wrote:
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
Doug Anderson wrote:
Vivek,
Hi,
On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
From: Naveen Krishna Chatradhi ch.nav...@samsung.com
MMC capability for HS200 is parsed in mmc/core/host.c as
dts string mmc-hs200-1_8v.
This patch corrects the dts
Hi Kukjin,
On Wed, Sep 17, 2014 at 5:39 PM, Kukjin Kim kg...@kernel.org wrote:
Doug Anderson wrote:
Vivek,
Hi,
On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
From: Naveen Krishna Chatradhi ch.nav...@samsung.com
MMC capability for HS200 is parsed in
On Wed, Sep 17, 2014 at 1:44 AM, Joonyoung Shim jy0922.s...@samsung.com wrote:
It's problem to add this from commit 25c8b5c3048cb6c98d402ca8d4735ccf910f727c.
My patch moves that drm_framebuffer_reference() call to the plane
function which is called from crtc_mode_set context (and also called
in
On Wed, Sep 17, 2014 at 5:43 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Hi Kukjin,
On Wed, Sep 17, 2014 at 5:39 PM, Kukjin Kim kg...@kernel.org wrote:
Doug Anderson wrote:
Vivek,
Hi,
On Tue, Sep 16, 2014 at 1:50 AM, Vivek Gautam gautam.vi...@samsung.com
wrote:
From: Naveen
On Wed, Sep 17, 2014 at 2:57 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Ajay,
On Wednesday 17 September 2014 14:37:30 Ajay kumar wrote:
On Mon, Sep 15, 2014 at 11:07 PM, Laurent Pinchart wrote:
Hi Ajay,
Thank you for the patch.
I think we're moving in the right
On Wed, Sep 17, 2014 at 2:19 PM, Daniel Drake dr...@endlessm.com wrote:
Chip specific drm driver internally doesn't have to care fb reference count
if
there is no special case. We should have switched to universal plane at that
time.
To me it seems like the chip-specific DRM drivers do need
This interface and relevant codes aren't used anymore.
Signed-off-by: Inki Dae inki@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_drv.c |3 ---
drivers/gpu/drm/exynos/exynos_drm_gem.c | 17 -
drivers/gpu/drm/exynos/exynos_drm_gem.h |4
Hi Tomi,
Thanks for your comments.
On Wed, Sep 17, 2014 at 5:22 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 27/08/14 17:39, Ajay Kumar wrote:
Add documentation for DT properties supported by ps8622/ps8625
eDP-LVDS converter.
Signed-off-by: Ajay Kumar ajaykumar...@samsung.com
---
On Wed, Sep 17, 2014 at 10:48:44PM +0900, Inki Dae wrote:
This patch set removes unnecessary DRM_EXYNOS_GEM_MAP_OFFSET interface
which isn't used anymore and also uses drm generic mmap interface
instead of a mmap interface specific to Exynos drm. So this patch set
removes a existing mmap
On Wednesday 17 September 2014, Pankaj Dubey wrote:
---
V2 of this patchset and related discussion can be found here [1].
Changes since v2:
- Added back platform device support from syscon, with one change that
syscon will not be probed for DT based platform.
- Added back
Javier,
On Wed, Sep 17, 2014 at 4:50 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that
Hi,
On Wed, Sep 17, 2014 at 4:50 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
controller that specifies the 32.768 kHz clock that uses
Am 17.09.2014 um 17:47 schrieb Doug Anderson:
Hi,
On Wed, Sep 17, 2014 at 4:50 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
commit 546b117fdf17 (rtc: s3c: add support for RTC of Exynos3250 SoC)
added an rtc_src DT property for the Samsung's S3C Real Time Clock
Hi,
On Friday 15 August 2014 06:10 PM, Peter Griffin wrote:
This patch removes the superflous .owner field for drivers which
use the module_platform_driver or platform_driver_register api,
as this is overriden in __platform_driver_register.
Signed-off-by: Peter Griffin
On 17/09/14 17:29, Ajay kumar wrote:
Hi Tomi,
Thanks for your comments.
On Wed, Sep 17, 2014 at 5:22 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 27/08/14 17:39, Ajay Kumar wrote:
Add documentation for DT properties supported by ps8622/ps8625
eDP-LVDS converter.
Signed-off-by:
On Thu, 11 Sep 2014, Javier Martinez Canillas wrote:
From: Andrew Bresticker abres...@chromium.org
When an EC command returns EC_RES_IN_PROGRESS, we need to query
the state of the EC until it indicates that it is no longer busy.
Do this in cros_ec_cmd_xfer() under the EC's mutex so that
On Thu, 11 Sep 2014, Javier Martinez Canillas wrote:
From: Todd Broch tbr...@chromium.org
If the EC device tree node has sub-nodes, try to instantiate them as
MFD sub-devices. We can configure the EC features provided by the board.
Signed-off-by: Todd Broch tbr...@chromium.org
On Wed, Sep 17, 2014 at 7:45 AM, Daniel Vetter dan...@ffwll.ch wrote:
I think fb refcounting in exynos is just plain busted. If you look at
other drivers the only place the refcount framebuffers or backing
storage objects is for pageflips to make sure the memory doesn't go
away while the hw is
Daniel,
On Wed, Sep 17, 2014 at 9:49 AM, Daniel Drake dr...@endlessm.com wrote:
On Tue, Sep 16, 2014 at 4:15 PM, Doug Anderson diand...@chromium.org wrote:
NOTE: I don't think that the builtin RTC is terribly important for any
exynos-based Chromebooks that I'm aware of. We rely on the RTC
On Tuesday 16 September 2014 10:32 AM, Vivek Gautam wrote:
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed to control power to the PHY.
With mfd-syscon and regmap interface available at our disposal,
it's wise to use that instead of using a 'reg' property for the
Hi Kishon,
On Wed, 17 Sep 2014, Kishon Vijay Abraham I wrote:
Hi,
On Friday 15 August 2014 06:10 PM, Peter Griffin wrote:
This patch removes the superflous .owner field for drivers which
use the module_platform_driver or platform_driver_register api,
as this is overriden in
Hi,
I'm using pwm-samsung on Exynos4412 for a variable-brightness LED.
When the LED is set to maximum brightness via the pwm-leds driver, we
arrive at pwm_samsung_config with duty_ns = period_ns, i.e. 100% duty
cycle.
This function does:
/* -1UL will give 100% duty. */
--tcmp;
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 failing boot
tests due to imprecise external aborts. This only appears to
Hi,
On 09/18/2014 01:41 AM, Daniel Drake wrote:
On Wed, Sep 17, 2014 at 7:45 AM, Daniel Vetter dan...@ffwll.ch wrote:
I think fb refcounting in exynos is just plain busted. If you look at
other drivers the only place the refcount framebuffers or backing
storage objects is for pageflips to
Hi Kishon,
On Wed, Sep 17, 2014 at 10:24 PM, Kishon Vijay Abraham I kis...@ti.com wrote:
On Tuesday 16 September 2014 10:32 AM, Vivek Gautam wrote:
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed to control power to the PHY.
With mfd-syscon and regmap interface
+CC: Dong Aisheng
Hi Arnd,
On Wednesday, September 17, 2014, Arnd Bergmann wrote,
V2 of this patchset and related discussion can be found here [1].
Changes since v2:
- Added back platform device support from syscon, with one change that
syscon will not be probed for DT based
On Wed, Sep 17, 2014 at 04:50:50PM +0530, Pankaj Dubey wrote:
Hi,
On Wednesday, September 17, 2014, Dong Aisheng Wrote,
+static struct syscon *of_syscon_register(struct device_node *np) {
+ struct syscon *syscon;
+ struct regmap *regmap;
+ void __iomem *base;
+
+ if
On Thu, Sep 18, 2014 at 08:59:32AM +0530, Pankaj Dubey wrote:
+CC: Dong Aisheng
Hi Arnd,
On Wednesday, September 17, 2014, Arnd Bergmann wrote,
V2 of this patchset and related discussion can be found here [1].
Changes since v2:
- Added back platform device support from syscon,
Hi Alan,
On Wed, Sep 17, 2014 at 8:27 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 17 Sep 2014, Vivek Gautam wrote:
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
We also defer the probe for our host in case we end up getting
EPROBE_DEFER
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.
We also defer the probe for our host in case we end up getting
EPROBE_DEFER
Hi,
On 09/17/2014 10:48 PM, Inki Dae wrote:
This patch removes DRM_EXYNOS_GEM_MMAP ictrl feature specific
to Exynos drm and instead uses drm generic mmap.
We had used the interface specific to Exynos drm to do mmap directly,
not to use demand paging which maps each page with physical memory
Thanks for review.
Below trivial things you pointed out will be fixed soon.
On 2014년 09월 18일 13:56, Joonyoung Shim wrote:
Hi,
On 09/17/2014 10:48 PM, Inki Dae wrote:
This patch removes DRM_EXYNOS_GEM_MMAP ictrl feature specific
to Exynos drm and instead uses drm generic mmap.
We had
This patch removes DRM_EXYNOS_GEM_MMAP ictrl feature specific
to Exynos drm and instead uses drm generic mmap.
We had used the interface specific to Exynos drm to do mmap directly,
not to use demand paging which maps each page with physical memory
at page fault handler. We don't need the specific
On Thursday 18 September 2014 12:34 AM, Peter Griffin wrote:
Hi Kishon,
On Wed, 17 Sep 2014, Kishon Vijay Abraham I wrote:
Hi,
On Friday 15 August 2014 06:10 PM, Peter Griffin wrote:
This patch removes the superflous .owner field for drivers which
use the module_platform_driver or
Hi Tomi,
On Wed, Sep 17, 2014 at 9:52 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On 17/09/14 17:29, Ajay kumar wrote:
Hi Tomi,
Thanks for your comments.
On Wed, Sep 17, 2014 at 5:22 PM, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
On 27/08/14 17:39, Ajay Kumar wrote:
Add
On Thursday 18 September 2014 08:55 AM, Vivek Gautam wrote:
Hi Kishon,
On Wed, Sep 17, 2014 at 10:24 PM, Kishon Vijay Abraham I kis...@ti.com
wrote:
On Tuesday 16 September 2014 10:32 AM, Vivek Gautam wrote:
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed
60 matches
Mail list logo
