On Tue, 15 Jul 2014, Amit Daniel Kachhap wrote:
> This is a cleanup patch and moves min/step voltages in a common samsung
> header file so that they can be used by other s2mpxxx PMIC drivers. Only
> few required macros are added currently and others can be added if needed.
>
> Cc: Sangbeom Kim
>
Hi Andreas,
On 7/27/14, Andreas Färber wrote:
> Hi Ajay,
>
> Am 25.07.2014 21:22, schrieb Ajay Kumar:
>> This series is based on exynos-drm-next branch of Inki Dae's tree at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
>>
>> I have tested this after adding few DT chang
On Sun, Jul 27, 2014 at 8:44 PM, Olof Johansson wrote:
> On Sun, Jul 27, 2014 at 8:30 PM, Doug Anderson wrote:
>> Kukjin,
>>
>> On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim wrote:
>>> Oops, I always use my script to check kernel build like follow...
>>>
>>> $ mt
>>> building exynos_defconfig done
Hi Arnd,
On Wednesday, June 18, 2014 Arnd wrote:
> To: Tomasz Figa
> Cc: linux-arm-ker...@lists.infradead.org; mark.br...@linaro.org; Tomasz
Figa;
> linux-samsung-soc@vger.kernel.org; Kukjin Kim; Russell King - ARM Linux;
Samuel
> Ortiz; Pankaj Dubey; linux-ker...@vger.kernel.org; jo...@samsung.co
On Sun, Jul 27, 2014 at 8:30 PM, Doug Anderson wrote:
> Kukjin,
>
> On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim wrote:
>> Oops, I always use my script to check kernel build like follow...
>>
>> $ mt
>> building exynos_defconfig done
>> building s3c2410_defconfig done
>> building s3c6400_defconfig
Kukjin,
On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim wrote:
> Oops, I always use my script to check kernel build like follow...
>
> $ mt
> building exynos_defconfig done
> building s3c2410_defconfig done
> building s3c6400_defconfig done
> building s5pv210_defconfig done
>
> but seems it couldn't
Hi Tomasz,
On Friday, July 25, 2014 Tomasz Figa wrote:
> To: Pankaj Dubey; 'Kukjin Kim'; linux-arm-ker...@lists.infradead.org;
linux-
> samsung-...@vger.kernel.org; linux-ker...@vger.kernel.org
> Cc: li...@arm.linux.org.uk; t.f...@samsung.com; vikas.saj...@samsung.com;
> jo...@samsung.com; naus..
Replaced the "disable-wp" into host's quirks.
(Because the slot-node is removed at dt-file.)
Signed-off-by: Jaehoon Chung
Tested-by: Sachin Kamat
Acked-by: Seungwon Jeon
---
drivers/mmc/host/dw_mmc.c | 12 +---
include/linux/mmc/dw_mmc.h |6 ++
2 files changed, 7 insertions(
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 to "cap-sd/mmc-highspeed".
Signed-off-by: Ja
Almost 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
Reviewed-b
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 to "cap-mmc/sd-highspeed" property.
Chnagelog V7:
- Fixed typo and modified the commit message.
Changelog V
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 to "cap-sd/mmc-highspeed".
Signed-off-by: Ja
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 to "cap-sd/mmc-highspeed".
Signed-off-by: Ja
Hi, Andreas,
On 07/25/2014 09:11 PM, Andreas Färber wrote:
> Hi Jaehoon,
>
> Am 25.07.2014 03:11, schrieb Jaehoon Chung:
>> Almost Soc is used the slot per a host.
>
> Something's very wrong with this sentence. What are you trying to say?
> Almost all SoCs use one slot only per host controller d
This patch adds LPM transfer support for video or command data.
With this patch, Exynos MIPI DSI controller can transfer command or
video data with HS or LP mode in accordance with mode_flags set
by LCD Panel driver.
Changelog v2: Enable High Speed clock only in case of stand by request.
Signed-
This patch series adds lpm tranfer support for video and command data.
for this, this patch adds two flags, and makes mipi dsi host to send
commands to lcd panel device with lpm if mode_flags of lcd panel driver
includes lpm flag.
and also it applies this feature to exynos mipi dsi driver.
Chang
This patch adds below two flags for LPM transfer, and it attaches LPM flags
to a msg in accordance with master's mode_flags set by LCD Panel driver.
MIPI_DSI_MODE_CMD_LPM
- If this flag is set by Panel driver, MIPI-DSI controller will tranfer
command data to Panel device in Low Power Mode.
MIPI_D
Andreas Färber wrote:
>
> Am 27.07.2014 05:08, schrieb Andreas Färber:
> > On the ODROID-XU (with local patches based on smdk5410) I get the
> > following with earlyprintk:
> >
> > Uncompressing Linux... done, booting the kernel.
> > [0.00] Booting Linux on physical CPU 0x0
> > [0.
Andreas Färber wrote:
>
> Am 27.07.2014 14:22, schrieb Andreas Färber:
> > Hello,
> >
> > This mini-series unbreaks booting on 5410 based ODROID-XU.
> >
> > Since I do not have access to a TRM, the address is a guess based on
> > 5250 and 5410. Such a node was not present in the 3.14 downstream tr
Andreas Färber wrote:
>
> Hi Kukjin,
>
Hi,
> Are you aware that `make dtbs` fails on your for-next branch (4533046)?
>
> DTC arch/arm/boot/dts/exynos5420-peach-pit.dtb
> arch/arm/boot/dts/exynos5420-peach-pit.dts:447:33: fatal error:
> cros-ec-keyboard.dtsi: No such file or directory
> #
Am Sonntag, 27. Juli 2014, 23:10:21 schrieb Hartmut Knaack:
> Arnd Bergmann schrieb:
> > @@ -205,6 +217,9 @@ static void exynos_adc_v1_init_hw(struct exynos_adc
> > *info)>
> > /* Enable 12-bit ADC resolution */
> > con1 |= ADC_V1_CON_RES;
> > writel(con1, ADC_V1_CON(info->regs));
> >
Arnd Bergmann schrieb:
> This adds support for the touchscreen on Samsung s3c64xx.
> The driver is completely untested but shows roughly how
> it could be done, following the example of the at91 driver.
>
> Open questions include:
>
> - compared to the old plat-samsung/adc driver, there is
> no s
Chanwoo Choi schrieb:
> 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 to select channel
> - ADCDAT mask (10bit or 12bit ADC resolution according to SoC version)
Hi,
Chanwoo Choi schrieb:
> From: Arnd Bergmann
>
> 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 exynos-adc.
>
> Signed-off-by
Hi Ajay,
Am 25.07.2014 21:22, schrieb Ajay Kumar:
> This series is based on exynos-drm-next branch of Inki Dae's tree at:
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
>
> I have tested this after adding few DT changes for exynos5250-snow,
> exynos5420-peach-pit and exyno
Am 27.07.2014 05:08, schrieb Andreas Färber:
> On the Arndale Octa (5420) I see an asynchronous external abort on
> serial console when systemd gets started.
>
> http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34680.html
This turned out to be somehow caused by MCPM driver. Disabl
Hi Chris & Ulf,
I hope you find this patch for next.
Thanks,
Seungwon Jeon
On Wed, May 21, 2014, Seungwon Jeon wrote:
> On Wed, May 21, 2014, Doug Anderson wrote:
> > If we happened to get a data error at just the wrong time the dw_mmc
> > driver could get into a state where it would never compl
Am 27.07.2014 07:57, schrieb Andreas Färber:
> Am 27.07.2014 05:08, schrieb Andreas Färber:
>> On the ODROID-XU (with local patches based on smdk5410) I get the
>> following with earlyprintk:
>>
[...]
>> [0.00] Kernel panic - not syncing: failed to find exynos pmu
>> register
[...]
>>
>> Re
Am 27.07.2014 14:22, schrieb Andreas Färber:
> Hello,
>
> This mini-series unbreaks booting on 5410 based ODROID-XU.
>
> Since I do not have access to a TRM, the address is a guess based on
> 5250 and 5410. Such a node was not present in the 3.14 downstream tree.
s/5410/5420/
>
> Regards,
> A
Exynos initialization code now relies on obtaining the PMU address,
so add the new 5410 value to the list of compatible string matches.
This unbreaks booting on 5410 based boards.
Fixes: fce9e5bb2526 ("ARM: EXYNOS: Add support for mapping PMU base address via
DT")
Signed-off-by: Andreas Färber
-
Exynos initialization code now relies on obtaining the PMU address,
so prepare a PMU node for Exynos5410.
Fixes: fce9e5bb2526 ("ARM: EXYNOS: Add support for mapping PMU base address via
DT")
Signed-off-by: Andreas Färber
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 inserti
Hello,
This mini-series unbreaks booting on 5410 based ODROID-XU.
Since I do not have access to a TRM, the address is a guess based on
5250 and 5410. Such a node was not present in the 3.14 downstream tree.
Regards,
Andreas
Andreas Färber (3):
Documentation: devicetree: Document exynos5410 P
We will start using "samsung,exynos5410-pmu".
Signed-off-by: Andreas Färber
---
Documentation/devicetree/bindings/arm/samsung/pmu.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/samsung/pmu.txt
b/Documentation/devicetree/bindings/arm/samsung/pmu.txt
33 matches
Mail list logo
