On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote:
2014-08-06 16:43 GMT+09:00 Thierry Reding thierry.red...@gmail.com:
On Wed, Aug 06, 2014 at 04:11:54PM +0900, Inki Dae wrote:
On 2014년 08월 05일 20:12, Thierry Reding wrote:
[...]
I think that low power mode is more often used for
Since used the mmc_of_parse(), didn't parse the sub-node.
So we can remove the sub-node, because almost SoC used the only one card per a
host.
And supports-highspeed can be replaced with cap-mmc/sd-highspeed property.
Changelog V10:
- Rebased for next.
- Remove conflict
Changelog
Slot quirks disable-wp is deprecated.
Instead, use the host quirk disable-wp.
(Because the slot-node is removed in dt-file.)
Signed-off-by: Jaehoon Chung jh80.ch...@samsung.com
Tested-by: Sachin Kamat sachin.ka...@samsung.com
Acked-by: Seungwon Jeon tgih@samsung.com
Reviewed-by: Doug Anderson
Almost all SoCs use one slot per host controller.
(Even if controller can support the multiple slot, Recommend to use one slot
per host controller.)
Don't use the slot-node and deprecate the supports-highspeed property.
Instead, use the cap-mmc/sd-highspeed.
Signed-off-by: Jaehoon Chung
dw-mmc controller can support multiple slots.
But, there are no use-cases anywhere. So we don't need to support the
slot-node for dw-mmc controller.
And supports-highspeed property in dw-mmc is deprecated.
supports-highspeed property can be replaced with cap-sd/mmc-highspeed.
Signed-off-by:
dw-mmc controller can support multiple slots.
But, there are no use-cases anywhere. So we don't need to support the
slot-node for dw-mmc controller.
And supports-highspeed property in dw-mmc is deprecated.
supports-highspeed property can be replaced with cap-sd/mmc-highspeed.
Signed-off-by:
dw-mmc controller can support multiple slots.
But, there are no use-cases anywhere. So we don't need to support the
slot-node for dw-mmc controller.
And supports-highspeed property in dw-mmc is deprecated.
supports-highspeed property can be replaced with cap-sd/mmc-highspeed.
Signed-off-by:
The Atmel maXTouch driver assumed that the IRQ type flags will
always be passed using platform data but this is not true when
booting using Device Trees. In these setups the interrupt type
was ignored by the driver when requesting an IRQ.
This means that it will fail if a machine specified other
Hello Dmitry,
On 08/07/2014 08:09 AM, Dmitry Torokhov wrote:
irq_of_parse_and_map() already sets up IRQ trigger type based on DT
data, by calling irq_create_of_mapping() which in turn calls
irq_set_irq_type().
Right but somehow when the IRQ is actually requested the type is
On 2014년 08월 07일 15:58, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote:
2014-08-06 16:43 GMT+09:00 Thierry Reding thierry.red...@gmail.com:
On Wed, Aug 06, 2014 at 04:11:54PM +0900, Inki Dae wrote:
On 2014년 08월 05일 20:12, Thierry Reding wrote:
[...]
I think
Hello,
On 08/04/2014 05:42 PM, Doug Anderson wrote:
For the touchpad it seems DT support has landed in the input tree as
atmel,maxtouch. Backporting just that patch does not make it work
though. (Tried the rejected pinctrl approach to be on the safe side.)
Hi,
I remembered that this patch was pushed at Ulf's tree.
Since dw_mci_idmac_reset() is located into #if CONFIG_MMC_DW_IDMAC,
it occurred the compiler error.
And it seems that didn't need to use IS_ENABLED() at there.
Acked-by: Jaehoon Chung jh80.ch...@samsung.com
Best Regards,
Jaehoon Chung
On Thu, Aug 07, 2014 at 04:51:18PM +0900, Inki Dae wrote:
On 2014년 08월 07일 15:58, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote:
2014-08-06 16:43 GMT+09:00 Thierry Reding thierry.red...@gmail.com:
[...]
As far as I can tell non-continuous mode simply means
On 2014년 08월 07일 18:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 04:51:18PM +0900, Inki Dae wrote:
On 2014년 08월 07일 15:58, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote:
2014-08-06 16:43 GMT+09:00 Thierry Reding thierry.red...@gmail.com:
[...]
As far as
On Thu, Aug 07, 2014 at 07:49:03PM +0900, Inki Dae wrote:
On 2014년 08월 07일 18:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 04:51:18PM +0900, Inki Dae wrote:
On 2014년 08월 07일 15:58, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 02:09:19AM +0900, Inki Dae wrote:
2014-08-06 16:43
Refactoring the pm.c to avoid using soc_is_exynos checks,
instead use the DT based lookup.
While at it, consolidate the common code across SoCs
and create a static helper functions.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
arch/arm/mach-exynos/pm.c | 168
Move the Disabling of JPEG USE_RETENTION for exynos5250 to pmu.c to make way for
refactoring of pm.c and to create common functions across exynos4 and
exynos5250.
Signed-off-by: Vikas Sajjan vikas.saj...@samsung.com
---
arch/arm/mach-exynos/pm.c |7 +--
arch/arm/mach-exynos/pmu.c |6
On 2014년 08월 07일 20:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 07:49:03PM +0900, Inki Dae wrote:
On 2014년 08월 07일 18:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 04:51:18PM +0900, Inki Dae wrote:
On 2014년 08월 07일 15:58, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 02:09:19AM
On Thu, Aug 07, 2014 at 10:05:44PM +0900, Inki Dae wrote:
On 2014년 08월 07일 20:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 07:49:03PM +0900, Inki Dae wrote:
On 2014년 08월 07일 18:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 04:51:18PM +0900, Inki Dae wrote:
On 2014년 08월 07일 15:58,
On Thu, Aug 07, 2014 at 10:39:29PM +0900, Inki Dae wrote:
On 2014년 08월 07일 22:17, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 10:05:44PM +0900, Inki Dae wrote:
On 2014년 08월 07일 20:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 07:49:03PM +0900, Inki Dae wrote:
On 2014년 08월 07일 18:09,
Runtime Power Management handling for the sdhci_add_host() failure
case in sdhci_s3c_probe() should match the code in sdhci_s3c_remove()
(which uses pm_runtime_disable() call which matches the earlier
pm_runtime_enable() one). Fix it.
This patch fixes BUG: spinlock bad magic on CPU#0,
On Thu, Aug 07, 2014 at 09:49:49AM +0200, Javier Martinez Canillas wrote:
Hello Dmitry,
On 08/07/2014 08:09 AM, Dmitry Torokhov wrote:
irq_of_parse_and_map() already sets up IRQ trigger type based on DT
data, by calling irq_create_of_mapping() which in turn calls
[ added missing linux-samsung-soc ML, sorry for the noise ]
On Thursday, August 07, 2014 06:42:28 PM Bartlomiej Zolnierkiewicz wrote:
Add missing check for the case of device without irq specified
in sec_irq_exit() (please note that sec_irq_init() already
correctly handles such devices).
[ added missing linux-samsung-soc ML, sorry for the noise ]
On Thursday, August 07, 2014 06:44:18 PM Bartlomiej Zolnierkiewicz wrote:
sec_irq_init() can fail if it encounters unknown device type or
on regmap_add_irq_chip() error. Add missing sec_irq_init() return
value checking to
On 28/07/14 13:44, Chanwoo Choi wrote:
From: Arnd Bergmann a...@arndb.de
The ADC in s3c64xx is almost the same as exynosv1, but
has a different 'select' method. Adding this here will be
helpful to move over the existing s3c64xx platform from the
legacy plat-samsung/adc driver to the new
On 28/07/14 13:44, Chanwoo Choi wrote:
This patch add support for s3c2410/s3c2416/s3c2440/s3c2443 ADC. The s3c24xx
is alomost same as ADCv1. But, There are a little difference as following:
- ADCMUX register address
- ADCDAT mask (10 bit or 12 bit ADC resolution according to SoC version)
-
On 28/07/14 13:44, Chanwoo Choi wrote:
This patch remove un-necessary white-sapce to code clean.
Signed-off-by: Chanwoo Choi cw00.c...@samsung.com
Applied to the togreg branch of iio.git. Obviously this didn't
need to go through my tree, but as it is so trivial it might
as well do so.
J
---
On 2014년 08월 07일 22:55, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 10:39:29PM +0900, Inki Dae wrote:
On 2014년 08월 07일 22:17, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 10:05:44PM +0900, Inki Dae wrote:
On 2014년 08월 07일 20:09, Thierry Reding wrote:
On Thu, Aug 07, 2014 at 07:49:03PM
28 matches
Mail list logo
