+ ARM maintainers.
It's Gear 2 board support.
Thank you,
Kyungmin Park
On Tue, Sep 30, 2014 at 8:07 PM, Chanwoo Choi wrote:
> This patchset adds new board dts file for Samsung Rinato board (Gear 2) which
> is based on Exynos3250 SoC and adds sleep mode pin configuration us
+ Adding ARM maintainers.
I know it's too late. just to know we trying to push product board
support at mainline.
Thank you,
Kyungmin Park
On Thu, Oct 2, 2014 at 9:50 AM, YoungJun Cho wrote:
> From: Youngjun Cho
>
> This patch adds new board dts file to support Samsung Monk
On Mon, Sep 29, 2014 at 4:22 PM, Pankaj Dubey wrote:
> Hi,
>
> On Monday, September 29, 2014 9:07 AM, Kyungmin Park wrote,
>> To: Pankaj Dubey
>> Cc: Chanwoo Choi; Kukjin Kim; Russell King - ARM Linux;
> naus...@samsung.com;
>> Tomasz Figa; linux-samsung-soc;
t UART 2,3.
>>
>
> As per Exynos3250 user manual that I have with me it supports UART(0,1,2,3).
> It has been mentioned
which UM do you use? There are two UARTs at rev0.01
> in UART Chapter as well as CMU IP details also mentioned about the clock
> entries. We have tested it
> a
add Mr. Dae
On Thu, May 22, 2014 at 11:16 PM, Rahul Sharma wrote:
> Hi Inki,
>
> This is another one which has not got reviewed. Please review.
>
> Regards,
> Rahul Sharma
>
> On 30 April 2014 19:11, Rahul Sharma wrote:
>> From: Rahul Sharma
>>
>> While testing S2R on exynos board, system is ha
On Sat, Mar 15, 2014 at 2:35 AM, Tomasz Figa wrote:
> Hi Chanwoo, Mark,
>
>
> On 14.03.2014 11:56, Chanwoo Choi wrote:
>>
>> Hi Mark,
>>
>> On 03/14/2014 07:35 PM, Mark Rutland wrote:
>>>
>>> On Fri, Mar 14, 2014 at 07:14:37AM +, Chanwoo Choi wrote:
Hi Mark,
On 03/14/2014 0
om now to show it.
Lots of time is going from last reply. there are two options.
1. just waiting more
2. remove it as patch and start it again by someone.
what's the opinions?
Thank you,
Kyungmin Park
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
default".
>>
>> * If we set the pinmux up as "output" then there's a chance that the
>> line will glitch at bootup since the pinmux happens (changing the pin
>> to output) before the driver has a chance to run.
>
> I think that last point should be
On Tue, Nov 5, 2013 at 5:04 PM, Tushar Behera wrote:
> On 5 November 2013 13:27, Kyungmin Park wrote:
>> On Tue, Nov 5, 2013 at 3:29 PM, Tushar Behera
>> wrote:
>>> On 31 October 2013 21:46, Lee Jones wrote:
>>>> On Thu, 31 Oct 2013, Tushar Behera wrote:
&
.name = "s5m-rtc",
>>> - },
>>> + }, {
>>> + .name = "s5m8767-clk",
Do you want to handle these as "clock"? previous time, it's
implemented at regulator. please see drivers/regulator/max* series.
Thank you,
Kyung
ery wasteful.
>
> This patch modifes the code such that, i2c bus registers to
> cpu_freq_transition only if CONFIG_CPU_FREQ_S3C24XX is enabled.
>
> This change should save a bunch of cpufreq transitions calls
> which does not apply to exynos SoCs.
>
> Signed-off-by: Naveen K
On Mon, Jun 17, 2013 at 7:17 AM, Doug Anderson wrote:
> It's convenient if get_maintainer suggests sending samsung/exynos
> pinctrl changes to linux-samsung-soc and to Tomasz and Thomas.
>
> Signed-off-by: Doug Anderson
Acked-by: Kyungmin Park
> ---
> Changes in v2:
>
igned-off-by: Arnd Bergmann
> Cc: linux-...@lists.infradead.org
> Cc: Kyungmin Park
Acked-by: Kyungmin Park
> Cc: David Woodhouse
> ---
> drivers/mtd/onenand/samsung.c | 4
> ++--
> .../include/plat/regs-onenand.h => drivers/mtd/onenan
header file explicitly.
It's really wanted feature.
>
> Signed-off-by: Arnd Bergmann
Acked-by: Kyungmin Park
> ---
> arch/arm/mach-exynos/dev-uart.c | 1 +
> arch/arm/mach-exynos/include/mach/irqs.h | 5 -
> arch/arm/mach-exynos/mach-armlex4210.c | 2 ++
> arch/a
equivalent dt support added for these boards?
>
> I think Tomasz has some initial dts files for Universal_c210 ready, and
> Nuri could probably just be dropped. But we need Kyungmin's opinion on
> that.
Agree.
Tomasz will send unviersal DT files soon.
Thank you,
Kyungmin Park
>
>
st to enable power when usb is connected only.
In our case, micro IC detects the usb connection and enable usb power
at that time.
Thank you,
Kyungmin Park
>
> Signed-off-by: Tushar Behera
> ---
>
> Based on v3.8.
>
> arch/arm/mach-exynos/mach-origen.c |2 ++
> 1 files cha
.init_late = exynos_init_late,
> - .init_time = mct_init,
> + .init_time = exynos_init_time,
> .reserve= &smdkv310_reserve,
> .restart= exynos4_restart,
> MACHINE_END
> diff --git a/arch/arm/mach-exynos/mach-universal_
-s3c24xx/mach-tct_hammer.c
>
> bh...@samsung.com
> mentioned in:
> arch/arm/mach-s5pc100/mach-smdkc100
> and a bunch of files in arch/arm/mach-s5pc100
FYI: He's left the company. and he doesn't work it anymore, so you can drop him.
Thank you
driver uses 4210 and
>> 4212 to differentiate between different register addresses and
>> features, but most things are just exynos4-hdmi compatible.
I would like to distinguish between 4210 and 4x12. since it has
different features. e.g., HDMI v1.3 and v1.4.
and I also want to use 4412
or master; and 1 is for slave */
> + unsigned inti2c_mode;
If it's used for master or not, doesn't better to use 'is_master' or
'is_slave'? what's the meaning of 'i2c_mode'?
and
#define is_master(i2c) (i2c->is_master)
Thank you,
Kyungmi
Acked-by: Kyungmin Park
On Thu, Nov 29, 2012 at 2:05 PM, Naveen Krishna Chatradhi
wrote:
> From: Simon Glass
>
> There is a rather odd feature of the exynos i2c controller that if it
> is left enabled, it can lock itself up with the clk line held low.
> This makes t
compatible = "insignal,origen4quad", "samsung,exynos4412";
> +
> + memory {
> + reg = <0x4000 0x4000>;
> + };
does it test to boot with this dts file?
does it support 1GiB memory section?
Thank you,
Kyungmin Park
> +
> +
On 11/26/12, Thomas Abraham wrote:
> With device tree support enabled for dwmci controller, the unused non-dt
> support
> for dwmci controller can be removed.
Are there no problem to use legacy board? e.g., universal_c210.
>
> Signed-off-by: Thomas Abraham
> ---
> arch/arm/mach-exynos/Makefile
hy code from mach-s3c64xx. Same can be done for other
>> SoCs
>> when they start supporting this phy driver.
>> This driver is tested with smdk6410 and Exynos4210(with DT).
>>
>> Praveen Paneri (5):
>> usb: phy: samsung: Introducing usb phy driver for hsotg
>>
On 10/29/12, Linus Walleij wrote:
> On Wed, Oct 24, 2012 at 4:37 PM, Tomasz Figa wrote:
>
>> This patch extends the driver with any necessary SoC-specific
>> definitions to support Exynos4x12 SoCs.
>>
>> Signed-off-by: Tomasz Figa
>> Signed-off-by: Kyungm
+ Arnd, Olof,
Tomasz,
I think it's better to add arm-soc maintainers at CC when send the patches.
Samsung patches doesn't handled or merged with proper time.
Thank you,
Kyungmin Park
On 10/22/12, Tomasz Figa wrote:
> On Friday 12 of October 2012 11:49:38 Tomasz Figa wrote:
>&
, drm patches are hold only at local git.
How do you think?
Thank you,
Kyungmin Park
On 10/16/12, Rahul Sharma wrote:
> Hi Mr. Park, Mr. Kim,
>
> I had a suggestion here from Tomasz about dividing this patch-set into
> 2 portions:
>
> 1) DT related (patches 1-4) for samsung-dt branch.
+ Tomasz Figa,
Acked-by: Kyungmin Park
On Mon, Oct 15, 2012 at 10:28 PM, Felipe Balbi wrote:
> On Fri, Oct 12, 2012 at 03:45:34PM +0530, Praveen Paneri wrote:
>> platform_set_drvdata() required for driver's remove function, so adding
>> it back.
>>
>> From v6
>> supported) and return an error instead of trying to modify an inexistent
>> register.
>>
>> Signed-off-by: Tomasz Figa
>
> I'm quite happy with these 17 patches, but I'd like to have Thomas
> Abraham's definitive ACK before I merge anything.
Thoma
upport. we can solve this issue and use generic pinctrl drivers.
For all series.
Reviewed-by: Kyungmin Park
>
> 1) What the first part does, in addition to various related fixes, is
> removing any unnecessary static data from pinctrl-exynos driver.
>
> This is achieved mos
Hi Arnd or Olof,
Can you pick up for v3.7?
To Tomasz,
Can you rebase it on the latest arm-soc tree?
Thank you,
Kyungmin Park
On Tue, Oct 2, 2012 at 6:13 PM, Tomasz Figa wrote:
> Hi,
>
> On Monday 24 of September 2012 16:28:27 Tomasz Figa wrote:
>> Some Exynos-based boards a
;> - simplify error handling in vb2_dc_get_dmabuf (from Laurent Pinchart)
>
> For now, NACK. See below.
Sad news!
It's failed to merge by very poor samsung board support at mainline.
CC arm & samsung mailing list.
Thank you,
Kyungmin Park
>
> I spent 4 days trying to setup a
@ static void __init exynos5250_dt_map_io(void)
> s3c24xx_init_clocks(2400);
> }
>
> +static void smdk_hpd_setup(void)
> +{
> + s3c_gpio_cfgpin(EXYNOS5_GPX3(7), S3C_GPIO_SFN(0xf));
> + s3c_gpio_setpull(EXYNOS5_GPX3(7), S3C_GPIO_PULL_DOWN);
> +}
these sho
ve issue.
IOW it's not exynos specific, but arm specific issue.
Thank you,
Kyungmin Park
>
> [1]: ARM: EXYNOS: Add support for secondary CPU bring-up on Exynos4412
>
> ---
>
> Thanks,
> Matt
> --
> To unsubscribe from this list: send the line "unsubscribe linux
lleij for all.
Now samsung tree is merged so if you don't mind, can you merge it by
pinctl tree?
Thank you,
Kyungmin Park
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Acked-by: Kyungmin Park
On 9/17/12, Praveen Paneri wrote:
> This driver uses usb_phy interface to interact with s3c-hsotg. Supports
> phy_init and phy_shutdown functions to enable/disable phy. Tested with
> smdk6410 and smdkv310. More SoCs can be brought under later.
>
> Signed-
On 9/22/12, Olof Johansson wrote:
> On Fri, Sep 21, 2012 at 10:57 PM, Kyungmin Park
> wrote:
>> On 9/22/12, Olof Johansson wrote:
>>> On Wed, Sep 19, 2012 at 3:10 AM, Tomasz Figa wrote:
>>>> Hi Olof,
>>>>
>>>> On Saturday 15 of September
interface for platforms to specify available firmware
>> operations and call them.
>>
>> A wrapper macro, call_firmware_op(), checks if the operation is provided
>> and calls it if so, otherwise returns 0.
>>
>> By default no operations are provided.
>>
>&g
me.
As it touched at several places, it's defined at iodesc. if it changed
with ioremap, it has to export remaped address and each codes should
use it.
As I wrote at cover letter, if you want to use ioremap, it can be
modified. however can you merge firmware codes itself? since ioremap
is not re
;
>> This series adds support for specifying firmware operations, implements
>> some firmware operations for Exynos secure firmware and adds a method of
>> enabling secure firmware operations on Exynos-based boards through board
>> file and device tree.
>>
>> This
imd or fb?. I think 'fb' is used
for framebuffer historically.
but now it's used both fb and drm, so fimd is neutral and architecture
specific.
To do this, Modify arch-exynos first and update it at each drivers it properly.
Thank you,
Kyungmin Park
> + fimd using DRM fra
Acked-by: Kyungmin Park
# git grep HAVE_SCHED_CLOCK arch/arm/
arch/arm/Kconfig: select HAVE_SCHED_CLOCK
arch/arm/mach-exynos/Kconfig: select HAVE_SCHED_CLOCK
On 8/31/12, Barry Song <21cn...@gmail.com> wrote:
> 2012/8/31 Kyungmin Park :
>> Hi,
>>
>> then where
Hi,
then where select it HAVE_SCHED_CLOCK? apart from other exynos board,
universal have to use another clock.
Thank you,
Kyungmin Park
On 8/31/12, Barry Song wrote:
> From: Barry Song
>
> Signed-off-by: Barry Song
> ---
> arch/arm/mach-exynos/Kconfig |1 -
>
+ Thomas Abraham,
> -Original Message-
> From: Tomasz Figa [mailto:t.f...@samsung.com]
> Sent: Wednesday, August 29, 2012 10:13 PM
> To: linux-samsung-soc@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org; kyungmin.p...@samsung.com;
> kgene@samsung.com; jy0922.s...@samsung.com
On 8/29/12, Kukjin Kim wrote:
> On 08/28/12 04:08, Tomasz Figa wrote:
>> Using secure MDMA1 on TrustZone-enabled boards causes early boot crash,
>> so use non-secure instead.
>>
>> Signed-off-by: Tomasz Figa
>> Signed-off-by: Kyungmin Park
>> ---
>>
ail/linux-arm-kernel/2012-May/101522.html
It's perference issue. some person like this style. others doesn't.
Moreever vender, System LSI, provided codes have whole different style.
It lists up whole gpios for each SoCs.
EXYNOS4210_{A0, Z}
EXYNOS4412_{A0, V4}
EXYNOS5250_{A0,
t;
> So the probable steps in getting started with using device tree for
> Exynos4412 would be
>
> 1. Create a new exynos4.dtsi file with all the Exynos4 common
> properties for all dt supported controllers.
> 2. Update the exynos4210.dtsi file accordingly and add the new
> exynos441
Hi,
Now another person try to use drivers/usb/phy for it.
"usb: phy: samsung: Introducing usb phy driver for hsotg"
Can you use it instead of previous one?
Thank you,
Kyungmin Park
On 8/6/12, Dongjin Kim wrote:
> This patch support to control USB HSIC of EXYNOS4,
> edited based
On 8/7/12, Praveen Paneri wrote:
> Hi,
>
> On Mon, Aug 6, 2012 at 3:21 PM, Praveen Paneri
> wrote:
>> Hi,
>>
>> On Mon, Aug 6, 2012 at 2:53 PM, Heiko Stübner wrote:
>>> Am Montag, 6. August 2012, 10:23:52 schrieb Kyungmin Park:
>>>> Hi
does the "sec" in sec_usbphy for?
> Its Samsung Electronics Co. :)
I'm also prefer to use 'samsung' or 'exynos'. Since I didn't see the
'sec' prefix for samsung drivers.
Thank you,
Kyungmin Park
>
> Praveen
>
On Fri, Jul 13, 2012 at 8:10 PM, Amit Daniel Kachhap
wrote:
> Add necessary default platform data support needed for TMU driver. This
> dt/non-dt values are tested for origen exynos4210 and smdk exynos5250
> platforms.
Looks good to me.
just nitpicks below.
Thank you,
Kyungmin Park
&
rq);
> + irq_set_affinity(mct_lx_irq, cpumask_of(1));
> }
> } else {
> enable_percpu_irq(EXYNOS_IRQ_MCT_LOCALTIMER, 0);
> @@ -473,7 +478,7 @@ static void __init exynos4_timer_resources(void)
>
> static void __init exynos4_ti
Hi Mark,
BTW, do you know that you're reviewing the same device driver patch
from different person?
One from Mr. Lee and another from Yadwinder.
I wonder how to handle it finally. which one is choose?
Thank you,
Kyungmin Park
On 5/22/12, yadi.bra...@gmail.com wrote:
> From: Yadwind
On Thu, May 10, 2012 at 10:48 PM, Arnd Bergmann wrote:
> On Thursday 10 May 2012, Kyungmin Park wrote:
>> > And I won't apply new feature for non-dt board file from now on. I think,
>> > we
>> > need to support DT in mach-exynos/ instead of non-DT and DT togeth
On 5/10/12, Thomas Abraham wrote:
> Dear Mr. Park,
>
> On 2 May 2012 12:25, Kyungmin Park wrote:
>> Hi,
>>
>> On 5/2/12, Thomas Abraham wrote:
>>> Add device tree based discovery support.
>>>
>>> Signed-off-by: Thomas Abraham
>>
based board files and
get them to work together first, but leave it up to the individual
subarch maintainers whether they want to add other board files into
the mix."
It doesn't mean add new feature to non-DT board. don't add new board file.
In this case, DRM is not yet ready to sup
msung tree directly.
Thank you,
Kyungmin Park
On 5/2/12, Thomas Abraham wrote:
> Add clock instances for bus interface unit clock and card interface unit
> clock of the all four MSHC controller instances.
>
> Signed-off-by: Abhilash Kesavan
> Signed-off-by: Thomas Abraham
&g
Hi,
On 5/2/12, Thomas Abraham wrote:
> The instantiation of the Synopsis Designware controller on Exynos5250
> include extension for SDR and DDR specific tx/rx phase shift timing
> and CIU internal divider. In addition to that, the option to skip the
> command hold stage is also introduced. Add s
Hi,
On 5/2/12, Thomas Abraham wrote:
> Add device tree based discovery support.
>
> Signed-off-by: Thomas Abraham
> ---
> .../devicetree/bindings/mmc/synposis-dw-mshc.txt | 85 +
> drivers/mmc/host/dw_mmc-pltfm.c| 24 +++
> drivers/mmc/host/dw_mmc.c
lets drivers
>> > to be registered into 'disabled' power domains and finally solves
>> > mysterious freezes and lack of resume/suspend calls on Samsung Exynos4
>> > NURI and UniversalC210 platforms.
>> >
>> > Signed-off-by: Marek Szyprows
On 4/17/12, Thomas Abraham wrote:
> On 17 April 2012 12:00, Kyungmin Park wrote:
>> Hi,
>>
>> It's already merged with different patch,
>
> This is a repost of the patch from Heiko Stuebner which would be
> required to fix compilation issue for rtc driver.
On 4/17/12, Thomas Abraham wrote:
> From: Sangsu Park
>
> Add GPC4 bank instance which is included in rev1 of Exynos5.
>
> Cc: Grant Likely
> Signed-off-by: Sangsu Park
> ---
> arch/arm/mach-exynos/include/mach/gpio.h |9 ++---
> drivers/gpio/gpio-samsung.c |8
Hi,
On 4/17/12, Thomas Abraham wrote:
> From: Changhwan Youn
>
> Adapt to changes in GIC physical address in rev1 of Exynos5.
Does it different from rev0 and rev1? and does it support the rev1 only?
Thank you,
Kyungmin Park
>
> Signed-off-by: Changhwan Youn
> ---
>
= "samsung,s3c6410-rtc",
.data = &s3c_rtc_drv_data_array[TYPE_S3C64XX],
},
{},
};
MODULE_DEVICE_TABLE(of, s3c_rtc_dt_match);
#else
#define s3c_rtc_dt_match NULL
#endif
Thank you,
Kyungmin Park
On 4/17/12, Thomas Abraham wrote:
> From: Heiko Stuebne
trl,
> + .ctrlbit= (1 << 19),
Hi,
Can you place this in order? It has same "exynos5_clk_ip_peris_ctrl",
but located under (1 << 20).
Thank you,
Kyungmin Park
> + }, {
> .name = "hsmmc",
> .devn
; Yes I hope so.
> Marek's patch corrects run-time power management in Exynos4 with System MMU.
Hi,
Next time, if you give Acked-By or Reviewed_by, then it's more helpful
to determine to merge or not.
Thank you,
Kyungmin Park
>
> Thank you.
>
> KyongHo
> --
> To uns
Hi,
On Tue, Apr 3, 2012 at 4:17 AM, Kukjin Kim wrote:
> From: Colin Cross
>
> Check the ULCON register of each serial port to determine if
> it has been enabled by the bootloader. If only one serial port
> is found enabled, use that one. Otherwise, use the value from
> CONFIG_S3C_LOWLEVEL_UART
+CC another i2c subsystem maintainer, Wolfram Sang.
On 3/14/12, Karol Lewandowski wrote:
> Changes since v1:
> - Move unrelated code fragment to separate patch (of_match_ptr())
> - Move device-type handling to separate function and rework its
>internals a bit
>
> This patchset reworks i2c-s
Signed-off-by: Marek Szyprowski
>> Signed-off-by: Kyungmin Park
>> ---
>> arch/arm/mach-exynos/Kconfig |1 +
>> arch/arm/mach-exynos/mach-universal_c210.c | 31
>>
>> 2 files changed, 32 insertions(+), 0 delet
+ pstate = pdata->max_width ? "sdhci-pcfg8" : "sdhci-pcfg4";
You should check pdata->max_width == 8 instead of max_width itself.
BTW if platform set the amx_width as 1. How do you handle this?
Thank you,
Kyungmin Park
> + sc->pinctrl = pinctrl_get_select(&
stuff for now and then sorting out
> single kernel for exynos4 and exynos5 next time? Actually, this exynos5 arch
> part is _really_ needed for developing/contribution of drivers on exynos5.
No,
I heard too many times. "we have plan to support ..." but I didn't see
any
Hi,
some not critical comments.
Thank you,
Kyungmin Park
On Tue, Mar 6, 2012 at 5:31 PM, KyongHo Cho wrote:
> HAALgBjAGgAbwBAAHMAYQBtAHMAdQBuAGcALgBjAG8AbQA=;Tue,
> 06 Mar 2012 08:31:29
On 3/6/12, Kukjin Kim wrote:
> On 03/06/12 02:13, Kyungmin Park wrote:
>> On 3/6/12, Kukjin Kim wrote:
>>> On 03/01/12 00:40, Marek Szyprowski wrote:
>>>> Patch 189eb7407 "ARM: EXYNOS: use 'exynos4-sdhci' as device name for
>>>> sdhci
>
nitions for the regulator subsystem. This patch fixes
>> this issue.
>>
>> Signed-off-by: Marek Szyprowski
>> Signed-off-by: Kyungmin Park
>> ---
>> arch/arm/mach-exynos/mach-nuri.c |4 ++--
>> arch/arm/mach-exynos/mach-universal_c210.c |2 +
Hi,
On 3/6/12, KyongHo Cho wrote:
> Handling System MMUs with an identifier is not flexible to manage
> System MMU platform devices because of the following reasons:
> 1. A device driver which needs to handle System MMU must know the ID.
> 2. A System MMU may not present in some implementations o
On 2/28/12, KyongHo Cho wrote:
> QBtAHMAdQBuAGcALgBjAG8AbQA=;Tue,
> 28 Feb 2012 06:37:18
> GMT;WwBQAEEAVABDAEgAIAB2ADkAIAAyAC8AMgBdACAAaQBvAG0AbQB1AC8AZQB4AHkAbgBvAHMAOgAgAEEAZABkACAAaQBvAG0AbQB1ACAAZAByAGkAdgBlAHIAIABmAG8AcgAgAEUAeAB5AG4AbwBzACAAUABsAGEAdABmAG8AcgBtAHMA
> x-cr-puzzleid: {A7DCA01
Hi,
On 2/28/12, KyongHo Cho wrote:
> Handling System MMUs with an identifier is not flexible to manage
> System MMU platform devices because of the following reasons:
> 1. A device driver which needs to handle System MMU must know the ID.
> 2. A System MMU may not present in some implementations
be
fimc.
So I suggest to send exynos4 series patch as before and send
additional exynos5 patch series next.
Thank you,
Kyungmin Park
On 2/28/12, KyongHo Cho wrote:
> Changes since v8:
> - exynos_iommu_map/unmap() just works for the page sizes
>that System MMU supports. (Joerg
> +F: arch/arm/boot/dts/exynos*
> +F: arch/arm/mach-exynos/*dt.c
> +F: Documentation/devicetree/*/*/*samsung*
> +
> ARM/SAMSUNG MOBILE MACHINE SUPPORT
> M: Kyungmin Park
> L: linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> --
> 1.7.1
>
-109,6 +121,7 @@
> #define EXYNOS4_PA_SATAPHY_CTRL 0x126B
>
> #define EXYNOS4_PA_SROMC 0x1257
> +#define EXYNOS5_PA_SROMC 0x1225
>
> #define EXYNOS4_PA_EHCI 0x1258
> #define EXYNOS4_PA_OHCI
+ Karol for DT support later
On Fri, Feb 10, 2012 at 3:58 AM, Thomas Abraham
wrote:
> Dear Mr. HeungJun Kim,
>
> On 27 January 2012 00:21, HeungJun, Kim wrote:
>> This patch adds Samsung Mobile TRATS board support.
>>
>> Signed-off-by: HeungJun, Kim
>
---
> .../include/plat/regs-usb3-exynos-drd.h | 305
>
If special reason, please move to the proper drivers/usb.
Thank you,
Kyungmin Park
> arch/arm/plat-samsung/include/plat/udc-ss.h | 21 ++
> arch/arm/plat-samsung/include/plat/usb
there any reason to put here? I think you can merge with 2/2
patch. I mean you can move it under drivers/misc/c2c.
Thank you,
Kyungmin Park
> 2 files changed, 136 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/mach-exynos/include/mach/c2c.h
> create mode 100644 arch/arm/m
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/mach-exynos/platsmp.c |9 ++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-exynos/platsmp.c b/arch/arm/mach-exynos/platsmp.c
> index 683aec7..dfb4630 100644
> --- a/arch/arm/m
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/mach-exynos/include/mach/map.h | 13 +++--
> 1 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-exynos/include/mach/map.h
> b/arch/arm/mach-exynos/include/mach/map.h
> index f88acaf.
On 2/1/12, Kukjin Kim wrote:
> Cc: Thomas Abraham
> Cc: Greg Kroah-Hartman
> Signed-off-by: Kukjin Kim
> ---
> drivers/tty/serial/samsung.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c
> index 3b07fb9
As I remember only DT based board file is acceptable for mainline?
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/mach-exynos/Kconfig | 11
> arch/arm/mach-exynos/Makefile|2 +
> arch/arm/mach-exynos/mach-smdk5250.c | 94
>
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/Makefile|1 +
> arch/arm/mach-exynos/Kconfig | 13 ++
> arch/arm/mach-exynos/Makefile|1 +
> arch/arm/mach-exynos/common.c| 163
> +
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/mach-exynos/Makefile |2 +-
> arch/arm/mach-exynos/setup-i2c0.c | 13 +
> 2 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-exynos/Makefile b/arch/arm/mach-exynos/Makefi
On 2/1/12, Kukjin Kim wrote:
> Signed-off-by: Kukjin Kim
> ---
> arch/arm/mach-exynos/clock-exynos5.c | 1258
>
> arch/arm/mach-exynos/include/mach/regs-clock.h | 62 ++
Doesn't it better split the three header files?
regs-clock.h as wrapper. regs-clock-exynos
*cfg, int no);
> extern void exynos4_map_io(void);
> extern void exynos4_init_clocks(int xtal);
> -extern void exynos4_init_uarts(struct s3c2410_uartcfg *cfg, int no);
Are there any cases build without CONFIG_ARCH_EXYNOS?
I think it's always defined CONFIG_ARCH_EXYNOS.
Thank you,
ble of working.
If it assumes it has 8 gpios, you can make it simple calculate it like this.
enum exynos5_gpios {
EXYNOS5_GPIO_A,
...
};
EXYNOS5_GPIO_A_START(n) (EXYNOS5_GPIO_A * 8)
with this one, it can make a simple gpio driver when using irq domain for GPIO.
Thank y
restart is also required.
On 1/31/12, Karol Lewandowski wrote:
> Commit 4e44d2cb95bd ("ARM: exynos4: convert to CONFIG_MULTI_IRQ_HANDLER")
> converted all exynos boards but exynos4-dt.c.
>
> This commit fixes that omission.
>
> Signed-off-by: Karol Lewandowski
&g
lk_add_alias().
Hi,
Doesn't it better to add common.c?
Are there any reason to add each board files?
Thank you,
Kyungmin Park
>
> Cc: Jonghwan Choi
> Signed-off-by: Jingoo Han
> ---
> arch/arm/mach-exynos/mach-nuri.c |2 ++
> arch/arm/mach-exynos/mach-origen.c
xynos/common.c:396: error: dereferencing pointer to
> incomplete type
>
> Following A and B have been created from different base and the build
> error was casued in the process of merging and should be fixed in this
> merge window.
Acked-by: Kyungmin Park
Do the same job. boot tested.
>
&
platforms, the power domains are statically
> instantiated. For dt platforms, the power domain nodes found in the device
> tree are instantiated.
>
> Cc: Rafael J. Wysocki
> Cc: Kukjin Kim
> Cc: Kyungmin Park
> Cc: Rob Herring
> Cc: Grant Likely
> Signed-off-by: Th
Hi,
It's not clear to add the panel data at platform_lcd. It's board
specific and it's used the gpio only.
So no need to specific it like HYDIS_HV070WSA. just define
PLATFORM_LCD_GPIO or similar.
How do you think?
Thank you,
Kyungmin Park
On 1/2/12, Thomas Abraham wrote:
>
On 12/27/11, Kukjin Kim wrote:
> Kyungmin Park wrote:
>>
>> On 12/27/11, Kukjin Kim wrote:
>> > Kyungmin Park wrote:
>> >>
>> >> On 12/24/11, Kukjin Kim wrote:
>> >> > HeungJun, Kim wrote:
>> >> >>
>> &g
On 12/27/11, Kukjin Kim wrote:
> Kyungmin Park wrote:
>>
>> On 12/24/11, Kukjin Kim wrote:
>> > HeungJun, Kim wrote:
>> >>
>> >> This patch adds Samsung Mobile TRATS board support.
>> >>
>> >> Signed-off-by: HeungJun, Kim
&
On 12/24/11, Kukjin Kim wrote:
> HeungJun, Kim wrote:
>>
>> This patch adds Samsung Mobile TRATS board support.
>>
>> Signed-off-by: HeungJun, Kim
>> Signed-off-by: Kyungmin Park
>> ---
>> arch/arm/mach-exynos/Kconfig | 11 ++
>> arch/
1 - 100 of 334 matches
Mail list logo