Dear Sir
Did your website get hit by Google Penguin update on October 17th 2014? What
basically is Google Penguin Update? It is actually a code name for Google
algorithm which aims at decreasing your websites search engine rankings that
violate Googles guidelines by using black hat SEO
exynos_drm_display is used by internal Exynos DRM framework for
representing encoder:connector pair. As it should be mapped 1:1 to vidi
private context it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be
The patch replaces accesses to display-ctx pointer by container_of
construct. It will allow to remove ctx field in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff
exynos_drm_display is used by internal Exynos DRM framework for
representing encoder:connector pair. As it should be mapped 1:1 to dpi
private context it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be
The patch replaces accesses to display-ctx pointer by container_of
construct. The field is removed as well as dpi was the last user of it.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_dpi.c | 5 ++---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 -
2
Hi Inki,
This patchset embed all remaining exynos_drm framework objects into driver
private
context, thanks to this global variables can be removed and the code can be
simplified.
It continues refactoring started by dsi related patchset [1].
I have tested it on trats and universal boards with
The patch replaces accesses to manager-ctx pointer by container_of
construct. As fimd was the last user of ctx the patch removes
this field as well.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 -
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 40
The patch replaces accesses to display-ctx pointer by container_of
construct. It will allow to remove ctx field in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_vidi.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff
The patch replaces accesses to display-ctx pointer by container_of
construct. It will allow to remove ctx field in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_dp_core.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
The patch replaces accesses to manager-ctx pointer by container_of
construct. It will allow to remove ctx field in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_mixer.c | 30 +-
1 file changed, 17 insertions(+), 13
exynos_drm_display is used by internal Exynos DRM framework for
representing encoder:connector pair. As it should be mapped 1:1 to dp
private context it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be
exynos_drm_manager is used by internal Exynos DRM framework for
representing crtc. As it should be mapped 1:1 to fimd private context
it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be possible to handle
exynos_drm_display is used by internal Exynos DRM framework for
representing encoder:connector pair. As it should be mapped 1:1 to hdmi
private context it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be
exynos_drm_manager is used by internal Exynos DRM framework for
representing crtc. As it should be mapped 1:1 to vidi private context
it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be possible to handle
exynos_drm_manager is used by internal Exynos DRM framework for
representing crtc. As it should be mapped 1:1 to fimd private context
it seems more reasonable to embed it directly in that context.
As a result further code simplification will be possible.
Moreover it will be possible to handle
The patch replaces accesses to manager-ctx pointer by container_of
construct. It will allow to remove ctx field in the future.
Signed-off-by: Andrzej Hajda a.ha...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_vidi.c | 26 +++---
1 file changed, 15 insertions(+), 11
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. DISCONNINT interrupt cannot be used for this
purpose, because it is asserted only in host mode.
To avoid reporting disconnect event
Adds QUIRK_SUPPORTS_192KHZ to allow 192kHz rate
to be selected for hardware that supports it.
Signed-off-by: Richard Fitzgerald r...@opensource.wolfsonmicro.com
---
.../devicetree/bindings/sound/samsung-i2s.txt |2 ++
include/linux/platform_data/asoc-s3c.h |1 +
This patch removes restart hook from machine_desc of Exynos, and moves
respective code into restart_notifiers.
Exynos5440 handles reboot via clock register so let's register a
restart_handler in Exynos5440 clock driver.
For rest Exynos SoC, reboot is handled via PMU SWRESET register so
let's
Let's register restart handler for Exynos5440 from it's clock driver
for reboot functionality. So that we can cleanup restart hooks from
machine specific file.
CC: Sylwester Nawrocki s.nawro...@samsung.com
CC: Tomasz Figa tomasz.f...@gmail.com
Signed-off-by: Pankaj Dubey pankaj.du...@samsung.com
Let's register restart handler from PMU driver for reboot
functionality. So that we can remove restart hooks from
machine specific file, and thus moving ahead when PMU moved
to driver folder, this functionality can be reused for ARM64
based Exynos SoC's.
Signed-off-by: Pankaj Dubey
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable only from secure mode.
First four patches extend
From: Tomasz Figa t.f...@samsung.com
Firmware on certain boards (e.g. ODROID-U3) can leave incorrect L2C prefetch
settings configured in registers leading to crashes if L2C is enabled
without overriding them. This patch introduces bindings to enable
prefetch settings to be specified from DT and
From: Tomasz Figa t.f...@samsung.com
This patch adds device tree nodes for L2 cache controller present on
Exynos4 SoCs.
Signed-off-by: Tomasz Figa t.f...@samsung.com
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Acked-by: Arnd Bergmann a...@arndb.de
Acked-by: Kukjin Kim
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers are writable only from secure mode.
First four patches extend
From: Tomasz Figa t.f...@samsung.com
On Exynos SoCs it is necessary to resume operation of L2C early in
assembly code, because otherwise certain systems will crash. This patch
adds necessary code to non-secure resume handler.
Signed-off-by: Tomasz Figa t.f...@samsung.com
[rewrote the code
From: Tomasz Figa t.f...@samsung.com
Certain platforms (i.e. Exynos) might need to set .write_sec callback
from firmware initialization which is happenning in .init_early callback
of machine descriptor. However current code will overwrite the pointer
with whatever is present in machine
From: Tomasz Figa t.f...@samsung.com
Because certain secure hypervisor do not allow writes to individual L2C
registers, but rather expect set of parameters to be passed as argument
to secure monitor calls, there is a need to provide an interface for the
L2C driver to ask the firmware to configure
From: Tomasz Figa t.f...@samsung.com
Exynos4 SoCs equipped with an L2C-310 cache controller and running under
secure firmware require certain registers of aforementioned IP to be
accessed only from secure mode. This means that SMC calls are required
for certain register writes. To handle this, an
From: Tomasz Figa t.f...@samsung.com
Certain implementations of secure hypervisors (namely the one found on
Samsung Exynos-based boards) do not provide access to individual L2C
registers. This makes the .write_sec()-based interface insufficient and
provoking ugly hacks.
This patch is first step
Today's 3.19/for-next regressed on usb (and display panel too) on my samsung
chromebook2 peach pi.
Blindly typing i was able to login and get a dmesg, and this is the relevant
part:
...
[0.195049] exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU
regmap
[0.195304]
On 14/11/14 07:54, Kukjin Kim wrote:
Use kernel.org account instead of samsung.com and cleanup for Samsung
s3c, s5p and exynos SoCs.
Cc: Ben Dooks ben.do...@codethink.co.uk
I do wish these would be sent to the mail address I use for
Linux related issues. I only want to see work related Linux
This function is valid only the SoC has SHADOWCON register
and it should be used together with fimd_enable_video_output()
to match the ENWIN_F bit in WINCON# and C#_EN_F bit in SHADOWCON.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin
Hi,
This series modifies LCD I80 interface display for Exynos DRM driver
to make it similar with Video(RGB) interface.
Some patches in v1 are applied already and these are modified as Inki's
comments.
And Joonyoung's patches are also included for merge convenience.
This is based on
This bit is used for video output and logic signal control.
So it is better for readability.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 27
The C#_EN_F in SHADOWCON register is updated per frame.
So it should be protected by fimd_shadow_protect_win().
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Joonyoung Shim jy0922.s...@samsung.com
It's better to be checking whether triggerring in fimd_trigger function.
Also it will return if in triggerring on fimd_te_handler, then it can't
execute remain codes.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
For the I80 interface, the video interrupt pending register(VIDINTCON1)
should be handled in fimd_irq_handler() and the video interrupt control
register(VIDINTCON0) should be handled in fimd_enable_vblank() and
fimd_disable_vblank() like RGB interface.
So this patch moves each set / unset routines
There is a case like set config which requires triggering
but vblank is not enabled yet.
So triggering unset routine is required to exit from
triggering mode.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park kyungmin.p...@samsung.com
The drm_helper_hpd_irq_event() does dpms control and
the panel is initialized and displayed on by it.
So the exynos_dsi_te_irq_handler() should be registered
beforehand.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.com
Acked-by: Kyungmin Park
From: Joonyoung Shim jy0922.s...@samsung.com
The drm_handle_vblank should be called whenever be vsync, te interrupt
means vsync on i80 interface.
Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 10 ++
1 file changed, 6 insertions(+),
The exynos_dsi_te_irq_handler() works only dsi(DPMS) is on.
So it is enough to enable and disable TE GPIO IRQ in
exynos_dsi_enable(disable)_irq() like DSI IRQ.
Signed-off-by: YoungJun Cho yj44@samsung.com
Acked-by: Inki Dae inki@samsung.coma
Acked-by: Kyungmin Park
On Mon, Nov 17, 2014 at 07:26:29PM +0530, Krishna Mohan Dani wrote:
Fixes the following compilation warning:
Warning: 'rt5631_i2c_dt_ids' defined but not used - when DT is not used.
Signed-off-by: Claude Youn claude.y...@gmail.com
Signed-off-by: Krishna Mohan Dani krishna...@samsung.com
On Mon, Nov 17, 2014 at 10:57:54AM +, Richard Fitzgerald wrote:
Adds QUIRK_SUPPORTS_192KHZ to allow 192kHz rate
to be selected for hardware that supports it.
+- samsung,supports-192khz: specify this (without a value) if you want to
allow
+192000 sample rate over the I2S link.
Two
The amba bus, amba drivers and a vast amount of platform drivers which
enables runtime PM, don't invoke a pm_runtime_get_sync() while probing
their devices.
Instead, once they have turned on their PM resourses during -probe()
and are ready to handle I/O, these invokes pm_runtime_set_active() to
On Mon, Nov 17, 2014 at 04:19:10PM +0100, Ulf Hansson wrote:
The amba bus, amba drivers and a vast amount of platform drivers which
enables runtime PM, don't invoke a pm_runtime_get_sync() while probing
their devices.
Instead, once they have turned on their PM resourses during -probe()
and
On Mon, Nov 17, 2014 at 07:26:29PM +0530, Krishna Mohan Dani wrote:
Fixes the following compilation warning:
Warning: 'rt5631_i2c_dt_ids' defined but not used - when DT is not used.
Signed-off-by: Claude Youn claude.y...@gmail.com
Signed-off-by: Krishna Mohan Dani krishna...@samsung.com
---
FYI...
Various new exynos5 boot failures starting next-20141117. Looking in
the boot logs, the boot stops during DRM initialization.
Note that the boot failures are only on exynos_defconfig, and not
multi_v7_defconfig.
Excerpt from boot report below, or recent exynos boots can also be
explored
Hello.
On 11/17/2014 9:36 AM, 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
On Mon, Nov 17, 2014 at 04:51:13PM +0530, Pankaj Dubey wrote:
Let's register restart handler from PMU driver for reboot
functionality. So that we can remove restart hooks from
machine specific file, and thus moving ahead when PMU moved
to driver folder, this functionality can be reused for
On Mon, Nov 17, 2014 at 04:51:12PM +0530, Pankaj Dubey wrote:
Let's register restart handler for Exynos5440 from it's clock driver
for reboot functionality. So that we can cleanup restart hooks from
machine specific file.
CC: Sylwester Nawrocki s.nawro...@samsung.com
CC: Tomasz Figa
On 17.11.2014 16:57, Kevin Hilman wrote:
FYI...
Various new exynos5 boot failures starting next-20141117. Looking in
the boot logs, the boot stops during DRM initialization.
Note that the boot failures are only on exynos_defconfig, and not
multi_v7_defconfig.
Cc: +Inki Dae, +dri-devel
On Mon, Nov 17, 2014 at 06:54:44PM +0200, Grygorii Strashko wrote:
I'd be very appreciated if you would be able to clarify one point to me as
I'm not familiar with amba hw?
I've found at least 2 AMBA drivers where secondary clock is used
to enable/disable device in addition to apb_pclk:
-
Exynos Snow and Peach Pit/Pi Chromebooks have a serial dataflash that
is accessed through SPI. This series add spidev nodes in the Device
Tree source files so the flash can be accessed from user-space.
The series is composed of the following patches taken from the ChromeOS tree:
Doug Anderson
Some Exynos boards have SPI devices such as flash memories that can be
accessed from user-space. Enable support for the SPI usermode interface.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/configs/exynos_defconfig | 1 +
1 file changed, 1 insertion(+)
From: Doug Anderson diand...@chromium.org
Exynos5250 Snow machine has a SPI flash memory that is used to store
firmware data and different system parameters.
Add a spidev node so the flash chip can be accessed by user-space tools.
Signed-off-by: Doug Anderson diand...@chromium.org
Reviewed-by:
From: Simon Glass s...@chromium.org
Peach Pit and Pi machines have a SPI flash memory that is used to store
firmware data and different system parameters.
Add a spidev node so the flash chip can be accessed by user-space tools.
Signed-off-by: Simon Glass s...@chromium.org
Reviewed-by: Doug
Ulf Hansson ulf.hans...@linaro.org writes:
The amba bus, amba drivers and a vast amount of platform drivers which
enables runtime PM, don't invoke a pm_runtime_get_sync() while probing
their devices.
Instead, once they have turned on their PM resourses during -probe()
and are ready to
On Mon, Nov 17, 2014 at 10:14:51AM +0530, Abhilash Kesavan wrote:
From: Pankaj Dubey pankaj.du...@samsung.com
Exynos7 has a similar serial controller to that present in older Samsung
SoCs. To re-use the existing serial driver on Exynos7 we need to have
SERIAL_SAMSUNG_UARTS_4 and
On Mon, 17 Nov 2014, Kevin Hilman wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
The amba bus, amba drivers and a vast amount of platform drivers which
enables runtime PM, don't invoke a pm_runtime_get_sync() while probing
their devices.
Instead, once they have turned on their PM
On Mon, Nov 17, 2014 at 11:06 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 17 Nov 2014, Kevin Hilman wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
The amba bus, amba drivers and a vast amount of platform drivers which
enables runtime PM, don't invoke a
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
For devices that aren't part of a power domain, things are simpler.
The bus does _get_noresume() to make sure the device won't be runtime
suspended while the probe routine is running. It doesn't do
_get_sync(), because that would end up calling
On Mon, Nov 17, 2014 at 02:54:53PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
For devices that aren't part of a power domain, things are simpler.
The bus does _get_noresume() to make sure the device won't be runtime
suspended while the probe routine is
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 02:54:53PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
For devices that aren't part of a power domain, things are simpler.
The bus does _get_noresume() to make sure the device won't be
On Mon, Nov 17, 2014 at 03:49:14PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 02:54:53PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
For devices that aren't part of a power domain, things are simpler.
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
When the runtime PM core invokes a power domain's callback routine,
what does the domain's routine usually do? Does it go ahead and invoke
the driver's callback? Or does it try to invoke the subsystem's
callback?
Obviously this depends on
On Mon, Nov 17, 2014 at 04:44:56PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
When the runtime PM core invokes a power domain's callback routine,
what does the domain's routine usually do? Does it go ahead and invoke
the driver's callback? Or does it try to
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
Except buses
usually call pm_generic_runtime_resume() which ends up fetching driver's
callbacks. Maybe pm_generic_runtime_*() need be a bit smarter?
No, the bus subsystem needs to be smarter. It shouldn't call
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
Except buses
usually call pm_generic_runtime_resume() which ends up fetching driver's
callbacks. Maybe pm_generic_runtime_*() need be a bit smarter?
No, the bus subsystem
Kevin Hilman khil...@kernel.org writes:
FYI...
Various new exynos5 boot failures starting next-20141117. Looking in
the boot logs, the boot stops during DRM initialization.
Note that the boot failures are only on exynos_defconfig, and not
multi_v7_defconfig.
As might have been expected
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
Except buses
usually call pm_generic_runtime_resume() which ends up fetching
driver's
callbacks. Maybe
Hello Kevin,
On 11/17/2014 11:24 PM, Kevin Hilman wrote:
As might have been expected, reverting the change that enables the
DRM/display options in exynos_defconfig fixes the problem.
Kevin
I'm sorry for causing a boot failure but when I first posted that patch,
the Exynos DRM driver was
On Tue, Nov 18, 2014 at 12:28:26AM +0100, Rafael J. Wysocki wrote:
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
Except buses
usually call
On Monday, November 17, 2014 03:26:04 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:28:26AM +0100, Rafael J. Wysocki wrote:
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry
On Tuesday, November 18, 2014 01:26:38 AM Rafael J. Wysocki wrote:
On Monday, November 17, 2014 03:26:04 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:28:26AM +0100, Rafael J. Wysocki wrote:
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at
Hello all,
On 2014년 11월 18일 08:25, Javier Martinez Canillas wrote:
Hello Kevin,
On 11/17/2014 11:24 PM, Kevin Hilman wrote:
As might have been expected, reverting the change that enables the
DRM/display options in exynos_defconfig fixes the problem.
Kevin
I'm sorry for causing a boot
This patch fixes a infinite loop issue incurred when
it doesn't have a pair of crtc and connector drivers,
which was reported by Kevin Hilman like below,
http://www.spinics.net/lists/linux-samsung-soc/msg39050.html
cdev-conn_dev could be NULL by exynos_drm_component_del call in case
that
Javier Martinez Canillas javier.marti...@collabora.co.uk writes:
Hello Kevin,
On 11/17/2014 11:24 PM, Kevin Hilman wrote:
As might have been expected, reverting the change that enables the
DRM/display options in exynos_defconfig fixes the problem.
Kevin
I'm sorry for causing a boot
On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar ajaykumar...@samsung.com wrote:
This series is based on master branch of Linus tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Changes since V2:
-- Address comments from Jingoo Han for ps8622 driver
--
Dear Kukjin,
Could you please review or pick this patchset?
Best Regards,
Chanwoo Choi
On 10/08/2014 11:11 AM, YoungJun Cho wrote:
From: Youngjun Cho yj44@samsung.com
This patch adds new board dts file to support Samsung Monk board which is
based on Exynos3250 SoC and has different H/W
Hello,
On 2014-11-14 15:51, Arnd Bergmann wrote:
On Friday 14 November 2014 15:11:58 Marek Szyprowski wrote:
I assume that after all comments from previous versions, no more changes
are needed
to this patchset and I would really like to have it queued to v3.19.
Arnd, Olof: could you take this
On Tue, 2014-11-18 at 12:20 +0900, Inki Dae wrote:
This patch makes the deferred probe is tried up to 3 times in maximum.
However, this is considered only for Exynos drm so I think other SoC
drivers could also produce same issue. Therefore, the best way to resolve
this issue, infinite loop
82 matches
Mail list logo
