Re: [GIT PULL 6/9] ARM: EXYNOS: clk: Another clock dependency, ARMv7, for v4.5

[Olof Johansson]

On Wed, Dec 23, 2015 at 07:55:11PM +0900, Krzysztof Kozlowski wrote:
> W dniu 22.12.2015 o 13:51, Olof Johansson pisze:
> > On Wed, Dec 02, 2015 at 10:39:43AM +0900, Krzysztof Kozlowski wrote:
> >> Hi Kukjin,
> >>
> >> This is also clock dependency. I put it in separate tag in case clock
> >> folks want to pull it also.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 
> >> 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> >>
> >>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> >>
> >> are available in the git repository at:
> >>
> >>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> >> tags/samsung-clk-exynos4-4.5
> >>
> >> for you to fetch changes up to 94af7a3c310f5877dc6f756179b92f24f89a9b08:
> >>
> >>   clk: samsung: exynos4: Add SSS gate clock (2015-11-18 22:02:02 +0900)
> > 
> > Again, this should probably go through the clk maintainer (or have an ack).
> > It's just two one-line changes though, so if they're slow to respond we can
> > take it as a fallback. Resend if that's the case.
> > 
> 
> Wait, I am missing something. This contains only one patch which has the
> Stephen's Boyd ack:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/379230.html
> (this is in commit message already)
> 
> What kind of ack do you expect here? Ack for pull-request?

Yeah, looks good. I likely mixed up branch contents when I replied to this one.

I'll merge it into drivers. Still, for patches that only touches clock
subsystem, the default of merging through those subsystem maintainers is
preferred. Complications, of course, are when there's dependencies.


-Olof
--
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

Re: [GIT PULL 3/9] ARM64: EXYNOS: clk: Clock dependency for ARM64 for v4.5

[Olof Johansson]

Hi,

Sorry for the slow reply, holidays and vacation and all that.

On Wed, Dec 23, 2015 at 07:44:32PM +0900, Krzysztof Kozlowski wrote:
> W dniu 22.12.2015 o 13:46, Olof Johansson pisze:
> > On Wed, Dec 02, 2015 at 10:39:40AM +0900, Krzysztof Kozlowski wrote:
> >> Hi Kukjin,
> >>
> >> Dependency for soc64 changes.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 
> >> 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> >>
> >>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> >>
> >> are available in the git repository at:
> >>
> >>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> >> tags/samsung-clk-arm64-symbols-4.5
> >>
> >> for you to fetch changes up to 8c2a90ed18a74e8b9cdbba679403faa44d6024fc:
> >>
> >>   clk: samsung: Don't build ARMv8 clock drivers on ARMv7 (2015-11-22 
> >> 19:25:29 +0900)
> > 
> > Hi,
> > 
> > Looks like this lacks ack from any of the clock maintainers.
> 
> It got the ack from Sylwester and Tomasz - Samsung clock maintainers. If
> it is not sufficient... then let's wait with it for v4.6. I am on
> holidays now so I cannot really do anything meaningful with it.

Ok -- even though we have per-driver maintainers, we still look for acks from
the overall subsystem maintainers on these drivers. 

> > Given that EXYNOS_ARM64_COMMON_CLK is not yet introduced, this will cause
> > a breakage in bisectability on some of these platforms as well.
> 
> The patch introduces EXYNOS_ARM64_COMMON_CLK which will be enabled by
> default on our platforms. What kind of breakage do you have in mind?

Ah, I probably missed that.


-Olof
--
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

Re: [PATCH] ARM: multi_v7_defconfig: Enable fan, sensors and audio for Odroid XU3

[Olof Johansson]

On Wed, Dec 23, 2015 at 07:37:17PM +0900, Krzysztof Kozlowski wrote:
> From: Krzysztof Kozlowski 
> 
> For Odroid XU3-family enable the:
>  - PWM fan (to control the CPU fan using thermal subsystem),
>  - TI INA231 sensors (provide power measurements of big.LITTLE cores,
>DRAM and GPU),
>  - Samsung sound (for Odroid XU3 and Snow as well).
> 
> Signed-off-by: Krzysztof Kozlowski 
> Reviewed-by: Javier Martinez Canillas 
> 
> ---
> 
> Resending with Javier's tag.

Thanks, applied but had to resolve conflicts.


-Olof

--
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

Re: [GIT PULL 2/9] ARM: EXYNOS: Exynos SoC/mach specific code for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:39AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> SoC/mach specific code.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-soc-4.5
> 
> for you to fetch changes up to 8438aef01d3560549b3a95d247b3a69311fa6f2d:
> 
>   ARM: EXYNOS: Remove redundant code from regs-pmu.h (2015-11-20 16:00:47 
> +0900)

Thanks, merged into next/soc.


-Olof

--
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

Re: [GIT PULL 7/9] ARM: EXYNOS: dts: DeviceTree for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:44AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> A lot of stuff here, mostly cleanups. Description in tag.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-dt-4.5
> 
> for you to fetch changes up to 2cf107f1033e0343d45b59d06f16487c8362702f:
> 
>   ARM: dts: Unify G2D device node with other devices on exynos4 (2015-11-30 
> 17:00:43 +0900)
> 
> 
> Samsung DeviceTree updates and improvements for 4.5:
> 1. Pinctrl for Exynos5410.
> 2. eMMC/SDIO minor fixes usage of bindings on Snow and Peach
>Chromebooks.
> 3. Remove FIMD from Odroid XU3-family because on XU3 it cannot be used
>yet and on XU3-Lite and XU4 it is not supported.
> 4. Remove deprecated since June 2013 samsung,exynos5-hdmi.
> 5. Add support for Pseudo Random Generator on Exynos4 (Trats2 for now).
>This depends on new SSS clock.
> 6. Add rotator nodes for Exynos4 and Exynos5.
> 7. Switch DWC3_1 on Odroid XU3 and XU3-Lite to peripheral mode because
>now it cannot be used as OTG.
> 8. Cleanup the G2D usage on Exynos4 and add it to a proper domain
>in case of Exynos4210.
> 9. Put MDMA1 in proper domain on Exynos4210 as well.
> 10. Minor cleanups.

Given the request to get acks for the pinctrl changes, can you respin this
branch without those pieces so we can merge in the rest of it?


Thanks!


-Olof
--
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

Re: [GIT PULL 6/9] ARM: EXYNOS: clk: Another clock dependency, ARMv7, for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:43AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> This is also clock dependency. I put it in separate tag in case clock
> folks want to pull it also.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-clk-exynos4-4.5
> 
> for you to fetch changes up to 94af7a3c310f5877dc6f756179b92f24f89a9b08:
> 
>   clk: samsung: exynos4: Add SSS gate clock (2015-11-18 22:02:02 +0900)

Again, this should probably go through the clk maintainer (or have an ack).
It's just two one-line changes though, so if they're slow to respond we can
take it as a fallback. Resend if that's the case.


-Olof

--
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

Re: [GIT PULL 5/9] ARM: EXYNOS: Drivers for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:42AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> Pinctrl for v4.5.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-drivers-4.5
> 
> for you to fetch changes up to 023e06dfa6882f500b9c86fd61f0b1913aa07f36:
> 
>   pinctrl: exynos: add exynos5410 SoC specific data (2015-11-16 10:54:43 
> +0900)

Hi,

This should either go in through the pinctrl tree, or have an acked/reviewed-by
one of the pinctrl maintainers.



-Olof
--
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

Re: [GIT PULL 3/9] ARM64: EXYNOS: clk: Clock dependency for ARM64 for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:40AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> Dependency for soc64 changes.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-clk-arm64-symbols-4.5
> 
> for you to fetch changes up to 8c2a90ed18a74e8b9cdbba679403faa44d6024fc:
> 
>   clk: samsung: Don't build ARMv8 clock drivers on ARMv7 (2015-11-22 19:25:29 
> +0900)

Hi,

Looks like this lacks ack from any of the clock maintainers.

Given that EXYNOS_ARM64_COMMON_CLK is not yet introduced, this will cause
a breakage in bisectability on some of these platforms as well.

I'll hold off on this one for a bit.


-Olof
--
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

Re: [GIT PULL 4/9] ARM64: EXYNOS: Soc specific code for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:41AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> ARM64 change touch also defconfig.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-soc64-4.5
> 
> for you to fetch changes up to db44c07a3f0b32815bd1f3e731db9e043e57cf9c:
> 
>   arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS (2015-11-22 
> 19:31:30 +0900)

Given that Arnd started splitting out config64 separately, there's a small
chance we'll get a conflict here. We can deal with that if needed though.

Still, since this branch contains the previous clock branch I can't apply it
as it is. Can you respin without that for now?


-Olof

--
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

Re: [GIT PULL 8/9] ARM64: EXYNOS: dts: DeviceTree for ARM64 for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:45AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> Few changes for Espresso board.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-dt64-4.5
> 
> for you to fetch changes up to fb026cb6524744c8bd0f133f4b0d8e2595d04e15:
> 
>   arm64: dts: Add reboot node for exynos7 (2015-11-18 22:47:16 +0900)

Thanks, merged into next/dt64.


-Olof
--
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

Re: [PATCH] ARM: multi_v7_defconfig: Enable fan, sensors and audio for Odroid XU3

[Olof Johansson]

On Thu, Dec 17, 2015 at 08:50:24PM +0900, Krzysztof Kozlowski wrote:
> 2015-12-07 18:43 GMT+09:00 Arnd Bergmann :
> > On Monday 07 December 2015 18:38:44 Krzysztof Kozlowski wrote:
> >> On 07.12.2015 18:14, Arnd Bergmann wrote:
> >> > On Monday 07 December 2015 09:59:54 Krzysztof Kozlowski wrote:
> >> >> For Odroid XU3-family enable the:
> >> >>  - PWM fan (to control the CPU fan using thermal subsystem),
> >> >>  - TI INA231 sensors (provide power measurements of big.LITTLE cores,
> >> >>DRAM and GPU),
> >> >>  - Samsung sound (for Odroid XU3 and Snow as well).
> >> >>
> >> >> Signed-off-by: Krzysztof Kozlowski 
> >> >>
> >> >
> >> > Looks good. Do you have a samsung/defconfig branch already that you
> >> > can put this into, or should be pick it up into arm-soc directly?
> >> >
> >> > My preference is the former, but it would be a bit silly if that
> >> > is the only samsung defconfig change we need.
> >>
> >> I had a couple of defconfig patches in my queue but I sent them last
> >> week to Kukjin in pull request. He didn't pull it yet. Maybe he could
> >> apply this patch after pulling?
> >>
> >> Anyway we can wait for a few days to sort it out. If I don't have
> >> another defconfig patches then I will remind myself with applying it to
> >> arm-soc.
> >>
> >
> > Ok, sounds good.
> 
> +Cc a...@kernel.org,
> 
> I don't have any other defconfig changes in my queue, except of course
> stuff which I sent in pull request. I mean the request sent initially
> to Kukjin but now redirected with his ack to you guys.
> 
> If you don't mind, please apply this patch directly (with Javier's 
> reviewed-by).

Happy to apply, but can you please resend it to us (in patch format is fine)
since I just get this email from the thread in the arm@ folder...


-Olof
--
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

Re: [GIT PULL 9/9] ARM: EXYNOS: Defconfig for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:46AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> This may conflict with other arm-soc updates...
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-defconfig-4.5
> 
> for you to fetch changes up to 00a5e81fff2d81c3b1bf45712d3a12c905bc7c66:
> 
>   ARM: exynos_defconfig: Set recommended options for systemd (2015-12-01 
> 08:28:44 +0900)

Merged into next/defconfig.

Thanks!


-Olof
--
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

Re: [GIT PULL 1/9] ARM: EXYNOS: dts: Syscon dependency for v4.5

[Olof Johansson]

On Wed, Dec 02, 2015 at 10:39:38AM +0900, Krzysztof Kozlowski wrote:
> Hi Kukjin,
> 
> The DT changes are needed before switching to syscon-based reboot
> and power off method.
> 
> Best regards,
> Krzysztof
> 
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-dt-syscon-restart-4.5
> 
> for you to fetch changes up to 35135f4b95f03be7ebbf31221ce738f1ec0faa02:
> 
>   ARM: dts: Add syscon-{reboot, poweroff} nodes for exynos5410 (2015-11-20 
> 15:58:44 +0900)

Thanks, merged into next/dt.


-Olof
--
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

Re: [GIT PULL 4/5] Late Samsung driver updates for v4.4

[Olof Johansson]

On Wed, Oct 28, 2015 at 04:37:23PM +0900, Krzysztof Kozlowski wrote:
> On 24.10.2015 06:26, Kukjin Kim wrote:
> > The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> > 
> >   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/samsung-driver
> > 
> > for you to fetch changes up to c612d5a7785b307df96938d590c3a1edfb624ccf:
> > 
> >   cpufreq: s5pv210: remove superfluous CONFIG_PM ifdefs (2015-10-24
> > 04:34:50 +0900)
> > 
> > 
> > Samsung driver udpates for v4.4
> > 
> > - add support for exynos SROM controller DT based driver
> >   (drivers/soc/samsung/exynos-srom.c)
> >   : Since the exynos SROM registers are used during Suspend to RAM
> > so the exynos SROM driver handles the S2R and then we can remove
> > static mapping for SROM registers.
> >   : Pankaj tested boot and S2R functionality on Peach-Pi chromebook
> >   : Pavel tested on SMDK5410 board
> >   : Krzysztof tested on Trats2 (exynos4412) board
> > - update Maintainer entry accordingly
> > - remove superfluous CONFIG_PM ifdefs with Viresh's ack
> > 
> > 
> > Bartlomiej Zolnierkiewicz (1):
> >   cpufreq: s5pv210: remove superfluous CONFIG_PM ifdefs
> > 
> > Pankaj Dubey (8):
> >   ARM: EXYNOS: remove unused static mapping of CMU for exynos5
> >   ARM: EXYNOS: code cleanup in map.h
> >   dt-bindings: add exynos-srom device tree binding
> >   ARM: dts: add SROM device node for exynos4
> >   ARM: dts: add SROM device node for exynos5
> 
> Hi Olof and Kukjin,
> 
> I see that this pull request was not pulled yet. (Un)Fortunately I
> spotted one mistake in DTS changes above - the length of mapped region
> is too small by one word. This does not produce any visible effect but
> actually is wrong because driver will read from unmapped memory.

Yeah, I started looking now at why I didn't merge it since I had just not
touched it nor replied to it.

It looks like it contains an slight jumble of patches. It modifies DT
contents, which we always ask to get in the dt branch.

Please resend after -rc1 and we'll merge this for 4.5.


Thanks,


-Olof
--
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

Re: [GIT PULL 1/5] Late Samsung DT updates for v4.4

[Olof Johansson]

On Sat, Oct 24, 2015 at 06:18:06AM +0900, Kukjin Kim wrote:
> Hi Arnd, Olof, Kevin
> 
> Here is late pull-request for v4.4, please pull.
> 
> If any problems, please kindly let me know.
> See you in Seoul next week ;-)
> 
> Thanks,
> Kukjin
> 
> 
> The following changes since commit df829b06f0079165d9dc7719af8f8a7da852fe51:
> 
>   ARM: dts: Use GPIO constants for flags cells in exynos5440 boards
> (2015-10-08 07:39:58 +0900)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-dt-2
> 
> for you to fetch changes up to d6b9aea67f40e138e972b17c7c658bc3c8ac2459:
> 
>   MAINTAINERS: Add documentation and dt-bindings for exynos stuff
> (2015-10-24 05:07:26 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 2/5] Late Samsung DT64 update for v4.4

[Olof Johansson]

On Sat, Oct 24, 2015 at 06:21:39AM +0900, Kukjin Kim wrote:
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-dt64
> 
> for you to fetch changes up to c60ce7fe82c46d9480b85858828e3042dfe6c9bf:
> 
>   arm64: dts: Add BUS1 instance pinctrl support for exynos7 (2015-10-08
> 07:18:33 +0900)

Merged, thanks.


-Olof

--
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

Re: [GIT PULL 3/5] Late Samsung SoC updates for v4.4

[Olof Johansson]

On Sat, Oct 24, 2015 at 06:23:32AM +0900, Kukjin Kim wrote:
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-soc
> 
> for you to fetch changes up to 97d5c7a77e39ab96a2a6137de0e35dd6e3f38325:
> 
>   Documentation: EXYNOS: Update bootloader interface on exynos542x
> (2015-10-24 04:43:31 +0900)
> 
> 
> Samsung SoC updates for v4.4
> 
> - use PWM lookup table with pwm_add_table() for the following boards
>   : s3c24xx h1940 and rx1950
>   : s3c64xx smdk6410, crag6410, hmt and smartq
> - document: update bootloader interface on exynos542x

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 5/5] Late Samsung defconfig updates for v4.4

[Olof Johansson]

On Sat, Oct 24, 2015 at 06:27:56AM +0900, Kukjin Kim wrote:
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/samsung-defconfig
> 
> for you to fetch changes up to f0864f843f0249f3e16e1a9af7152d7aa8070b10:
> 
>   ARM: multi_v7_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
> (2015-10-24 04:13:12 +0900)

Merged, thanks.


-Olof

--
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

Re: [PATCH 1/4] sysfs: Support is_visible() on binary attributes

[Olof Johansson]

On Sun, Oct 04, 2015 at 07:33:34PM +0100, Greg KH wrote:
> On Mon, Sep 21, 2015 at 10:38:20AM -0300, Emilio L?pez wrote:
> > According to the sysfs header file:
> > 
> > "The returned value will replace static permissions defined in
> >  struct attribute or struct bin_attribute."
> > 
> > but this isn't the case, as is_visible is only called on struct attribute
> > only. This patch introduces a new is_bin_visible() function to implement
> > the same functionality for binary attributes, and updates documentation
> > accordingly.
> > 
> > Note that to keep functionality and code similar to that of normal
> > attributes, the mode is now checked as well to ensure it contains only
> > read/write permissions or SYSFS_PREALLOC.
> > 
> > Reviewed-by: Guenter Roeck 
> > Signed-off-by: Emilio L?pez 
> 
> As this should probably go through the "platform drivers" maintainer,
> I'll just give you this:
> 
> Acked-by: Greg Kroah-Hartman 
> 
> So it can go through their tree and not require me to just take this
> one.

Thanks, applied to the chrome-platform tree now.


-Olof
--
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

Re: [PATCH v3 3/4] platform/chrome: Support reading/writing the vboot context

[Olof Johansson]

On Mon, Sep 21, 2015 at 10:38:22AM -0300, Emilio L??pez wrote:
> Some EC implementations include a small nvram space used to store
> verified boot context data. This patch offers a way to expose this
> data to userspace.
> 
> Reviewed-by: Javier Martinez Canillas 
> Signed-off-by: Emilio L??pez 

Applied, thanks!


-Olof
--
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

Re: [PATCH 00/18] ARM: use const and __initconst for smp_operations

[Olof Johansson]

On Mon, Aug 24, 2015 at 2:21 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
 On Mon, Aug 24, 2015 at 02:12:06PM -0700, Olof Johansson wrote:
 Easiest of all would probably be to get the sub-arch patches into one
 release, then switch the prototypes and function definitions in the
 next. If you switch prototypes first you'll get a bunch of warnings,
 right?

 Wrong way around. :)

 If you change the sub-arches to declare the smp operations as const,
 and try and pass them into a function which doesn't take a const-pointer,
 you'll get a warning.  The core bits need to go in first before the
 sub-arch patches.

Ah yes, my bad.

 I think the series has limited value - it allows us to (a) check that a
 small quantity of code doesn't write to these things, and (b) allows us
 to move the SMP operations structure from __initdata to __initconstdata.
 It's still going to end up in the init region which is read/write in any
 case, and still gets thrown away.

 Given where we are, I don't think we need to rush this in during the
 last week before the merge window opens, even though it's trivial.

Agreed. So if you pick it up for 4.4, we'll get the rest for 4.5.


-Olof
--
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

Re: [PATCH 00/18] ARM: use const and __initconst for smp_operations

[Olof Johansson]

On Sun, Aug 23, 2015 at 9:36 PM, Masahiro Yamada
yamada.masah...@socionext.com wrote:

 Currently, SoC code can not add const qualifier to smp_operations
 structures although they are never over-written.

 01/18 and 02/18 add small changes to the ARM core to fix that.
 The rest of this series replace __initdata with const ... __initconst
 for each of SoC code.

 I split this series into per-SoC so that each sub-arch maintainer
 can easily give their Acked-by.  (Is this better?)

When you split, chances are each sub-arch maintainer will apply
instead of ack. If that's what you want, that's fine.

 Russell, Olof, and Arnd:

 How should this series be applied (if it looks good)?
 The first two are ARM-tree wide and looks like in the field of Russell.
 The rest are highly SoC-related.

Easiest of all would probably be to get the sub-arch patches into one
release, then switch the prototypes and function definitions in the
next. If you switch prototypes first you'll get a bunch of warnings,
right?


-Olof
--
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

Re: [GIT PULL v2 0/5] Samsung updates for v4.3

[Olof Johansson]

On Fri, Aug 14, 2015 at 03:42:31AM +0900, Kukjin Kim wrote:
 Hello Arnd, Olof, Kevin
 
 Here is re-spin of pull request for Samsung stuff for v4.3 as per Olof's
 suggestion.
 
 Most of this pull-requests are to switch to support generic cpufreq
 driver for exynos3250, 4210, 4412 and 5250 and several exynos dt updates.
 
 Note as I commented in each tag, each pull-request(signed tag) has a
 dependency with each other, so please keep the ordering in this time.
 
 1) tags/samsung-clk-driver
 2) tags/samsung-late-dt
 3) tags/samsung-soc
 4) tags/samsung-late-cpufreq-driver
 5) tags/samsung-defconfig-new
 
 If any problems, please kindly let me know.

That ordering is awkward for us. driver-dt-soc-driver-defconfig is
not the way we do it.

I'll merge them into a next/late branch together, and we might or might not
send it in this merge window depending on how it goes.

The lesson to learn here (for us and you) is that if there is complex
contents, getting it sent in very early is important: rc2/rc3 is
ideal. We're likely to be less tolerant of messy dependencies as we start
to approach -rc6 and already have a lot of things merged up. We might
also have locked into ordering between branches by then that doesn't
match what you've used.


-Olof

--
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

Re: [GIT PULL v2 1/5] Samsung clk driver updates for v4.3

[Olof Johansson]

On Fri, Aug 14, 2015 at 03:48:37AM +0900, Kukjin Kim wrote:
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-clk-driver
 
 for you to fetch changes up to cd6aceef028afc3fa216e3e7bc94cc31632cad43:
 
   clk: exynos4x12: add cpu clock configuration data and instantiate cpu
 clock (2015-08-14 02:00:43 +0900)
 
 
 Samsung clk driver updates for v4.3
 
 - add cpu clock configuration data and instantiate cpu clock
   for exynos3250, 4210, 4412 and 5250 SoCs to support Samsung
   specific cpu-clock type
 
 * Note this branch has been provided to clk tree as a topic branch

Merged into next/late.


-Olof

--
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

Re: [GIT PULL v2 3/5] Samsung SoC updates for v4.3

[Olof Johansson]

On Fri, Aug 14, 2015 at 03:51:40AM +0900, Kukjin Kim wrote:
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-soc
 
 for you to fetch changes up to bdd2648e50508cbb2eb6d1c303e4d2d6d7505400:
 
   ARM: EXYNOS: switch to using generic cpufreq driver for exynos4x12
 (2015-08-14 03:07:10 +0900)
 

Merged into next/late.


-Olof

--
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

Re: [GIT PULL v2 2/5] Samsung 2nd DT updates for v4.3

[Olof Johansson]

On Fri, Aug 14, 2015 at 03:50:30AM +0900, Kukjin Kim wrote:
 The following changes since commit 5e080b078fa1f929d9aa5586985d5e7c0739d207:
 
   ARM: dts: Extend exynos5420-pinctrl nodes using labels instead of
 paths (2015-07-21 13:01:23 +0900)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-late-dt
 
 for you to fetch changes up to ba032795463bfc461937dbde7a345103a47f969b:
 
   ARM: dts: add iommu property to JPEG device for exynos4 (2015-08-14
 02:30:58 +0900)
 
 
 Samsung 2nd DT updates for v4.3
 
 - for exynos3250, 4212, 4412 and 5250
   : add CPU OPP and regulator supply property
 
 - for exynos3250
   : add CPU cooling binding for exynos3250 boards
 
 - for exynos4 SoCs
   : add iommu property to JPEG device
 
 - for exynos4412-odroidu3
   : enable SPI1
 
 - for exynos5250-snow
   : add SPI CS
 
 - for exynos5422
   : add exynos5422-cpus.dtsi to correct cpu order
 
 * Note this branch is depending on tags/samsung-clk-driver

It's not depending on it, it contains it -- which is what's required here or
bisectability would be broken.

Merged into next/late.


-Olof

--
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

Re: [GIT PULL v2 5/5] Samsung defconfig updates for v4.3

[Olof Johansson]

On Fri, Aug 14, 2015 at 03:53:51AM +0900, Kukjin Kim wrote:
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-defconfig-new
 
 for you to fetch changes up to 2b347c6494cbc6bfdc81b5201b8aa34afb2c3500:
 
   ARM: exynos_defconfig: Enable cpufreq-dt driver (2015-08-12 08:17:31
 +0900)

Merged into next/late.


-Olof

--
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

Re: [GIT PULL] Samsung mach fixes for 4.2

[Olof Johansson]

On Mon, Aug 10, 2015 at 11:04:25AM +0900, Kukjin Kim wrote:
 Hi arm-soc guys,
 
 Can you please pull this into arm-soc fixes for v4.2 directly?
 I don't have other samsung fixes in my tree at this moment.
 
 Thanks,
 Kukjin
 
 Krzysztof Kozlowski wrote:
  
  Dear Kukjin,
  
  Please find latest two fixes for v4.2 cycle. You can find more detailed
  description with the tag.
  
  Best regards,
  Krzysztof
  
  
  The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
  
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
  
  are available in the git repository at:
  
https://github.com/krzk/linux.git tags/samsung-mach-fixes-4.2
  
  for you to fetch changes up to 3e9f798784b30293012682021d5a0352f78658b8:
  
ARM: EXYNOS: fix double of_node_put() on error path (2015-07-31 10:12:17 
  +0900)

Merged, thanks.


-Olof

--
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

Re: [GIT PULL 4/5] Samsung 2nd DT updates for v4.3

[Olof Johansson]

On Tue, Aug 04, 2015 at 04:29:25PM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin
 
 This 2nd DT update branch is based tags/samsung-dt-1 +
 v4.3-topic/clk-samsung branch because of dependency to support generic
 cpufreq driver. Please pull.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit e4a39d904c3c3e4855287b7325306289ff044b06:
 
   Merge branch 'v4.3-topic/clk-samsung' into v4.3-next/dt-samsung-2
 (2015-07-24 12:54:00 +0900)
 
 are available in the git repository at:
 
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-2

clk: exynos5250: add cpu clock configuration data and instantiate cpu
clock is applied twice, once to your own branch, and once merged in
from Mike's branch. That doesn't look right.

Can you please respin? Thanks.


Thanks,

-Olof
--
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

Re: [GIT PULL 2nd 2/4] Samsung DT 3rd updates for v4.3

[Olof Johansson]

On Thu, Aug 13, 2015 at 09:12:34AM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin
 
 This is based on tags/samsung-dt-2 and including exynos4 related clock
 changes to support cpufreq-dt driver for exynos4 SoCs. Note that I've
 created one more clk topic branch called v4.3-topic/clk-samsung-2 based
 on previous one has been merged by Mike into clock tree before but I'm
 not sure new one merged into clk tree that's why I've noted its merge in
 this signed tag.

Since this depends on the previous DT branch that I asked for a respin, please
do it all over and send a fresh pull request that we hopefully can include.

We normally ask that you don't queue up merge requests like these for that
reason: If there's need to redo an earlier branch there's a lot of work that
needs to be done on your side. Instead, please wait until previous pull request
has been merged before you send the next one. Thanks!


-Olof

--
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

Re: [GIT PULL 2nd 3/4] Samsung driver 2nd updates for v4.3

[Olof Johansson]

On Thu, Aug 13, 2015 at 09:12:59AM +0900, Kukjin Kim wrote:
 Hi,
 
 I've created the signed tag based on previous tags/samsung-driver so you
 can see several merge in there. To support cpufreq-dt driver requires
 clk/cpufreq/exynos changes together and clk/cpufreq maintainers are
 aware of this changes. And we can remove exynos cpufreq driver at last.
 
 Note this drivers update is including previous dependencies and if
 you're OK, please pull.

Again, this needs to be revisited.

Please try to keep the dependency only driver-dt if you can,
and we can merge drivers before DT this release cycle. If you do
driver-dt-driver-dt like here then things get messy.


-Olof

--
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

Re: [GIT PULL 5/5] Samsung driver updates for v4.3

[Olof Johansson]

On Tue, Aug 04, 2015 at 04:30:18PM +0900, Kukjin Kim wrote:
 Hi,
 
 This branch is including to support generic cpufreq driver in
 mach-exynos dir. for exynos3250 and exynos5250 even the tag name is
 driver. Because it is depending on clk and cpufreq changes which acked
 by regarding maintainers, Mike and Viresh.
 
 Please pull and if any problems, please kindly let me know.

This now needs to be respun too, apparantly, since it includes dt2.


-Olof

--
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

Re: [GIT PULL 1/5] Samsung non-critical-fixes for v4.3

[Olof Johansson]

On Tue, Aug 04, 2015 at 04:28:21PM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin,
 
 Here is Samsung non-critical-fixes for v4.3.
 Please pull.
 
 Thanks,
 Kukjin
 
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-non-critical-1


Merged, thanks.


-Olof
--
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

Re: [GIT PULL 2/5] Samsung cleanup for v4.3

[Olof Johansson]

On Tue, Aug 04, 2015 at 04:28:47PM +0900, Kukjin Kim wrote:
 Hi,
 
 Please pull Samsung cleanup for v4.3.
 Note I'm going to cleanup non-used definitions based on this soon.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-cleanup
 
 for you to fetch changes up to d306d08f07183fe1504257101b25b5b33d77bae9:
 
   ARM: SAMSUNG: remove keypad-core header in plat-samsung (2015-07-30
 02:02:06 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 3/5] Samsung DT updates for v4.3

[Olof Johansson]

On Tue, Aug 04, 2015 at 04:29:06PM +0900, Kukjin Kim wrote:
 Hi,
 
 Please pull Samsung DT updates for v4.3.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-1
 
 for you to fetch changes up to 5e080b078fa1f929d9aa5586985d5e7c0739d207:
 
   ARM: dts: Extend exynos5420-pinctrl nodes using labels instead of
 paths (2015-07-21 13:01:23 +0900)

Merged, thanks.


-Olof
--
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

Re: [PATCH v3] ARM: kill off set_irq_flags usage

[Olof Johansson]

On Mon, Jul 27, 2015 at 03:55:13PM -0500, Rob Herring wrote:
 set_irq_flags is ARM specific with custom flags which have genirq
 equivalents. Convert drivers to use the genirq interfaces directly, so we
 can kill off set_irq_flags. The translation of flags is as follows:
 
 IRQF_VALID - !IRQ_NOREQUEST
 IRQF_PROBE - !IRQ_NOPROBE
 IRQF_NOAUTOEN - IRQ_NOAUTOEN
 
 For IRQs managed by an irqdomain, the irqdomain core code handles clearing
 and setting IRQ_NOREQUEST already, so there is no need to do this in
 .map() functions and we can simply remove the set_irq_flags calls. Some
 users also modify IRQ_NOPROBE and this has been maintained although it
 is not clear that is really needed. There appears to be a great deal of
 blind copy and paste of this code.
 
 Signed-off-by: Rob Herring r...@kernel.org
 Cc: Russell King li...@arm.linux.org.uk
 Cc: Sekhar Nori nsek...@ti.com
 Cc: Kevin Hilman khil...@deeprootsystems.com
 Cc: Jason Cooper ja...@lakedaemon.net
 Cc: Andrew Lunn and...@lunn.ch
 Cc: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
 Cc: Gregory Clement gregory.clem...@free-electrons.com
 Acked-by: Hans Ulli Kroll ulli.kr...@googlemail.com
 Acked-by: Shawn Guo shawn...@kernel.org
 Cc: Sascha Hauer ker...@pengutronix.de
 Cc: Imre Kaloz ka...@openwrt.org
 Acked-by: Krzysztof Halasa khal...@piap.pl
 Cc: Greg Ungerer g...@uclinux.org
 Cc: Roland Stigge sti...@antcom.de
 Cc: Tony Lindgren t...@atomide.com
 Cc: Daniel Mack dan...@zonque.org
 Cc: Haojian Zhuang haojian.zhu...@gmail.com
 Cc: Robert Jarzmik robert.jarz...@free.fr
 Cc: Simtec Linux Team li...@simtec.co.uk
 Cc: Kukjin Kim kg...@kernel.org
 Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
 Acked-by: Wan ZongShun mcuos@gmail.com
 Cc: linux-arm-ker...@lists.infradead.org
 Cc: linux-o...@vger.kernel.org
 Cc: linux-samsung-soc@vger.kernel.org
 Tested-by: Kevin Hilman khil...@linaro.org
 ---
 Thomas asked that this be merged thru subsystem trees instead of arm-soc,
 so please apply just this patch to your tree.

this be merged through subsystem trees + please apply just this
patch. I'm going to assume that the first this means a patch series. So
I've applied this to next/cleanup, let me know if this was in error and
should be removed, it's easy to drop at this time.


-Olof
--
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

Re: [PATCH 1/3] platform/chrome: Don't make CHROME_PLATFORMS depends on X86 || ARM

[Olof Johansson]

On Thu, Jun 25, 2015 at 02:20:42AM +0200, Javier Martinez Canillas wrote:
 The Chrome platform support depends on X86 || ARM because there are
 only Chromebooks using those architectures. But only some drivers
 depend on a given architecture, and the ones that do already have
 a dependency on their specific Kconfig symbol entries.
 
 An option is to also make CHROME_PLATFORMS depends on || COMPILE_TEST
 but is more future proof to remove the dependency and let the drivers
 be built in all architectures if possible to have more build coverage.
 
 Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk

Acked-by: Olof Johansson o...@lixom.net


-Olof
--
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

Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM

[Olof Johansson]

On Tue, Jul 21, 2015 at 6:13 PM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
 [Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015 
 (Thu 10:44) Javier Martinez Canillas wrote:

 Hello Lee,

 On 06/25/2015 10:38 AM, Lee Jones wrote:
  On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
 
  A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
 
  (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct 
  dependencies (X86 || ARM)
 
  This happened because CHROME_PLATFORMS had a dependency on X86 || ARM but
  that dependency was removed since there isn't a reason why the option can
  not be selected on other architectures. So now the above warning will not
  happen and the MFD_CROS_EC dependency can be removed since is not needed.
 
  Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
  ---
 
   drivers/mfd/Kconfig | 1 -
   1 file changed, 1 deletion(-)
 
  Applied for v4.3, thanks.
 

 Thanks a lot.

 Olof,

 Could you please ack patch 1/3 so Lee can pick it through the mfd tree?
 Since both patches 1/3 and 2/3 are needed to fix the build warning for
 !X86 and !ARM architectures.

 Hi all,

 Wondering if this fell through the cracks.  It used to be just a
 linux-next issue, but now it is a mainline issue.  This _really_ should
 be fixed and fed to Linus ASAP.  Ideally it should have been fixed before
 going to mainline as it was reported in plenty of time ; that is the
 whole point of linux-next to fix unanticipated fallout and revise.

Yep, agreed. I've been a bit removed from upstream work for the last
couple of months (getting back to it now), so I've been bad at
following up on this.

Acks sent now, Lee, please pick up for 4.2 if you don't mind.


-Olof
--
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

Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM

[Olof Johansson]

On Thu, Jun 25, 2015 at 10:44:28AM +0200, Javier Martinez Canillas wrote:
 Hello Lee,
 
 On 06/25/2015 10:38 AM, Lee Jones wrote:
  On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
  
  A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
  
  (MFD_CROS_EC) selects CHROME_PLATFORMS which has unmet direct dependencies 
  (X86 || ARM)
  
  This happened because CHROME_PLATFORMS had a dependency on X86 || ARM but
  that dependency was removed since there isn't a reason why the option can
  not be selected on other architectures. So now the above warning will not
  happen and the MFD_CROS_EC dependency can be removed since is not needed.
  
  Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
  ---
  
   drivers/mfd/Kconfig | 1 -
   1 file changed, 1 deletion(-)
  
  Applied for v4.3, thanks.
  
 
 Thanks a lot.
 
 Olof,
 
 Could you please ack patch 1/3 so Lee can pick it through the mfd tree?
 Since both patches 1/3 and 2/3 are needed to fix the build warning for
 !X86 and !ARM architectures.

Yep, done.

-Olof
--
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

Re: [GIT PULL] Samsung 1st fixes for v4.2

[Olof Johansson]

Hi Kukjin,

On Tue, Jul 21, 2015 at 12:40:04PM +0900, Kukjin Kim wrote:
 Hi,
 
 Please pull samsung fixes for v4.2.
 
 Thanks,
 Kukjin
 
 The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
 
   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-fixes-1
 
 for you to fetch changes up to 300bde79f3d86b1af6fcde7b7b2439ecffccbff4:
 
   ARM: dts: add CPU OPP and regulator supply property for exynos4210
 (2015-07-21 12:32:29 +0900)

Was there a reason you rebased Krzystztof's branch? The contents is identical.

In cases like those, feel free to just forward the pull request to us
and we can do it directly. If you have more patches you want to add into
the same fixes branch then you can just merge his in and apply yours on
top. That's for example how Tony Lindgren tends to handle OMAP -- he'll
forward a pull request from Paul Walmsley if that's the only contents
he has.

Anyway, merged.


-Olof
--
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

Re: [PATCH 2/9] ARM: multi_v7_defconfig: Enable max77802 regulator, rtc and clock drivers

[Olof Johansson]

On Thu, Jul 16, 2015 at 09:42:47AM +0900, Krzysztof Kozlowski wrote:
 On 16.07.2015 00:38, Javier Martinez Canillas wrote:
  Hello,
  
  On Thu, May 14, 2015 at 5:40 PM, Javier Martinez Canillas
  javier.marti...@collabora.co.uk wrote:
  The Maxim max77802 Power Management IC is used on many Exynos machines.
  Besides a bunch of regulators, this chip has a Real-Time-Clock (RTC)
  and 2-channel 32kHz clock outputs.
 
  Enable the kernel config options to have the drivers for these devices
  built as a module.
 
  Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
  ---
   arch/arm/configs/multi_v7_defconfig | 3 +++
   1 file changed, 3 insertions(+)
 
  diff --git a/arch/arm/configs/multi_v7_defconfig 
  b/arch/arm/configs/multi_v7_defconfig
  index 2349584b6e08..080120fe5580 100644
  --- a/arch/arm/configs/multi_v7_defconfig
  +++ b/arch/arm/configs/multi_v7_defconfig
  @@ -373,6 +373,7 @@ CONFIG_POWER_RESET_SYSCON=y
   CONFIG_REGULATOR_MAX8907=y
   CONFIG_REGULATOR_MAX8973=y
   CONFIG_REGULATOR_MAX77686=y
  +CONFIG_REGULATOR_MAX77802=m
  
  I noticed that the version that landed in 4.2-rc1 as commit
  f3caa529c6f5 (ARM: multi_v7_defconfig: Enable max77802 regulator, rtc
  and clock drivers) doesn't include this symbol. I guess it was caused
  by a wrong resolved conflict? I'll post a patch to enable the
  regulator again.
 
 As you can see in mentioned mainline commit Kukjin removed it manually:
 [kg...@kernel.org: removing useless REGULATOR_MAX77802 config]
 
 I wonder why?

Seems odd. exynos_defconfig still enables it.

Javier or Krzysztof, please send an incremental fix to enable and I'll pick
it up as a fix.


-Olof
--
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

Re: [PATCH 2/9] ARM: multi_v7_defconfig: Enable max77802 regulator, rtc and clock drivers

[Olof Johansson]

Hi,


On Fri, Jul 17, 2015 at 11:47 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
 Hello Olof,

 On Fri, Jul 17, 2015 at 6:49 PM, Olof Johansson o...@lixom.net wrote:
 On Thu, Jul 16, 2015 at 09:42:47AM +0900, Krzysztof Kozlowski wrote:
 On 16.07.2015 00:38, Javier Martinez Canillas wrote:
  Hello,
 
  On Thu, May 14, 2015 at 5:40 PM, Javier Martinez Canillas
  javier.marti...@collabora.co.uk wrote:
  The Maxim max77802 Power Management IC is used on many Exynos machines.
  Besides a bunch of regulators, this chip has a Real-Time-Clock (RTC)
  and 2-channel 32kHz clock outputs.
 
  Enable the kernel config options to have the drivers for these devices
  built as a module.
 
  Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
  ---
   arch/arm/configs/multi_v7_defconfig | 3 +++
   1 file changed, 3 insertions(+)
 
  diff --git a/arch/arm/configs/multi_v7_defconfig 
  b/arch/arm/configs/multi_v7_defconfig
  index 2349584b6e08..080120fe5580 100644
  --- a/arch/arm/configs/multi_v7_defconfig
  +++ b/arch/arm/configs/multi_v7_defconfig
  @@ -373,6 +373,7 @@ CONFIG_POWER_RESET_SYSCON=y
   CONFIG_REGULATOR_MAX8907=y
   CONFIG_REGULATOR_MAX8973=y
   CONFIG_REGULATOR_MAX77686=y
  +CONFIG_REGULATOR_MAX77802=m
 
  I noticed that the version that landed in 4.2-rc1 as commit
  f3caa529c6f5 (ARM: multi_v7_defconfig: Enable max77802 regulator, rtc
  and clock drivers) doesn't include this symbol. I guess it was caused
  by a wrong resolved conflict? I'll post a patch to enable the
  regulator again.

 As you can see in mentioned mainline commit Kukjin removed it manually:
 [kg...@kernel.org: removing useless REGULATOR_MAX77802 config]

 I wonder why?

 Seems odd. exynos_defconfig still enables it.


 Yeah since it is needed for at least the Exynos5420 Peach Pit and
 Exynos5800 Peach Pi Chromebooks that use this PMIC.

 Javier or Krzysztof, please send an incremental fix to enable and I'll pick
 it up as a fix.


 I already posted an incremental patch [0] and Krzysztof is pushing it
 through Kukjin for 4.3 [1].

 I guess that's OK and there is no need to add it as a fix for the 4.2
 -rc cycle since this is not really a regression. I mean, the max77802
 regulator driver was never enabled for multi_v7_defconfig before.

Yeah, I came across those emails a little further down. :-) It's all
good, we'll see it come in later.


-Olof
--
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

Re: [PATCH v6 6/8] mfd: cros_ec: Support multiple EC in a system

[Olof Johansson]

On Fri, Jun 05, 2015 at 11:17:30AM +0100, Lee Jones wrote:
 On Thu, 04 Jun 2015, Javier Martinez Canillas wrote:
 
  From: Gwendal Grignou gwen...@chromium.org
  
  Chromebooks can have more than one Embedded Controller so the
  cros_ec device id has to be incremented for each EC registered.
  
  Add a new structure to represent multiple EC as different char
  devices (e.g: /dev/cros_ec, /dev/cros_pd). It connects to
  cros_ec_device and allows sysfs inferface for cros_pd.
  
  Also reduce number of allocated objects, make chromeos sysfs
  class object a static and add refcounting to prevent object
  deletion while command is in progress.
  
  Signed-off-by: Gwendal Grignou gwen...@chromium.org
  Reviewed-by: Dmitry Torokhov d...@chromium.org
  Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
  Tested-by: Heiko Stuebner he...@sntech.de
  ---
  
  Changes since v5:
   - Don't allow to change the device name from DT. Suggested by Lee Jones.
   - Expand error messages in case of mfd_add_devices() failure.
 Suggested by Lee Jones.
  
  Changes since v4:
   - Use cros-ec-name DT property instead of devname. Suggested by Lee Jones.
   - Pass PLATFORM_DEVID_AUTO directly to mfd_add_devices().
 Suggested by Lee Jones.
   - Add Heiko Stuebner tested-by tag.
   - Fix get_version by passing the cmd_offset to EC_CMD_GET_VERSION.
  
  Changes since v3:
   - Add defines for the EC and PD index constants.
   - Remove cros_ec_dev_register() and declare the mfd_cells as static 
  structs.
 Suggested by Lee Jones.
   - Add a new line before the return statement in cros_ec_dev_register().
 Suggested by Lee Jones.
  
  Changes since v2: None
  
  Changes since v1:
- Squash patch that adds support to represent EC's as different
  char devices (e.g: /dev/cros_ec, /dev/cros_pd):
  https://chromium-review.googlesource.com/#/c/217297/
  Suggested by Gwendal Grignou
- Use cros_ec instead of cros-ec in the subject line to be consistent.
  Suggested by Gwendal Grignou
  ---
   drivers/input/keyboard/cros_ec_keyb.c  |   2 +-
   drivers/mfd/cros_ec.c  |  52 ++--
   drivers/mfd/cros_ec_i2c.c  |   1 -
   drivers/mfd/cros_ec_spi.c  |   1 -
   drivers/platform/chrome/cros_ec_dev.c  | 130 
  -
   drivers/platform/chrome/cros_ec_dev.h  |   7 --
   drivers/platform/chrome/cros_ec_lightbar.c |  75 +
   drivers/platform/chrome/cros_ec_lpc.c  |   1 -
   drivers/platform/chrome/cros_ec_sysfs.c|  48 +--
   include/linux/mfd/cros_ec.h|  44 --
   10 files changed, 234 insertions(+), 127 deletions(-)
 
 For my own reference:
   Acked-by: Lee Jones lee.jo...@linaro.org
 
 Let me know when you have all the appropriate Acks and I'll apply the
 set.

Whole series:

Acked-by: Olof Johansson o...@lixom.net

I'm OK with this going through the mfd tree, since there's nothing queued up
for chrome-platform that this would conflict with.


-Olof
--
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

Re: [GIT PULL 5/5] Samsung mach updates for v4.1

[Olof Johansson]

On Thu, Apr 02, 2015 at 03:17:33AM +0900, Kukjin Kim wrote:
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-updates
 
 for you to fetch changes up to bd0d888c4f7f125b7c7168f51039142150d9d1cc:
 
   ARM: EXYNOS: allow cpuidle driver usage on Exynos3250 SoC (2015-03-27
 02:35:52 +0900)

Merged.


-Olof
--
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

Re: [GIT PULL] Samsung 2nd fixes for v4.0

[Olof Johansson]

On Thu, Apr 02, 2015 at 02:23:55AM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin,
 
 Here is 2nd Samsung fixes for v4.0 and it fixes arm allmodconfig build
 breakage and exynos5250-spring lid, power-pin and mmc nodes dt updates.
 
 Please pull and sorry for pretty late pull-request for v4.0.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-fixes-2
 
 for you to fetch changes up to cfdda3535f87e752780ca18a57d13db58f6a6913:
 
   ARM: EXYNOS: Fix build breakage cpuidle on !SMP (2015-03-18 03:26:11
 +0900)

Merged.


-Olof
--
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

Re: [GIT PULL 1/5] Samsung non-critical-fixes for v4.1

[Olof Johansson]

On Thu, Apr 02, 2015 at 03:15:54AM +0900, Kukjin Kim wrote:
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-fixes-v4.1
 
 for you to fetch changes up to a11176e65b8727158bc355ca0cb00bf70cd69e48:
 
   ARM: S3C24XX: avoid a Kconfig warning (2015-02-27 05:50:25 +0900)
 
 
 Samsung non-critical fixes for v4.1
 
 - mostly trivial build fixes with random configurations
   from Arnd Bergmann
 
   for s3c24xx:
   avoid a Kconfig warning and fix header file inclusions,
   and fix building without PM_SLEEP and use SAMSUNG_WAKEMASK
 
   for s3c64xx:
   fix __initdata section mismatch and add I2C dependencies,
   and fix building with PM_SLEEP

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 4/5] Samsung arm64 DT updates for v4.1

[Olof Johansson]

On Thu, Apr 02, 2015 at 03:16:55AM +0900, Kukjin Kim wrote:
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-64
 
 for you to fetch changes up to 423c716151e254e42650ad78b30c2cd782c6f654:
 
   arm64: dts: Add thermal-zones dt node for exynos5433 (2015-03-27
 02:13:43 +0900)
 
 
 Samsung arm64 DT updates for v4.1
 
 - add new SoC for arm64 based exynos5433 SoC
   : exynos5433 - Octa cores for big.LITTLE architecture
   (Quad Cortex-A57 big and Quad Cortex-A53 LITTLE cores)
 
   : added thermal-zones, TMU sensor and I2S dt nodes
   : added ADMA, RTC, ADC, PMU, SPI/PDMA and MSHC dt nodes
   : added pinctrl, HS-I2C, Serial and basic system dt nodes
 
 
 Chanwoo Choi (6):
   arm64: dts: Add dts files for 64-bit Exynos5433 SoC
   arm64: dts: Add SPI/PDMA dt node for exynos5433
   arm64: dts: Add PMU dt node for exynos5433
   arm64: dts: Add RTC and ADC dt node for exynos5433
   arm64: dts: Add TMU sensor dt node for exynos5433
   arm64: dts: Add thermal-zones dt node for exynos5433
 
 Inha Song (2):
   arm64: dts: Add ADMA dt node for exynos5433
   arm64: dts: Add I2S dt node for exynos5433
 
 Jaehoon Chung (1):
   arm64: dts: Add MSHC dt node for exynos5433
 
  .../devicetree/bindings/arm/samsung/pmu.txt|   1 +
  arch/arm64/boot/dts/exynos/exynos5433-pinctrl.dtsi | 698 +++
  .../dts/exynos/exynos5433-tmu-sensor-conf.dtsi |  22 +
  arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi | 231 +
  arch/arm64/boot/dts/exynos/exynos5433.dtsi | 931
 +
  5 files changed, 1883 insertions(+)
  create mode 100644 arch/arm64/boot/dts/exynos/exynos5433-pinctrl.dtsi
  create mode 100644
 arch/arm64/boot/dts/exynos/exynos5433-tmu-sensor-conf.dtsi
  create mode 100644 arch/arm64/boot/dts/exynos/exynos5433-tmu.dtsi
  create mode 100644 arch/arm64/boot/dts/exynos/exynos5433.dtsi

How do you even build these dts files? How did you test this branch before you
sent it to us?

Not merged.


-Olof
--
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

Re: [GIT PULL 2/5] Samsung defconfig udpates for v4.1

[Olof Johansson]

On Thu, Apr 02, 2015 at 03:16:22AM +0900, Kukjin Kim wrote:
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-defconfig
 
 for you to fetch changes up to bb84296ae52da844c9cab81e0197152a69f2f841:
 
   ARM: exynos_defconfig: Enable HDMI support (2015-03-27 02:00:09 +0900)
 
 
 Samsung defconfig updates for v4.1
 
 - update exynos-defconfig
   : enable HDMI, CPUidle, ChromeOS EC chardev driver
 and thermal emulation, Marvell WiFi-Ex, CPUfreq,
 and support for NFS rootfs
   : remove EXYNOS_THERMAL_CORE define
 and disable IOMMU support until support it

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 3/5] Samsung DT updates for v4.1

[Olof Johansson]

On Thu, Apr 02, 2015 at 03:16:38AM +0900, Kukjin Kim wrote:
 The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
 
   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt
 
 for you to fetch changes up to f27b907595fc586bce62b8a3dc421e89bb927250:
 
   ARM: dts: Fixed typo interrupt-cells for exynos5420 and exynos5250
 (2015-03-27 01:55:28 +0900)

Merged, thanks.


-Olof
--
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

Re: [PATCH v5 4/7] platform/chrome: Add Chrome OS EC userspace device interface

[Olof Johansson]

On Thu, Feb 26, 2015 at 1:08 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
 Hello Olof,

 Thanks a lot for your feedback.

 On 02/26/2015 02:13 AM, Gwendal Grignou wrote:
 Olof,

 I think the way Javier did it is fine, the 'major' of the ioctl is
 0xEC, from ':'.

 Gwendal.


 As Gwendal said, I deliberately changed the IOCTL mayor number to
 make it different in both kernels.

 downstream:

 #define CROS_EC_DEV_IOC  ':'
 #define CROS_EC_DEV_IOCXCMD_IOWR(':', 0, struct cros_ec_command)
 #define CROS_EC_DEV_IOCRDMEM   _IOWR(':', 1, struct cros_ec_readmem)

 mainline:

 #define CROS_EC_DEV_IOC   0xEC
 #define CROS_EC_DEV_IOCXCMD   _IOWR(CROS_EC_DEV_IOC, 0, struct 
 cros_ec_command)
 #define CROS_EC_DEV_IOCRDMEM  _IOWR(CROS_EC_DEV_IOC, 1, struct 
 cros_ec_readmem)

 I can also do what you suggested and keep ':' as the major and use 2/3
 as command numbers but I just think 0xEC is a much nicer major for the
 interface to talk with the Embedded Controller and it was available ;)

No, changing major is definitely sufficient and an acceptable way to
do it -- I had missed that you did so.

Thanks, Javier, Gwendal, I'll apply this today and push out. Gwendal
has been giving it a go on a machine here too so I'll check with him
before I push.


-Olof
--
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

Re: [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support

[Olof Johansson]

On Thu, Feb 26, 2015 at 3:35 PM, Gwendal Grignou gwen...@chromium.org wrote:
 Tested-by: Gwendal Grignou gwen...@chromium.org
 Reviewed-by: Gwendal Grignou gwen...@chromium.org

 Tested on a chromebook pixel with kernel 4.0.0-rc1 and ectool using
 the enclosed patch in chromiumos platform/ec tree.
 I checked the lightbar is working, check the calls with strace ectool
 ..., check the sysfs interface calls.


Thanks Gwendal.

Series has been applied and pushed out to for-next now.

Thanks all. Bring on the next batch. Javier!


-Olof
--
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

Re: [PATCH v5 4/7] platform/chrome: Add Chrome OS EC userspace device interface

[Olof Johansson]

On Mon, Feb 02, 2015 at 12:26:25PM +0100, Javier Martinez Canillas wrote:
 From: Bill Richardson wfric...@chromium.org
 
 This patch adds a device interface to access the
 Chrome OS Embedded Controller from user-space.
 
 Signed-off-by: Bill Richardson wfric...@chromium.org
 Reviewed-by: Simon Glass s...@google.com
 Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
 Reviewed-by: Gwendal Grignou gwen...@chromium.org
 ---
 
 Changes since v4: None.
 
 Changes since v3: None.
 
 Changes since v2:
  - Rename the devname to cros-ec-ctl. Suggested by Lee Jones.
  - Added Gwendal Grignou Reviewed-by tag.
 
 Changes since v1: None, new patch.

Hi,

 ---
  Documentation/ioctl/ioctl-number.txt  |   1 +
  drivers/platform/chrome/Kconfig   |  14 +-
  drivers/platform/chrome/Makefile  |   1 +
  drivers/platform/chrome/cros_ec_dev.c | 268 
 ++
  drivers/platform/chrome/cros_ec_dev.h |  47 ++
  5 files changed, 328 insertions(+), 3 deletions(-)
  create mode 100644 drivers/platform/chrome/cros_ec_dev.c
  create mode 100644 drivers/platform/chrome/cros_ec_dev.h
 
 diff --git a/Documentation/ioctl/ioctl-number.txt 
 b/Documentation/ioctl/ioctl-number.txt
 index 8136e1fd30fd..51f4221657bf 100644
 --- a/Documentation/ioctl/ioctl-number.txt
 +++ b/Documentation/ioctl/ioctl-number.txt
 @@ -321,6 +321,7 @@ Code  Seq#(hex)   Include FileComments
  0xDB 00-0F   drivers/char/mwave/mwavepub.h
  0xDD 00-3F   ZFCP device driver  see drivers/s390/scsi/
   mailto:aherr...@de.ibm.com
 +0xEC 00-01   drivers/platform/chrome/cros_ec_dev.h   ChromeOS EC driver

It seems like a bad idea to reuse the same ioctl numbers as the out-of-tree
driver but changing the arguments. So please allocate a few more and use 2/3
for this calling interface.

[...]

 new file mode 100644
 index ..15c54c4c5531
 --- /dev/null
 +++ b/drivers/platform/chrome/cros_ec_dev.h
 @@ -0,0 +1,47 @@
 +/*
 + * cros_ec_dev - expose the Chrome OS Embedded Controller to userspace
 + *
 + * Copyright (C) 2014 Google, Inc.
 + *
 + * This program is free software; you can redistribute it and/or modify
 + * it under the terms of the GNU General Public License as published by
 + * the Free Software Foundation; either version 2 of the License, or
 + * (at your option) any later version.
 + *
 + * This program is distributed in the hope that it will be useful,
 + * but WITHOUT ANY WARRANTY; without even the implied warranty of
 + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 + * GNU General Public License for more details.
 + *
 + * You should have received a copy of the GNU General Public License
 + * along with this program. If not, see http://www.gnu.org/licenses/.
 + */
 +
 +#ifndef _CROS_EC_DEV_H_
 +#define _CROS_EC_DEV_H_
 +
 +#include linux/ioctl.h
 +#include linux/types.h
 +#include linux/mfd/cros_ec.h
 +
 +#define CROS_EC_DEV_NAME cros_ec
 +#define CROS_EC_DEV_VERSION 1.0.0
 +
 +/*
 + * @offset: within EC_LPC_ADDR_MEMMAP region
 + * @bytes: number of bytes to read. zero means read a string (including 
 '\0')
 + * (at most only EC_MEMMAP_SIZE bytes can be read)
 + * @buffer: where to store the result
 + * ioctl returns the number of bytes read, negative on error
 + */
 +struct cros_ec_readmem {
 + uint32_t offset;
 + uint32_t bytes;
 + uint8_t buffer[EC_MEMMAP_SIZE];
 +};
 +
 +#define CROS_EC_DEV_IOC   0xEC
 +#define CROS_EC_DEV_IOCXCMD   _IOWR(CROS_EC_DEV_IOC, 0, struct 
 cros_ec_command)
 +#define CROS_EC_DEV_IOCRDMEM  _IOWR(CROS_EC_DEV_IOC, 1, struct 
 cros_ec_readmem)

I.e. go with 2/3 here.

(I can just do that change when I apply this patch, let me know if you prefer
that).


-Olof
 
--
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

Re: [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support

[Olof Johansson]

On Tue, Feb 17, 2015 at 07:26:50PM -0700, Simon Glass wrote:
 Hi,
 
 On 16 February 2015 at 01:19, Javier Martinez Canillas
 javier.marti...@collabora.co.uk wrote:
  Hello Olof,
 
  On 02/02/2015 12:26 PM, Javier Martinez Canillas wrote:
  Hello,
 
  The mainline ChromeOS Embedded Controller (EC) driver is still missing some
  features that are present in the downstream ChromiumOS tree. These are:
 
- Low Pin Count (LPC) interface
- User-space device interface
- Access to vboot context stored on a block device
- Access to vboot context stored on EC's nvram
- Power Delivery Device
- Support for multiple EC in a system
 
  This is a fifth version of a series that adds support for the first two of
  the missing features: the EC LPC and EC character device interfaces that
  are used by user-space to access the ChromeOS EC. The support patches were
  taken from the downstream ChromiumOS 3.14 tree with the fixes and cleanups
  squashed to have a minimal patch-set.
 
 
  Any comments on this series? The last version was posted a couple of weeks
  ago but the series have been in the list for months. Lee has already acked
  the mfd changes so you can merge all through your chrome-platform tree if
  you want.
 
  It wold be great if this series get in to have the EC user-space interface
  supported and to minimize the delta with the Chromemium OS kernel since it
  still has other features that needs to be upstreamed like multiple EC in a
  system and access to vboot context stored in block device or EC's nvram.
 
 Are you sure Olof is the right maintainer for this going to mainline?

Yes.

 I do feel for you trying to get all this in and have seen your many
 attempts. It has been in U-Boot for 18 months...I hope you get there
 in the end.

Cool, u-boot has userspace interfaces now? I didn't know that.


-Olof
--
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

Re: [PATCH v5 0/7] platform/chrome: Add user-space dev inferface support

[Olof Johansson]

On Mon, Feb 16, 2015 at 09:19:49AM +0100, Javier Martinez Canillas wrote:
 Hello Olof,
 
 On 02/02/2015 12:26 PM, Javier Martinez Canillas wrote:
  Hello,
  
  The mainline ChromeOS Embedded Controller (EC) driver is still missing some
  features that are present in the downstream ChromiumOS tree. These are:
  
- Low Pin Count (LPC) interface
- User-space device interface
- Access to vboot context stored on a block device
- Access to vboot context stored on EC's nvram
- Power Delivery Device
- Support for multiple EC in a system
  
  This is a fifth version of a series that adds support for the first two of
  the missing features: the EC LPC and EC character device interfaces that
  are used by user-space to access the ChromeOS EC. The support patches were
  taken from the downstream ChromiumOS 3.14 tree with the fixes and cleanups
  squashed to have a minimal patch-set.
  
 
 Any comments on this series? The last version was posted a couple of weeks
 ago but the series have been in the list for months. Lee has already acked
 the mfd changes so you can merge all through your chrome-platform tree if
 you want.
 
 It wold be great if this series get in to have the EC user-space interface
 supported and to minimize the delta with the Chromemium OS kernel since it
 still has other features that needs to be upstreamed like multiple EC in a
 system and access to vboot context stored in block device or EC's nvram.

Yeah, sorry for dragging my feet on this. The only thing I found that should
should be revisited is the reuse of the ioctl numbers to make it easier to
transition on the Chrome OS side -- otherwise it'll be hard to know from
userspace to use old or new structs during transition without a flag day.


-Olof
--
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

Re: [GIT PULL 3/3] Samsung CPUIdle updates for v3.20

[Olof Johansson]

On Wed, Feb 04, 2015 at 11:31:42PM +0900, Kukjin Kim wrote:
 Hi,
 
 This is cpuidle update for v3.20.
 Please pull.
 
 Thanks,
 Kukjin
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-cpuidle
 
 for you to fetch changes up to 712eddf70225ab5ae65e946e22d2dfe6b93e8dd1:
 
   cpuidle: exynos: add coupled cpuidle support for exynos4210
 (2015-01-30 08:39:15 +0900)
 
 
 Samsung CPUIdle updates for v3.20
 
 - adds coupled cpuidle support for exynos4210
   : fix for Exynos platform PM code preparing it for the coupled
   cpuidle support and adds coupled cpuidle AFTR mode on exynos4210
 
 Note this is mostrly based on earlier cpuidle-exynos4210 driver
 from Daniel Lezcano and Bart updated.

Merged, thanks.

-Olof
--
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

Re: [GIT PULL 1/3] Samsung exynos_defconfig updates for v3.20

[Olof Johansson]

On Wed, Feb 04, 2015 at 11:31:23PM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin
 
 Here is late pull request for exynos_defconfig updates for v3.20 and if
 you're OK please pull.
 
 Note this is based on previous exynos_defconfig pull-request during
 v3.19-rc.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit 842ebf60bbad6d6e5ebaa063409fefdd2a7eb992:
 
   ARM: exynos_defconfig: Enable LM90 driver (2014-12-23 00:20:44 +0900)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-defconfig
 
 for you to fetch changes up to 39ecb024e9727c9c29765ca233bdca91c8589d01:
 
   ARM: exynos_defconfig: Enable CONFIG_FHANDLE (2015-01-24 13:50:01 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 2/3] Samsung 4th DT updates for v3.20

[Olof Johansson]

On Wed, Feb 04, 2015 at 11:31:33PM +0900, Kukjin Kim wrote:
 Hi,
 
 Here is 4th DT updates for v3.20.
 Please pull.
 
 Note there are several dt updates in my tree which has a dependency with
 driver side for v3.20 and I hope it can be sent to upstream via arm-soc
 during late merge window. If it is OK to you guys, I'll send a pull
 request soon. (example tmu, asoc and devfreq)

Why do they have driver dependencies? Can't the dts contents be merged
separately, such that the drivers just work once they land?

Or are you redefining bindings in an incompatible manner?

 The following changes since commit ea08de16eb1ba2052ce2db4b58b62a2ec33357a3:
 
   ARM: dts: Add DISP1 power domain for exynos5420 (2015-01-29 08:52:23
 +0900)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-4
 
 for you to fetch changes up to 7808cae3e97140781eb3f712084caf4e44c126c9:
 
   ARM: dts: Add PPMU node for exynos4412-trats2 (2015-02-04 08:11:52 +0900)


Merged.


-Olof
--
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

Re: [GIT PULL 4/4] Samsung 3rd DT updates for v3.20

[Olof Johansson]

On Thu, Jan 29, 2015 at 09:34:27AM +0900, Kukjin Kim wrote:
 Hi,
 
 This is another Samsung DT updates for v3.20. Since including a clock
 patch with Mike and Sylwester's acks so sending separate pull-request.
 
 Please pull and if any problems please let me know.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit 6591a02e17e6d6587c3cf7588d523fa6f26b584a:
 
   ARM: dts: reduce total RAM by 22 MiB for exynos5422-odroidxu3
 (2015-01-24 13:24:10 +0900)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-3
 
 for you to fetch changes up to ea08de16eb1ba2052ce2db4b58b62a2ec33357a3:
 
   ARM: dts: Add DISP1 power domain for exynos5420 (2015-01-29 08:52:23
 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 2/4] Samsung mach updates for v3.20

[Olof Johansson]

On Thu, Jan 29, 2015 at 09:33:52AM +0900, Kukjin Kim wrote:
 Hi,
 
 This is for updating of mach-exynos and plat-samsung.
 Please pull and if any problems, please let me know.
 
 Thanks,
 Kukjin
 
 
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-update
 
 for you to fetch changes up to a4f582f5c5fe3e8eaef7ce637c894619bdee650e:
 
   ARM: EXYNOS: Add exynos3250 suspend-to-ram support (2015-01-15
 00:24:26 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 1/4] Samsung Cleanup for v3.20

[Olof Johansson]

On Thu, Jan 29, 2015 at 09:33:39AM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin
 
 Please pull Samsung cleanup for v3.20.
 
 This cleanup is very nice, Samsung SoCs no more use specific DMA and
 remove i2c sys from mach-exynos. Thanks to Arnd and all involved guys.
 
 - Kukjin
 
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-cleanup

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 3/4] Samsung 2nd DT updates for v3.20

[Olof Johansson]

On Thu, Jan 29, 2015 at 09:34:14AM +0900, Kukjin Kim wrote:
 Hi,
 
 This is 2nd Samsung DT updates for v3.20, please pull.
 
 Thanks,
 Kukjin
 
 
 The following changes since commit 23c76dc666471dce5ce71b620839d2465723a7c9:
 
   ARM: dts: Configure regulators for suspend on exynos Peach boards
 (2015-01-15 00:30:49 +0900)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-2

Merged, thanks.


-Olof
--
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

Re: [GIT PULL] Samsung DT updates for v3.20

[Olof Johansson]

On Sat, Jan 24, 2015 at 12:59:20PM +0900, Kukjin Kim wrote:
 Hi,
 
 Please pull Samsung DT updates for v3.20.
 I checked to use signed tag in this time ;)
 
 Thanks and if any problems, please let me know.
 
 - Kukjin
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt
 
 for you to fetch changes up to 23c76dc666471dce5ce71b620839d2465723a7c9:
 
   ARM: dts: Configure regulators for suspend on exynos Peach boards
 (2015-01-15 00:30:49 +0900)

Merged, thanks for the tag description!


-Olof
--
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

Re: [GIT PULL RE-SEND] Samsung fixes for v3.19

[Olof Johansson]

On Thu, Jan 15, 2015 at 12:05:18AM +0900, Kukjin Kim wrote:
 Hi,
 
 Oops, it's totally my fault and mistake. Actually my git command for
 pull-request was correct but the git tool was old version :-( because
 there are two git in my laptop, anyway sorry for that and I'm resending
 with signed tag has been created before.
 
 Please pull if you're OK with my comments on your questions below.
 
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-fixes-3.19
 
 for you to fetch changes up to 26d13bf77b8e59adf4953577ba48e1903545bf7f:
 
   ARM: exynos_defconfig: Enable LM90 driver (2015-01-12 17:16:32 +0900)
 
 
 Samsung fixes for v3.19
 - exynos_defconfig: enable LM90 driver and display panel support
- HWMON
- SENSORS_LM90
- Direct Rendering Manager (DRM)
- DRM bridge registration and lookup framework
- Parade ps8622/ps8625 eDP/LVDS bridge
- NXP ptn3460 eDP/LVDS bridge
- Exynos Fully Interactive Mobile Display controller (FIMD)
- Panel registration and lookup framework
- Simple panels
- Backlight  LCD device support
 
 - use pmu_system_controller phandle for dp phy
   : DP PHY requires pmu_system_controller to handle PMU reg. now

Merged.


-Olof
--
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

Re: [GIT PULL RE-SEND] Samsung exynos7 updates for v3.20

[Olof Johansson]

On Thu, Jan 15, 2015 at 12:07:16AM +0900, Kukjin Kim wrote:
 Hi,
 
 Sorry, I'm resending this pull-request because of missing signed-tag.
 
 Please pull. If any problems, please let me know.
 
 Thanks,
 Kukjin
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
 
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-64
 
 for you to fetch changes up to 6f56eef1f9aba3747c811780a4768618167d5c97:
 
   arm64: Enable ARMv8 based exynos7 SoC support (2014-12-23 00:19:08 +0900)

Merged.


-Olof
--
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

Re: [GIT PULL] Samsung fixes for v3.19

[Olof Johansson]

Hi,

On Mon, Jan 12, 2015 at 05:26:56PM +0900, Kukjin Kim wrote:
 Hi Arnd, Olof, Kevin
 
 Please pull samsung fixes for v3.19.
 
 Thanks,
 Kukjin
 
 The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
 
   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
 
 are available in the git repository at:
   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 v3.19-samsung-fixes
 
 Andreas Faerber (1):
   ARM: exynos_defconfig: Enable LM90 driver
 
 Javier Martinez Canillas (1):
   ARM: exynos_defconfig: Enable options for display panel support
 
 Vivek Gautam (1):
   arm: dts: Use pmu_system_controller phandle for dp phy
 
  arch/arm/boot/dts/exynos5250.dtsi |2 +-
  arch/arm/boot/dts/exynos5420.dtsi |4 ++--
  arch/arm/configs/exynos_defconfig |   18 +-
  3 files changed, 20 insertions(+), 4 deletions(-)

Please write a tag description and sign it. You used to do this, why stop?

Also, you're not explaining what these patches fixes. I can see the usefulness
in the display configuration options, but I'm less sure why 3.19 needs the LM90
driver if it's just for consistency?

Finally, please explain why pmu breaks. Sounds like an incompatible binding
change?


-Olof
--
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

Re: [PATCH 2/2] arm: dts: disable CCI on exynos420 based arndale-octa

[Olof Johansson]

On Sat, Jan 10, 2015 at 08:41:36AM +0530, Abhilash Kesavan wrote:
 The arndale-octa board was giving imprecise external aborts during
 boot-up with MCPM enabled. CCI enablement of the boot cluster was found
 to be the cause of these aborts (possibly because the secure f/w was not
 allowing it). Hence, disable CCI for the arndale-octa board.
 
 Signed-off-by: Abhilash Kesavan a.kesa...@samsung.com
 Tested-by: Krzysztof Kozlowski k.kozlow...@samsung.com
 Tested-by: Kevin Hilman khil...@linaro.org
 Tested-by: Tyler Baker tyler.ba...@linaro.org

Applied 1-2 to fixes for 3.19.

Fixed two typos (arm-ARM in subject, and 420-5420).


Thanks,

-Olof
--
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

Re: [PATCH] ARM: multi_v7_defconfig: enable MAX77686 PMIC drivers for exynos4412-prime based SoCs

[Olof Johansson]

On Thu, Dec 04, 2014 at 01:24:24PM -0800, Tyler Baker wrote:
 This patch enables the MAX77686 PMIC drivers in the multi_v7_defconfig used
 on exynos4412-prime family of SoCs [1]. The exynos4412-prime based boards
 are producing the following runtime errors only on the multi_v7_defconfig [2]:
 
 kern.err: deviceless supply vdd_arm not found, using dummy regulator
 kern.err: exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1287500
 kern.err: cpufreq: __target_index: Failed to change cpu frequency: -22
 
 I reviewed the exynos_defconfig, which does not produce these runtime
 errors. It was obvious that the exynos_defconfig has the PMIC drivers
 enabled, whereas the multi_v7_defconfig does not. This patch has been tested 
 on a odroid-u2 and a odroid-u3 board. It has resolved the runtime errors.
 Therefore, I purpose we enabled these drivers in the multi_v7_defconfig.
 
 [1] http://www.hardkernel.com/main/products/prdt_info.php?g_code=G135270682824
 [2] 
 http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc7-48-g7cc78f8/arm-multi_v7_defconfig/lab-tbaker-00/boot-exynos4412-odroidu3.html
 

FWIW, the 5250-based Samsung Chromebook also uses 77686.

Applied to next/defconfig for 3.19 after fixing up some fuzz.


-Olof
--
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

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

[Olof Johansson]

On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin,

 On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin Kim kg...@kernel.org writes:

 Kevin Hilman wrote:

 From: Kevin Hilman khil...@linaro.org

 The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
 during boot testing, causing various userspace startup failures.

 Disable until it has gotten more testing.

 Cc: Kukjin Kim kgene@samsung.com,
 Cc: Javier Martinez Canillas javier.marti...@collabora.co.uk,
 Cc: Sachin Kamat sachin.ka...@samsung.com,
 Cc: Doug Anderson diand...@chromium.org,
 Cc: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com,
 Cc: Krzysztof Kozlowski k.kozlow...@samsung.com,
 Cc: Tushar Behera tushar.beh...@linaro.org,
 Cc: sta...@vger.kernel.org # v3.17+
 Signed-off-by: Kevin Hilman khil...@linaro.org
 ---
 This has been reported by a few people[1], but not investigated or fixed, 
 so it's
 time to disable this feature until it can be fixed.

 Hi Kevin,

 Yeah I agree with your opinion.

 But as you can see my tree, I've queued regarding mcpm patches for 3.19 will
 be shown in -next in this weekend.

 Which of the recently queued patches are expected to address the
 imprecise abort issue?  I'd be happy to test them out.

 Exynos5 MCPM is still broken in linux-next and still causing an imprecise 
 abort.

 What is the status of $SUBJECT patch?

 Anyway let me apply this into -fixes and
 then let's enable after test its functionality in -next in a couple of days.

 Yes, I think this needs to be applied until these aborts are understood
 and fixed.

 Is anyone at Samsung actually looking into these MCPM issues?

Hi Kevin,

What hardware are you having problems with? 5420 or 5422/5800?


-Olof
--
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

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

[Olof Johansson]

On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman khil...@kernel.org wrote:
 On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson o...@lixom.net wrote:
 On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin,

 On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin Kim kg...@kernel.org writes:

 Kevin Hilman wrote:

 From: Kevin Hilman khil...@linaro.org

 The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
 during boot testing, causing various userspace startup failures.

 Disable until it has gotten more testing.

 Cc: Kukjin Kim kgene@samsung.com,
 Cc: Javier Martinez Canillas javier.marti...@collabora.co.uk,
 Cc: Sachin Kamat sachin.ka...@samsung.com,
 Cc: Doug Anderson diand...@chromium.org,
 Cc: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com,
 Cc: Krzysztof Kozlowski k.kozlow...@samsung.com,
 Cc: Tushar Behera tushar.beh...@linaro.org,
 Cc: sta...@vger.kernel.org # v3.17+
 Signed-off-by: Kevin Hilman khil...@linaro.org
 ---
 This has been reported by a few people[1], but not investigated or 
 fixed, so it's
 time to disable this feature until it can be fixed.

 Hi Kevin,

 Yeah I agree with your opinion.

 But as you can see my tree, I've queued regarding mcpm patches for 3.19 
 will
 be shown in -next in this weekend.

 Which of the recently queued patches are expected to address the
 imprecise abort issue?  I'd be happy to test them out.

 Exynos5 MCPM is still broken in linux-next and still causing an imprecise 
 abort.

 What is the status of $SUBJECT patch?

 Anyway let me apply this into -fixes and
 then let's enable after test its functionality in -next in a couple of 
 days.

 Yes, I think this needs to be applied until these aborts are understood
 and fixed.

 Is anyone at Samsung actually looking into these MCPM issues?

 Hi Kevin,

 What hardware are you having problems with? 5420 or 5422/5800?

 Yes.  :)

 exynos5420-arndale-octa:
 http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html
 exynos5422-odroid-xu3:
 http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html

 My boot tests seem to pass fine because I have such a minimal
 userspace, but Tyler Baker reported that with a real userspace, he
 can't boot to a shell:

   
 http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html

I'm not surprised that 5420 has issues, but I have not seen any
external aborts on neither Chromebook that I have in my farm.

Sounds like the secondary cpus should be disabled on those device
trees instead, doesn't it?


-Olof
--
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

Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable

[Olof Johansson]

On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson o...@lixom.net wrote:
 On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman khil...@kernel.org wrote:
 On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson o...@lixom.net wrote:
 On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin,

 On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman khil...@kernel.org wrote:
 Kukjin Kim kg...@kernel.org writes:

 Kevin Hilman wrote:

 From: Kevin Hilman khil...@linaro.org

 The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
 during boot testing, causing various userspace startup failures.

 Disable until it has gotten more testing.

 Cc: Kukjin Kim kgene@samsung.com,
 Cc: Javier Martinez Canillas javier.marti...@collabora.co.uk,
 Cc: Sachin Kamat sachin.ka...@samsung.com,
 Cc: Doug Anderson diand...@chromium.org,
 Cc: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com,
 Cc: Krzysztof Kozlowski k.kozlow...@samsung.com,
 Cc: Tushar Behera tushar.beh...@linaro.org,
 Cc: sta...@vger.kernel.org # v3.17+
 Signed-off-by: Kevin Hilman khil...@linaro.org
 ---
 This has been reported by a few people[1], but not investigated or 
 fixed, so it's
 time to disable this feature until it can be fixed.

 Hi Kevin,

 Yeah I agree with your opinion.

 But as you can see my tree, I've queued regarding mcpm patches for 3.19 
 will
 be shown in -next in this weekend.

 Which of the recently queued patches are expected to address the
 imprecise abort issue?  I'd be happy to test them out.

 Exynos5 MCPM is still broken in linux-next and still causing an imprecise 
 abort.

 What is the status of $SUBJECT patch?

 Anyway let me apply this into -fixes and
 then let's enable after test its functionality in -next in a couple of 
 days.

 Yes, I think this needs to be applied until these aborts are understood
 and fixed.

 Is anyone at Samsung actually looking into these MCPM issues?

 Hi Kevin,

 What hardware are you having problems with? 5420 or 5422/5800?

 Yes.  :)

 exynos5420-arndale-octa:
 http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html
 exynos5422-odroid-xu3:
 http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html

 My boot tests seem to pass fine because I have such a minimal
 userspace, but Tyler Baker reported that with a real userspace, he
 can't boot to a shell:

   
 http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html

 I'm not surprised that 5420 has issues, but I have not seen any
 external aborts on neither Chromebook that I have in my farm.

 Sounds like the secondary cpus should be disabled on those device
 trees instead, doesn't it?

Er, cluster, not cpus.


-Olof
--
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

Re: [PATCH v3 2/2] ARM: EXYNOS: Call regulator core suspend prepare and finish functions

[Olof Johansson]

On Tue, Nov 11, 2014 at 2:23 AM, Javier Martinez Canillas
jav...@dowhile0.org wrote:
 Hello Kukjin,

 On Thu, Oct 30, 2014 at 11:06 AM, Javier Martinez Canillas
 jav...@dowhile0.org wrote:
 Hello Kukjin,

 On Mon, Oct 20, 2014 at 11:05 PM, Javier Martinez Canillas
 javier.marti...@collabora.co.uk wrote:
 The regulator framework has a set of helpers functions to be used when
 the system is entering and leaving from suspend but these are not called
 on Exynos platforms. This means that the .set_suspend_* function handlers
 defined by regulator drivers are not called when the system is suspended.

 Suggested-by: Doug Anderson diand...@chromium.org
 Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
 Reviewed-by: Doug Anderson diand...@chromium.org
 ---
  arch/arm/mach-exynos/suspend.c | 23 +++
  1 file changed, 23 insertions(+)


 Any comments on this patch?


 Just a gentle reminder about this patch.

Kukjin, should I just apply this directly since you seem to be busy?


Thanks,

-Olof
--
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

Re: [GIT PULL 2/3 v2] 1st Round of Samsung PM updates for v3.19

[Olof Johansson]

On Wed, Nov 05, 2014 at 09:31:49AM +0900, Kukjin Kim wrote:
 Olof Johansson wrote:
  On Tue, Oct 28, 2014 at 11:00:57AM +0900, Kukjin Kim wrote:
   Hi,
  
 Hi,
 
   I'm sending new pull-request for tags/samsung-pm-v2 instead of 
   tags/samsung-pm.
   Note that just added fix build with ARM_CPU_SUSPEND=n from Arnd, please 
   pull.
  
   Thanks,
   Kukjin
  
  Kukjin,
  
  The history here is somewhat odd. You've merged in cleanup and dt,
  and two merges of pm (one with just the extra fix from Arnd). Are the
  merges needed just to avoid merge conflicts? If so, we can resolve that
  when we merge here, that's not a problem.
  
 Oops, probably I did 'checkout for-next' in my tree when I tagged
 tags/samsung-pm-v2 :(
 
  If it's needed because pm doesn't work without the dt branch also being
  merged in, then this is not sufficient since when bisecting, you might get
  only the pm branch contents and not the dt contents in some circumstances.
  
  So, please confirm which of the cases it is, and resubmit just the bare
  pm branch if there are no dependencies.
  
 Can you please merge branch v3.19-next/pm-samsung-2 instead?
 If you don't want to merge just branch, I'll re-send with new tag.
 
 Sorry for the inconvenience.

Hi,

I've merged the branch into next/soc now.


-Olof
--
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

Re: [GIT PULL 2/3 v2] 1st Round of Samsung PM updates for v3.19

[Olof Johansson]

On Tue, Oct 28, 2014 at 11:00:57AM +0900, Kukjin Kim wrote:
 Hi,
 
 I'm sending new pull-request for tags/samsung-pm-v2 instead of 
 tags/samsung-pm.
 Note that just added fix build with ARM_CPU_SUSPEND=n from Arnd, please 
 pull.
 
 Thanks,
 Kukjin

Kukjin,

The history here is somewhat odd. You've merged in cleanup and dt,
and two merges of pm (one with just the extra fix from Arnd). Are the
merges needed just to avoid merge conflicts? If so, we can resolve that
when we merge here, that's not a problem.

If it's needed because pm doesn't work without the dt branch also being
merged in, then this is not sufficient since when bisecting, you might get
only the pm branch contents and not the dt contents in some circumstances.

So, please confirm which of the cases it is, and resubmit just the bare
pm branch if there are no dependencies.


-Olof
--
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

Re: [GIT PULL 1/3] 1st Round of Samsung cleanup for v3.19

[Olof Johansson]

On Tue, Oct 21, 2014 at 12:54:14AM +0900, Kukjin Kim wrote:
 Hi,
 
 Here is 1st round of Samsung updates for v3.19 and actually it has
 been sent out to arm-soc for v3.18 before but as you know missed.
 I've just rebased the branch on top of v3.18-rc1, please pull.
 
 Thanks,
 Kukjin
 
 
 
 The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
 
   Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
 
 are available in the git repository at:
 

 git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-cleanup
 
 for you to fetch changes up to 13cfa6c4f7facfc690ba9e99ec382c151fddaced:
 
   ARM: EXYNOS: Fix CPU idle clock down after CPU off (2014-10-21
 00:06:22 +0900)

Merged.


-Olof
--
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

Re: [GIT PULL 3/3] 1st Round of Samsung DT updates for v3.19

[Olof Johansson]

On Tue, Oct 21, 2014 at 12:54:41AM +0900, Kukjin Kim wrote:
 Hi,
 
 Here is Samsung DT updates for v3.19, please pull.
 
 Thanks,
 Kukjin
 
 ---
 
 The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
 
   Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
 
 are available in the git repository at:
 

 git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt
 
 for you to fetch changes up to e540920cf21c2764047b8a6ddaeaa0683624e46e:
 
   ARM: dts: add CPU nodes for Exynos4 SoCs (2014-10-21 00:12:42 +0900)

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 1/2] Samsung fixes for v3.18

[Olof Johansson]

On Tue, Oct 14, 2014 at 4:26 PM, Kukjin Kim kgene@samsung.com wrote:
 The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

   Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

 are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git

Merged, thanks.


-Olof
--
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

Re: [GIT PULL 2/2] Samsung defconfig updates for v3.18

[Olof Johansson]

On Tue, Oct 14, 2014 at 4:27 PM, Kukjin Kim kgene@samsung.com wrote:
 The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

   Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

 are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-defconfig

 for you to fetch changes up to 508423bebcda29eb0ba7c627f895387dad7cdcd6:

   ARM: exynos_defconfig: enable USB gadget support (2014-09-25 18:20:18
 +0900)

Merged, thanks.


-Olof
--
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

Re: Unable to boot mainline on snow chromebook since 3.15

[Olof Johansson]

Hi,

Been travelling I'm buried in email, so a bit slow at responding.

On Mon, Sep 8, 2014 at 12:40 PM, Grant Likely grant.lik...@secretlab.ca wrote:
 On Mon, Sep 8, 2014 at 4:58 PM, Doug Anderson diand...@chromium.org wrote:
 Grant,

 On Mon, Sep 8, 2014 at 5:20 AM, Grant Likely grant.lik...@secretlab.ca 
 wrote:
 On Mon, Sep 8, 2014 at 12:21 PM, Will Deacon will.dea...@arm.com wrote:
 On Sun, Sep 07, 2014 at 05:19:03PM +0100, Tomasz Figa wrote:
 At least for next 3.17-rc I'd suggest fixing this up in respective clock
 driver and dropping the hack only after Exynos DRM patches are merged
 and confirmed working.

 Whilst I'm sympathetic to people working to enable DRM, I think this is
 the right solution to the problem. The transition from simplefb to DRM
 shouldn't break display for a bunch of kernel revisions whilst the code is
 in flux.

 I would go further. The kernel behaviour has changed, and we have to
 deal with platforms that assume the old behaviour. That means either
 defaulting to leaving enabled regulators/clocks alone unless there is
 a flag in the DT saying they can be power managed, or black listing
 platforms that are known to depend on the regulator being on.

 Updating the device tree must not be required to get the kernel to
 boot, but it is valid to require a DT upgrade to get better
 performance (battery life) out of the platform.

 In this case people using SImple FB are not really using an officially
 sanctioned device tree.  The simple-fb fragment is created on the fly
 via a DO NOT SUBMIT patch sitting on a code review server.  It's not
 something that's shipped with real firmware nor is it something
 present in the kernel.  See
 https://chromium-review.googlesource.com/#/c/49358/2/board/samsung/smdk5250/smdk5250.c
 as I mentioned above.

 Is this really a device tree that we need to guarantee backward
 compatibility with?

 Well, lets see... We've got a real user complaining about a platform
 that used to work on mainline, and no longer does. The only loophole
 for ignoring breakage is if there nobody cares that it is broken. That
 currently isn't the case. So even though it's based on a patch that
 has DO NOT SUBMIT in large friendly letters on the front cover, it
 doesn't change the situation that mainline has a regression.

Yeah, I'm with you on this Grant, it doesn't matter what the patch is
labelled as.

For extra added complication, the firmware that is referenced above
isn't what most people use, they use another binary that someone that
I don't even know who it is has built, that boots the kernel in HYP
mode. I expect the ARM guys to be using that version since they make
use of KVM, etc.

One way to deal with this could be to add a quirk at boot time --
looking for the simplefb and if found, modifies the regulators to keep
them on. That'd go in the kernel, not in firmware.

Much better would have been if the DRM changes worked when they
landed, so that the migration form simplefb to drm was invisible to
the user. Or at least, to get them working ASAP since they're still
broken. :(


-Olof
--
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

Re: Unable to boot mainline on snow chromebook since 3.15

[Olof Johansson]

On Wed, Sep 10, 2014 at 7:31 AM, Mark Brown broo...@kernel.org wrote:
 On Wed, Sep 10, 2014 at 06:06:46AM -0700, Olof Johansson wrote:
 On Mon, Sep 8, 2014 at 12:40 PM, Grant Likely grant.lik...@secretlab.ca 
 wrote:

  Well, lets see... We've got a real user complaining about a platform
  that used to work on mainline, and no longer does. The only loophole
  for ignoring breakage is if there nobody cares that it is broken. That
  currently isn't the case. So even though it's based on a patch that
  has DO NOT SUBMIT in large friendly letters on the front cover, it
  doesn't change the situation that mainline has a regression.

 Yeah, I'm with you on this Grant, it doesn't matter what the patch is
 labelled as.

 One way to deal with this could be to add a quirk at boot time --
 looking for the simplefb and if found, modifies the regulators to keep
 them on. That'd go in the kernel, not in firmware.

 Well, we should also be fixing simplefb to manage the resources it uses
 though that doesn't clean up after the broken DTs that are currently
 deployed.

 As well as the regulators we'll also need to fix the clocks.  If we're
 going to start adding these fixups perhaps we want to consider having a
 wrapper stage that deals with rewriting DTs prior to trying to use them?
 I'm not sure if it makes much difference but there's overlap with other
 tools like the ATAGs conversion wrapper and building separately would
 let the fixup code run early without directly going into the early init
 code (which seems a bit scary).

Yes, having a stage that fixes up broken device trees makes a lot of
sense. It can likely be plugged into the machine descriptor today per
platform, since I think most things we have going on right now are
platform-specific quirks.

I'm strongly against doing this outside of the kernel, since they're
closely tied together today. We've always had the quirk tables for
devices in the kernel, and we used to do this a long time ago on
powerpc as well (we did it before we built the flat DT out of the OF
equivalent there, most of the time).

 Much better would have been if the DRM changes worked when they
 landed, so that the migration form simplefb to drm was invisible to
 the user. Or at least, to get them working ASAP since they're still
 broken. :(

 As far as I can tell the problem here is coming from the decision to
 have simplefb use resources without knowing about them - can we agree
 that this is a bad idea?

As already argued, there are good reasons to sometimes allow this, as
long as it can be expected that it's something that's just used during
early boot. For example, having DEBUG_LL output on a pre-mapped
framebuffer could be really useful. Once DRM comes up, it'll tear down
the existing one.


-Olof
--
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

Re: [PATCH 11/14] arm64: dts: Add initial device tree support for EXYNOS7

[Olof Johansson]

On Thu, Aug 28, 2014 at 2:48 AM, Mark Rutland mark.rutl...@arm.com wrote:
 Hi,

  +   cpus {
  +   #address-cells = 2;
  +   #size-cells = 0;

 Why size-cells=2? Can you not fit a cpuid in 32 bits?

 As of commit 72aea393a2e7 (arm64: smp: honour #address-size when parsing
 CPU reg property) Linux can handle single-cell cpu node reg entries
 where /cpus/#address-cells = 1.

 I can't make any guarantees about other code (e.g. bootloaders) which
 might try to do things with cpu nodes, YMMV.

Ok. If address-cells is kept at 2 the unit address needs to be changed
to 0,0. So one or the other has to be changed.

 [...]

  +   hsi2c_2: hsi2c@14E6 {

 I much prefer lowercase hex in unit addresses (and reg entries) below. I
 know 32-bit uses uppercase, but let's switch going forward here.

 My preference also; I'm happy to enforce that on new dts.

 [...]

  +   timer {
  +   compatible = arm,armv8-timer;
  +   interrupts = 1 13 0xff01,
  +1 14 0xff01,
  +1 11 0xff01,
  +1 10 0xff01;
  +   clock-frequency = 2400;
  +   use-clocksource-only;
  +   use-physical-timer;

 These two properties are not standard, and I would expect any 64-bit
 platform to come with PSCI such that you have a way to initialize the
 virtual timers.

 Likewise with clock-frequency. It's not a full workaround, and it's not
 hard to initialise CNTFRQ on each CPU.

Technically clock-frequency is documented, but not recommended to be
used unless needed for working around firmware that doesn't setup the
register value. :)

In this case it's likely a cargo cult carry over from 5250 where the
CNTFRQ requirement happened around the same time as we were working on
it so that generation firmware lacked support for it -- it should
since then have been fixed properly.


-Olof
--
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

Re: [PATCH 11/14] arm64: dts: Add initial device tree support for EXYNOS7

[Olof Johansson]

On Thu, Aug 28, 2014 at 10:03 AM, Mark Rutland mark.rutl...@arm.com wrote:
 On Thu, Aug 28, 2014 at 05:28:22PM +0100, Olof Johansson wrote:
 On Thu, Aug 28, 2014 at 2:48 AM, Mark Rutland mark.rutl...@arm.com wrote:
  Hi,
 
   +   cpus {
   +   #address-cells = 2;
   +   #size-cells = 0;
 
  Why size-cells=2? Can you not fit a cpuid in 32 bits?
 
  As of commit 72aea393a2e7 (arm64: smp: honour #address-size when parsing
  CPU reg property) Linux can handle single-cell cpu node reg entries
  where /cpus/#address-cells = 1.
 
  I can't make any guarantees about other code (e.g. bootloaders) which
  might try to do things with cpu nodes, YMMV.

 Ok. If address-cells is kept at 2 the unit address needs to be changed
 to 0,0. So one or the other has to be changed.

 I'm happy either way.

 I'm not sure the rest of the tree had 0, prefixes on all of the
 unit-addresses for 64-bit addresses that were under 4GB, and I'm not
 sure that existing dts consistently do that either.

 Do we want to enforce that for all 64-bit unit-addresses?

Yeah, I believe that's the only valid format for a 2-address-cell unit address.

  [...]
 
   +   hsi2c_2: hsi2c@14E6 {
 
  I much prefer lowercase hex in unit addresses (and reg entries) below. I
  know 32-bit uses uppercase, but let's switch going forward here.
 
  My preference also; I'm happy to enforce that on new dts.
 
  [...]
 
   +   timer {
   +   compatible = arm,armv8-timer;
   +   interrupts = 1 13 0xff01,
   +1 14 0xff01,
   +1 11 0xff01,
   +1 10 0xff01;
   +   clock-frequency = 2400;
   +   use-clocksource-only;
   +   use-physical-timer;
 
  These two properties are not standard, and I would expect any 64-bit
  platform to come with PSCI such that you have a way to initialize the
  virtual timers.
 
  Likewise with clock-frequency. It's not a full workaround, and it's not
  hard to initialise CNTFRQ on each CPU.

 Technically clock-frequency is documented, but not recommended to be
 used unless needed for working around firmware that doesn't setup the
 register value. :)

 True.

 In this case it's likely a cargo cult carry over from 5250 where the
 CNTFRQ requirement happened around the same time as we were working on
 it so that generation firmware lacked support for it -- it should
 since then have been fixed properly.

 It's probably unhelpful that the documentation isn't explicit about
 that. On that front, how about the patch below?

 Mark.

 8
 From 67104ad5a56e4c18f9c41f06af028b7561740afd Mon Sep 17 00:00:00 2001
 From: Mark Rutland mark.rutl...@arm.com
 Date: Thu, 28 Aug 2014 17:41:03 +0100
 Subject: [PATCH] Doc: dt: arch_timer: discourage clock-frequency use

 The ARM Generic Timer (AKA the architected timer, arm_arch_timer)
 features a CPU register (CNTFRQ) which firmware is intended to
 initialize, and non-secure software can read to determine the frequency
 of the timer. On CPUs with secure state, this register cannot be written
 from non-secure states.

 The firmware of early SoCs featuring the timer did not correctly
 initialize CNTFRQ correctly on all CPUs, requiring the frequency to be
 described in DT as a workaround. This workaround is not complete however
 as CNTFRQ is exposed to all software in a privileged non-secure mode,
 including KVM guests. The firmware and DTs for recent SoCs have followed
 the example set by these early SoCs.

 This patch updates the arch timer binding documentation to make it
 clearer that the use of the clock-frequency property is a poor
 work-around. The MMIO generic timer binding is similarly updated, though
 this is less of a concern as there is generally no need to expose the
 MMIO timers to guest OSs.

 Signed-off-by: Mark Rutland mark.rutl...@arm.com
 Cc: Marc Zyngier marc.zyng...@arm.com

With caps fixed:

Acked-by: Olof Johansson o...@lixom.net


 ---
  Documentation/devicetree/bindings/arm/arch_timer.txt | 8 ++--
  1 file changed, 6 insertions(+), 2 deletions(-)

 diff --git a/Documentation/devicetree/bindings/arm/arch_timer.txt 
 b/Documentation/devicetree/bindings/arm/arch_timer.txt
 index 37b2caf..5ca3f95 100644
 --- a/Documentation/devicetree/bindings/arm/arch_timer.txt
 +++ b/Documentation/devicetree/bindings/arm/arch_timer.txt
 @@ -17,7 +17,10 @@ to deliver its interrupts via SPIs.
  - interrupts : Interrupt list for secure, non-secure, virtual and
hypervisor timers, in that order.

 -- clock-frequency : The frequency of the main counter, in Hz. Optional.
 +- clock-frequency : The frequency of the main counter, in Hz. Should be 
 present
 +  only where necessary to work around BROKEN firmware which does not 
 configure

No need to do broken in all caps. In reality I don't expect it to make
a difference on people complying or not. :)

 +  CNTFRQ on all CPUs to a uniform correct value. Use of this property is
 +  STRONGLY DISCOURAGED; fix your firmware

Re: [PATCH 11/14] arm64: dts: Add initial device tree support for EXYNOS7

[Olof Johansson]

On Thu, Aug 28, 2014 at 10:54 AM, Rob Herring r...@kernel.org wrote:
 On Thu, Aug 28, 2014 at 12:19 PM, Olof Johansson o...@lixom.net wrote:
 On Thu, Aug 28, 2014 at 10:03 AM, Mark Rutland mark.rutl...@arm.com wrote:
 On Thu, Aug 28, 2014 at 05:28:22PM +0100, Olof Johansson wrote:
 On Thu, Aug 28, 2014 at 2:48 AM, Mark Rutland mark.rutl...@arm.com wrote:
  Hi,
 
   +   cpus {
   +   #address-cells = 2;
   +   #size-cells = 0;
 
  Why size-cells=2? Can you not fit a cpuid in 32 bits?
 
  As of commit 72aea393a2e7 (arm64: smp: honour #address-size when parsing
  CPU reg property) Linux can handle single-cell cpu node reg entries
  where /cpus/#address-cells = 1.
 
  I can't make any guarantees about other code (e.g. bootloaders) which
  might try to do things with cpu nodes, YMMV.

 Ok. If address-cells is kept at 2 the unit address needs to be changed
 to 0,0. So one or the other has to be changed.

 I'm happy either way.

 I'm not sure the rest of the tree had 0, prefixes on all of the
 unit-addresses for 64-bit addresses that were under 4GB, and I'm not
 sure that existing dts consistently do that either.

 Do we want to enforce that for all 64-bit unit-addresses?

 Yeah, I believe that's the only valid format for a 2-address-cell unit 
 address.

 But we don't do leading 0's anywhere else like single cell unit
 addresses. Buses expressed with ranges and offsets are one example.
 Also, I2C addresses have a 32-bit size in DT yet are only 8-bit and we
 don't do leading zero's there.

Ok, I'm happily proven wrong here, also by confirming how this is done
on real OF.

According to benh:

15:20 benh ojn: 0,0 is not quite right, it's supposed to be used
when the two numbers are different things, like device,fn on PCI

The same is true for 2^32 unit addresses, they just use the one
integer instead of x,y.

So, I take back all I've said on this in the last 72 hours. :) It
looks like we might need to revisit some of the 32-bit DTs.  Simon,
drop the series you had. :)


-Olof
--
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

Re: [PATCH 11/14] arm64: dts: Add initial device tree support for EXYNOS7

[Olof Johansson]

Hi,

On Wed, Aug 27, 2014 at 03:14:18PM +0530, Naveen Krishna Chatradhi wrote:
 Add initial device tree nodes for EXYNOS7 SoC.
 Also, includes the dt-binding definitions for clock ids.

Uh, no -- it just adds the dtsi.

 Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
 Cc: Thomas Abraham thomas...@samsung.com
 Cc: Rob Herring r...@kernel.org
 Cc: Catalin Marinas catalin.mari...@arm.com
 ---
  arch/arm64/boot/dts/exynos7.dtsi |  553 
 ++
  1 file changed, 553 insertions(+)
  create mode 100644 arch/arm64/boot/dts/exynos7.dtsi
 
 diff --git a/arch/arm64/boot/dts/exynos7.dtsi 
 b/arch/arm64/boot/dts/exynos7.dtsi
 new file mode 100644
 index 000..6b9eaf4
 --- /dev/null
 +++ b/arch/arm64/boot/dts/exynos7.dtsi

Let's not make the same mistake as on 32-bit, and go with a directory
hierarchy here from day one.

So, please create a exynos subdirectory for this file. You also need
a Makefile when you add a board dts.

 @@ -0,0 +1,553 @@
 +/*
 + * SAMSUNG EXYNOS7 SoC device tree source
 + *
 + * Copyright (c) 2014 Samsung Electronics Co., Ltd.
 + *   http://www.samsung.com
 + *
 + * SAMSUNG EXYNOS7 SoC device nodes are listed in this file.
 + * EXYNOS7 based board files can include this file and provide
 + * values for board specfic bindings.
 + *
 + * This program is free software; you can redistribute it and/or modify
 + * it under the terms of the GNU General Public License version 2 as
 + * published by the Free Software Foundation.
 + */
 +
 +#include dt-bindings/clock/exynos7-clk.h
 +
 +/ {
 + compatible = samsung,exynos7;
 + interrupt-parent = gic;
 + #address-cells = 1;
 + #size-cells = 1;

You should probably use address-cells/size-cells 2/2 on a 64-bit platform.

 + aliases {
 + pinctrl0 = pinctrl_0;
 + pinctrl1 = pinctrl_1;
 + pinctrl2 = pinctrl_2;
 + pinctrl3 = pinctrl_3;
 + pinctrl4 = pinctrl_4;
 + pinctrl5 = pinctrl_5;
 + pinctrl6 = pinctrl_6;
 + pinctrl7 = pinctrl_7;
 + pinctrl8 = pinctrl_8;
 + pinctrl9 = pinctrl_9;
 + mshc0 = mmc_0;
 + mshc2 = mmc_2;
 + };
 +
 + chipid@1000 {
 + compatible = samsung,exynos4210-chipid;
 + reg = 0x1000 0x100;
 + };
 +
 + cpus {
 + #address-cells = 2;
 + #size-cells = 0;

Why size-cells=2? Can you not fit a cpuid in 32 bits?

 + cpu@0 {
 + device_type = cpu;
 + compatible = arm,cortex-a57, arm,armv8;
 + reg = 0x0 0x0;
 + };
 + };
 +
 + fin_pll: xxti {
 + compatible = fixed-clock;
 + clock-frequency = 2400;
 + clock-output-names = fin_pll;
 + #clock-cells = 0;
 + };
 +
 + gic: interrupt-controller@11001000 {
 + compatible = arm,gic-400;
 + #interrupt-cells = 3;
 + #address-cells = 0;
 + interrupt-controller;
 + reg =   0x11001000 0x1000,
 + 0x11002000 0x1000,
 + 0x11004000 0x2000,
 + 0x11006000 0x2000;
 + };
 +
 + hsi2c_0: hsi2c@1364 {
 + compatible = samsung,exynos7-hsi2c;

Is the i2c controller here completely new?

Also, please use 'i2c' for node name on these nodes.

 + reg = 0x1364 0x1000;
 + interrupts = 0 441 0;
 + #address-cells = 1;
 + #size-cells = 0;
 + pinctrl-names = default;
 + pinctrl-0 = hs_i2c0_bus;
 + clocks = clock_peric0 PCLK_HSI2C0;
 + clock-names = hsi2c;
 + status = disabled;
 + };
 +
 + hsi2c_1: hsi2c@1365 {
 + compatible = samsung,exynos7-hsi2c;
 + reg = 0x1365 0x1000;
 + interrupts = 0 442 0;
 + #address-cells = 1;
 + #size-cells = 0;
 + pinctrl-names = default;
 + pinctrl-0 = hs_i2c1_bus;
 + clocks = clock_peric0 PCLK_HSI2C1;
 + clock-names = hsi2c;
 + status = disabled;
 + };
 +
 + hsi2c_2: hsi2c@14E6 {

I much prefer lowercase hex in unit addresses (and reg entries) below. I
know 32-bit uses uppercase, but let's switch going forward here.

 + mct@101C {
 + compatible = samsung,exynos4210-mct;

Please just do away with MCT here, and use architected timers going
forward. There really shouldn't be a need to keep supporting MCT any
more -- it's a construct from before arch timers on Cortex-A9.

 + mmc_0: mmc@1574 {
 + compatible = samsung,exynos7-dw-mshc-smu;

Is this controller backwards compatible with exynos5 ones?

 + /* The Clock nodes are ordered as per the usermanual. */

The clock

user manual

 + timer {
 + compatible = arm,armv8-timer;
 +   

Re: [PATCH 08/14] i2c: exynos5: Add Kconfig dependencies

[Olof Johansson]

On Wed, Aug 27, 2014 at 03:15:40PM +0530, Naveen Krishna Chatradhi wrote:
 The i2c-exynos5.c driver can be reused for the HSI2C controller
 on Exynos7 SoCs from Samsung.
 
 This patch adds the Kconfig dependency to choose i2c-exynos5.c
 for CONFIG_ARCH_EXYNOS7.
 
 Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
 To: linux-...@vger.kernel.org
 Cc: Wolfram Sang w...@the-dreams.de
 ---
  drivers/i2c/busses/Kconfig |2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
 index 2ac87fa..bd18fa6 100644
 --- a/drivers/i2c/busses/Kconfig
 +++ b/drivers/i2c/busses/Kconfig
 @@ -465,7 +465,7 @@ config I2C_EG20T
  
  config I2C_EXYNOS5
   tristate Exynos5 high-speed I2C driver
 - depends on ARCH_EXYNOS5  OF
 + depends on (ARCH_EXYNOS5 || ARCH_EXYNOS7)  OF

Ick, this will keep growing. Please use ARCH_EXYNOS instead. Yes,
this means you need to add it to the arm64 Kconfig and select it from
ARCH_EXYNOS7.



-Olof
--
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

Re: [PATCH 12/14] arm64: dts: add Exynos7 based Espresso board dts file

[Olof Johansson]

Hi,

On Wed, Aug 27, 2014 at 03:14:19PM +0530, Naveen Krishna Chatradhi wrote:
 This patch adds initial dts file for the Espresso board
 based on Exynos7 from Samsung.
 
 Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
 Cc: Rob Herring r...@kernel.org
 Cc: Catalin Marinas catalin.mari...@arm.com
 ---
  arch/arm64/boot/dts/Makefile |1 +
  arch/arm64/boot/dts/exynos7-espresso.dts |   69 
 ++
  2 files changed, 70 insertions(+)
  create mode 100644 arch/arm64/boot/dts/exynos7-espresso.dts
 
 diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
 index c52bdb0..d160de1 100644
 --- a/arch/arm64/boot/dts/Makefile
 +++ b/arch/arm64/boot/dts/Makefile
 @@ -1,5 +1,6 @@
  dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb foundation-v8.dtb
  dtb-$(CONFIG_ARCH_XGENE) += apm-mustang.dtb
 +dtb-$(CONFIG_ARCH_EXYNOS7) += exynos7-espresso.dtb

As mentioned on the dtsi patch, please create a subdirectory.

  targets += dtbs
  targets += $(dtb-y)
 diff --git a/arch/arm64/boot/dts/exynos7-espresso.dts 
 b/arch/arm64/boot/dts/exynos7-espresso.dts
 new file mode 100644
 index 000..e35e83c
 --- /dev/null
 +++ b/arch/arm64/boot/dts/exynos7-espresso.dts
 @@ -0,0 +1,69 @@
 +/*
 + * SAMSUNG Espresso board device tree source
 + *
 + * Copyright (c) 2014 Samsung Electronics Co., Ltd.
 + *   http://www.samsung.com
 + *
 + * This program is free software; you can redistribute it and/or modify
 + * it under the terms of the GNU General Public License version 2 as
 + * published by the Free Software Foundation.
 +*/
 +
 +/dts-v1/;
 +#include dt-bindings/gpio/gpio.h
 +#include exynos7.dtsi
 +
 +/ {
 + model = Samsung ESPRESSO board based on EXYNOS7;
 + compatible = samsung,espresso, samsung,exynos7;
 +
 + chosen {
 + bootargs = console=ttySAC2,115200n8 root=/dev/ram0 
 ramdisk=16384 initrd=0x4200,16M init=/linuxrc;

Having ramdisk bootargs like these in the upstream dts doesn't make much
sense. Configure your bootloader to pass them in instead.

You might want to specify the console through chosen instead, there's
been recent support added for that.

 +
 + memory@4000 {
 + device_type = memory;
 + reg = 0x4000 0xC000;
 + };
 +
 + mmc@1574 {
 + status = okay;
 + num-slots = 1;
 + broken-cd;
 + caps2-mmc-hs200-1_8v;
 + supports-highspeed;
 + non-removable;
 + card-detect-delay = 200;
 + clock-frequency = 8;
 + samsung,dw-mshc-ciu-div = 3;
 + samsung,dw-mshc-sdr-timing = 0 4;
 + samsung,dw-mshc-ddr-timing = 0 2;
 + pinctrl-names = default;
 + pinctrl-0 = sd0_clk sd0_cmd sd0_rdqs sd0_bus1 sd0_bus4 
 sd0_bus8;
 + bus-width = 8;
 +
 + slot@0 {
 + reg = 0;
 + bus-width = 8;
 + };

I thought the use of slot was deprecated. Why do you have it here?

Also, as mentioned by others elsewhere, please use references instead
of duplicating the structure here.


-Olof
--
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

Re: [PATCH 00/14] Support 64bit Cortex A57 based Exynos7 SoC

[Olof Johansson]

Naveen,

On Wed, Aug 27, 2014 at 03:14:16PM +0530, Naveen Krishna Chatradhi wrote:
 This patchset supports new Exynos7 Samsung SoC based on Cortex-A57.
 Exynos7 is a System-On-Chip (SoC) that is based on 64-bit
 ARMv8 RISC processor.

Your emails haven't threaded properly, so the series of patches are not
recognized as comments to the envelope (00/14) email. It makes it harder
to review them in order, and some mailers might not group them well.

 We tested these patches with the 
 arm64: dts: add dt-bindings/ symlink change posted @
 http://lists.infradead.org/pipermail/linux-arm-kernel/2014-January/224629.html

That means that these patches can't be picked up until a permanent
solution for that has gone in.


-Olof
--
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

Re: [PATCH 14/14] tty/serial: samsung: add support for exynos7

[Olof Johansson]

On Wed, Aug 27, 2014 at 03:16:35PM +0530, Naveen Krishna Chatradhi wrote:
 From: Alim Akhtar alim.akh...@samsung.com
 
 This patch enables upcoming exynos7 SoCs serial driver.
 This also modifies various dependencies for Kconfig
 
 Signed-off-by: Alim Akhtar alim.akh...@samsung.com
 Cc: Greg Kroah-Hartman gre...@linuxfoundation.org
 ---
  drivers/tty/serial/Kconfig   |6 +++---
  drivers/tty/serial/samsung.c |2 +-
  2 files changed, 4 insertions(+), 4 deletions(-)
 
 diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
 index 26cec64..f858d57 100644
 --- a/drivers/tty/serial/Kconfig
 +++ b/drivers/tty/serial/Kconfig
 @@ -220,7 +220,7 @@ config SERIAL_CLPS711X_CONSOLE
  
  config SERIAL_SAMSUNG
   tristate Samsung SoC serial support
 - depends on PLAT_SAMSUNG
 + depends on PLAT_SAMSUNG || ARCH_EXYNOS7

Same here, PLAT_SAMSUNG || ARCH_EXYNOS please.

 --- a/drivers/tty/serial/samsung.c
 +++ b/drivers/tty/serial/samsung.c
 @@ -1770,7 +1770,7 @@ static struct s3c24xx_serial_drv_data 
 s5pv210_serial_drv_data = {
  #define S5PV210_SERIAL_DRV_DATA  (kernel_ulong_t)NULL
  #endif
  
 -#if defined(CONFIG_ARCH_EXYNOS)
 +#if defined(CONFIG_ARCH_EXYNOS) || defined(CONFIG_ARCH_EXYNOS7)

And then this change won't be needed either.

  static struct s3c24xx_serial_drv_data exynos4210_serial_drv_data = {
   .info = (struct s3c24xx_uart_info) {
   .name   = Samsung Exynos4 UART,

-Olof
--
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

Re: [PATCH 13/14] arm64: exynos7: Enable ARMv8 based Exynos7 (SoC) support

[Olof Johansson]

On Wed, Aug 27, 2014 at 03:50:21PM +0100, Catalin Marinas wrote:
 On Wed, Aug 27, 2014 at 12:09:28PM +0100, Mark Rutland wrote:
  On Wed, Aug 27, 2014 at 10:44:20AM +0100, Naveen Krishna Chatradhi wrote:
   + select HAVE_SMP
  
  I may have missed something, but I didn't see any SMP support in this
  series.
 
 We don't even have HAVE_SMP defined for arm64 (just SMP, which is on in
 defconfig).
 
 In theory we don't need any specific SMP support for a new SoC as long
 as it uses a standard booting protocol (e.g. PSCI). But for whatever
 reason, I only received about four patches in this series, so can't see
 the rest.

Seems like about 9 of them made it to the list for me.


-Olof
--
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

Re: [PATCH 1/2] ARM: dts: Enable PMIC interrupts on ODROID

[Olof Johansson]

On Fri, Aug 22, 2014 at 3:39 AM, Kukjin Kim kgene@samsung.com wrote:
 Olof Johansson wrote:

 On Tue, Aug 19, 2014 at 12:15:41PM +0200, Javier Martinez Canillas wrote:
  Hello,
 
  On Tue, Aug 19, 2014 at 11:57 AM, Bartlomiej Zolnierkiewicz
  b.zolnier...@samsung.com wrote:
  
   IMHO they should go to upstream ASAP as they fix the boot for
   ODROID boards and they cannot break anything as they are limited
   to ODROID dts files.
  
 
  Agreed, this is definitely -rc material IMHO.

 Yes. Definitely.

 OK, agreed. Will apply into fixes.

Hi,

I'm about to send a batch up to Linus, and this was quick to apply
myself, so I've done so -- I'm interested in keeping this hardware
working since I have it in my test setup as the only EXYNOS4 machine.


-Olof
--
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

Re: [PATCH v2 0/4] Add Exynos4412 based Odroid X2 and U2/U3/U3+ support

[Olof Johansson]

ODROID-U3 has been broken in mainline for quite a while. Have patches
been posted for this already?

http://arm-soc.lixom.net/bootlogs/mainline/v3.17-rc1/odroidu3-arm-exynos_defconfig.html
 for one of the latest boots that failed.



-Olof

On Fri, Jul 18, 2014 at 8:40 AM, Przemyslaw Marczak
p.marc...@samsung.com wrote:
 Hello,


 On 06/30/2014 07:34 AM, Marek Szyprowski wrote:

 Hello,

 On 2014-06-25 15:26, Marek Szyprowski wrote:

 Hello,

 This is the second version of the initial patch series adding support
 for Exynos 4412 based Odroid X2 and U2/U3/U3+ boards and improving
 support for Odroid X.

 Complete USB support for Odroid U2/U3/U3+ still requires some fixes in
 Exynos4 USB2 Phy driver and clock driver for CLKOUT:
 http://thread.gmane.org/gmane.linux.kernel/1731843/
 http://www.spinics.net/lists/linux-usb/msg109587.html
 The above changes however don't affect Odroid DTS files, but without
 them, usb3503 hub is not yet functional.

 Support for audio codec will be posted separately by Sylwester Nawrocki
 soon. Support for HDMI video output will be also posted separately
 together with the required ExynosDRM-HDMI fixes.

 If one is interested in more complete and open-source Odroid board
 support, there are also patches for u-boot project:

 http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/188295/focus=188610


 Just to let everyone knows - updated Odroid patches for uboot has been
 posted in the following thread:
 http://www.mail-archive.com/u-boot@lists.denx.de/msg141234.html
 You can also download them here:
 http://patchwork.ozlabs.org/project/uboot/list/?submitter=23519

 Best regards


 Please follow the link to the new U-boot Odroid U3/X2 patches:

 http://www.mail-archive.com/u-boot@lists.denx.de/msg142507.html

 Regards,
 --
 Przemyslaw Marczak
 Samsung RD Institute Poland
 Samsung Electronics
 p.marc...@samsung.com
--
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

Re: [PATCH v2 0/4] Add Exynos4412 based Odroid X2 and U2/U3/U3+ support

[Olof Johansson]

On Tue, Aug 19, 2014 at 12:54 PM, Daniel Drake dr...@endlessm.com wrote:
 On Tue, Aug 19, 2014 at 8:40 PM, Olof Johansson o...@lixom.net wrote:
 ODROID-U3 has been broken in mainline for quite a while. Have patches
 been posted for this already?

 http://arm-soc.lixom.net/bootlogs/mainline/v3.17-rc1/odroidu3-arm-exynos_defconfig.html
  for one of the latest boots that failed.

 Yes, discussed in the thread titled [PATCH 1/2] ARM: dts: Enable PMIC
 interrupts on ODROID
 Those patches weren't important for boot at the time of submission,
 but it looks like something else changed (the max77686 driver?) that
 makes them now required.

Excellent, thanks. A bummer we didn't see this earlier, but let's get
the fix in asap.

-Olof
--
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

Re: [PATCH v5][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences

[Olof Johansson]

On Tue, Aug 05, 2014 at 02:43:10PM +0200, Bartlomiej Zolnierkiewicz wrote:
 From: Tomasz Figa t.f...@samsung.com
 
 Due to recent consolidation of Exynos suspend and cpuidle code, some
 parts of suspend and resume sequences are executed two times, once from
 exynos_pm_syscore_ops and then from exynos_cpu_pm_notifier() and thus it
 breaks suspend, at least on Exynos4-based boards. In addition, simple
 core power down from a cpuidle driver could, in case of CPU 0 could
 result in calling functions that are specific to suspend and deeper idle
 states.
 
 This patch fixes the issue by moving those operations outside the CPU PM
 notifier into suspend and AFTR code paths. This leads to a bit of code
 duplication, but allows additional code simplification, so in the end
 more code is removed than added.
 
 Fixes: 85f9f90808b4 (ARM: EXYNOS: Use the cpu_pm notifier for pm)
 Cc: Kukjin Kim kgene@samsung.com
 Cc: Arnd Bergmann a...@arndb.de
 Cc: Olof Johansson o...@lixom.net
 Cc: a...@kernel.org
 Signed-off-by: Tomasz Figa t.f...@samsung.com
 [b.zolnierkie: ported patch over current changes]
 [b.zolnierkie: fixed exynos_aftr_finisher() return value]
 Signed-off-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com

Applied to fixes.


-Olof
--
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

Re: [GIT PULL] Samsung 2nd cleanup for v3.17

[Olof Johansson]

On Thu, Jul 31, 2014 at 12:00 PM, Kukjin Kim kgene@samsung.com wrote:
 Hi Arnd, Olof

 One more pull-request. Sorry.

Hi Kukjin,

We're close enough to the merge window that this should be targeted to
3.18 instead.

Please send it as a cleanup once the merge window is over and we'll queue it up.


-Olof
--
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

Re: [GIT PULL] Samsung 2nd DT updates for v3.17

[Olof Johansson]

On Thu, Jul 31, 2014 at 11:20 AM, Kukjin Kim kgene@samsung.com wrote:
 The following changes since commit 6da287ad0266cca1fa8f88fb8b1c466e8164671f:

   Merge branch 'v3.17-next/power-exynos' into v3.17-next/dt-samsung-2
 (2014-07-29 06:09:42 +0900)

 are available in the git repository at:


   git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-dt-2

 for you to fetch changes up to a9408a6bba0de106d702fe5fa36fdc545116e9ab:

   ARM: dts: Add missing pinctrl for uart0/1 for exynos3250 (2014-07-30
 07:57:32 +0900)

These are mostly fixes and not new stuff, so I have merged them into
next/dt now.

-Olof
--
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

Re: [PATCH 0/3] ARM: EXYNOS: Fix Exynos5410 boot

[Olof Johansson]

Hi,

On Sun, Jul 27, 2014 at 5:39 PM, Kukjin Kim kgene@samsung.com wrote:
 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 tree.

 s/5410/5420/

 OK.

 
  Regards,
  Andreas
 
  Andreas Färber (3):
Documentation: devicetree: Document exynos5410 PMU
ARM: dts: exynos: Add PMU to Exynos5410
ARM: EXYNOS: Add support for Exynos5410 PMU
 
   Documentation/devicetree/bindings/arm/samsung/pmu.txt | 1 +
   arch/arm/boot/dts/exynos5410.dtsi | 5 +
   arch/arm/mach-exynos/exynos.c | 1 +
   3 files changed, 7 insertions(+)

 Andreas, thanks.

 I'll apply this whole series.

We're getting close to the merge window. I'd prefer not to have to
start reverting samsung code to recover from these regressions, so
please send this up very soon.


-Olof
--
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

Re: kgene's for-next branch broken, and boot regressions

[Olof Johansson]

On Sun, Jul 27, 2014 at 8:30 PM, Doug Anderson diand...@chromium.org wrote:
 Kukjin,

 On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim kgene@samsung.com 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 detect the breakage from dtb :(

 Could you add a make dtbs in there?

 Is there any chance you could get a boot farm on this, or somehow try
 to piggyback on Olof's or Kevin's boot farms (assuming they are
 willing to build/boot your branch on relevant hardware)?

I boot -next on the farm, and it had found the 5410 issues, which I
forwarded on to some of the relevant parties (but maybe not all). I
don't have any 5410 hardware so I couldn't bisect the problem and
narrow it down to a single patch. Hardware currently in there is 4412
(ODROID-U3), 5250 (Arndale and Snow), 5420 and 5800 (Pit/Pi). I have a
6410-based board that I have not yet hooked up.

I also boot arm-soc's for-next branch, so as soon as we merge
something in I'll notice breakage, if it's somehow masked by other
parts of linux-next (i.e. dependent but not described driver changes,
etc).


-Olof
--
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

Re: kgene's for-next branch broken, and boot regressions

[Olof Johansson]

On Sun, Jul 27, 2014 at 8:44 PM, Olof Johansson o...@lixom.net wrote:
 On Sun, Jul 27, 2014 at 8:30 PM, Doug Anderson diand...@chromium.org wrote:
 Kukjin,

 On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim kgene@samsung.com 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 detect the breakage from dtb :(

 Could you add a make dtbs in there?

 Is there any chance you could get a boot farm on this, or somehow try
 to piggyback on Olof's or Kevin's boot farms (assuming they are
 willing to build/boot your branch on relevant hardware)?

 I boot -next on the farm, and it had found the 5410 issues, which I
 forwarded on to some of the relevant parties (but maybe not all). I
 don't have any 5410 hardware so I couldn't bisect the problem and
 narrow it down to a single patch.


Obviously those two sentences are contradictory, and it was indeed
Kevin that found the issues with his boards, not me.


-Olof
--
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

Re: arm-soc boot: 64 boots: 62 pass, 2 fail (v3.16-rc5-727-gac8047e)

[Olof Johansson]

Kukjin,

Looks like the last set of branches from you regressed 5410. Since I
don't have that hardware myself I can't bisect down to what patch is
causing it.

Can you please try to sort out at your end and send a fixup patch? I
think Kevin is out, I haven't seen much from him lately.


-Olof

On Sat, Jul 19, 2014 at 4:35 PM, Kevin's boot bot khil...@linaro.org wrote:

 Full logs here: http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-727-gac8047e

 Tree/Branch: arm-soc
 Git describe: v3.16-rc5-727-gac8047e
 Failed boot tests
 =
  exynos5410-smdk5410: FAIL:arm-multi_v7_defconfig
   
 http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-727-gac8047e/arm-multi_v7_defconfig/boot-exynos5410-smdk5410.html
  exynos5410-smdk5410: FAIL:arm-exynos_defconfig
   
 http://armcloud.us/kernel-ci/arm-soc/v3.16-rc5-727-gac8047e/arm-exynos_defconfig/boot-exynos5410-smdk5410.html

 Full Report
 ===

 arm-davinci_all_defconfig
 -
  legacy,dm365evm 0 min 18.5 sec: PASS
da850-evm 0 min 16.8 sec: PASS

 arm-tegra_defconfig
 ---
  tegra124-jetson-tk1 0 min 18.6 sec: PASS
   tegra30-beaver 0 min 18.2 sec: PASS

 arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y
 
  tegra124-jetson-tk1 0 min 18.6 sec: PASS
   armada-xp-openblocks-ax3-4 0 min 24.6 sec: PASS
   omap5-uevm 2 min  0.6 sec: PASS  (Warnings: 1)
sun7i-a20-cubieboard2 0 min 13.7 sec: PASS

 arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y
 --
   armada-xp-openblocks-ax3-4 0 min 24.2 sec: PASS
   armada-370-mirabox 0 min 21.1 sec: PASS

 arm-omap2plus_defconfig
 ---
legacy,3730xm 0 min 42.0 sec: PASS
 am335x-boneblack 0 min 23.2 sec: PASS
  omap3-beagle-xm 0 min 51.5 sec: PASS
legacy,3530beagle 0 min 34.9 sec: PASS  (Warnings: 1)
  omap4-panda 0 min 51.8 sec: PASS
 omap3-overo-tobi 0 min 23.9 sec: PASS
  am335x-bone 0 min 24.9 sec: PASS
   omap3-overo-storm-tobi 0 min 26.0 sec: PASS
   omap5-uevm 0 min 57.6 sec: PASS  (Warnings: 1)
   omap3-n900 0 min 18.0 sec: PASS
  legacy,n900 0 min 16.8 sec: PASS  (Warnings: 1)
   omap4-panda-es 0 min 56.6 sec: PASS  (Warnings: 1)
 legacy,3730storm 0 min 20.7 sec: PASS
 legacy,3530overo 0 min 22.5 sec: PASS  (Warnings: 1)

 arm-multi_v7_defconfig
 --
   imx6dl-wandboard,wand-solo 0 min 16.2 sec: PASS
 am335x-boneblack 0 min 22.9 sec: PASS
sun7i-a20-cubieboard2 0 min 13.8 sec: PASS
 sun4i-a10-cubieboard 0 min 18.2 sec: PASS
  exynos5410-smdk5410 0 min 49.0 sec: FAIL
  am335x-bone 0 min 24.5 sec: PASS
  tegra124-jetson-tk1 0 min 18.7 sec: PASS
   armada-370-mirabox 0 min 22.4 sec: PASS
  omap4-panda 0 min 58.5 sec: PASS
  imx6q-wandboard 0 min 15.1 sec: PASS
   imx6dl-wandboard,wand-dual 0 min 15.9 sec: PASS
 ste-snowball 1 min 33.8 sec: PASS
   tegra30-beaver 0 min 24.3 sec: PASS
   omap3-n900 0 min 16.5 sec: PASS
 qcom-apq8074-dragonboard 0 min 20.2 sec: PASS
  bcm28155-ap 0 min 28.4 sec: PASS
 omap3-overo-tobi 0 min 26.0 sec: PASS
   omap3-overo-storm-tobi 0 min 24.5 sec: PASS
  omap3-beagle-xm 0 min 55.9 sec: PASS
  exynos5420-arndale-octa 0 min 34.9 sec: PASS
   armada-xp-openblocks-ax3-4 0 min 25.6 sec: PASS
   omap5-uevm 2 min  1.2 sec: PASS  (Warnings: 1)
   omap4-panda-es 0 min 53.4 sec: PASS  (Warnings: 1)
   exynos5250-arndale 0 min 37.8 sec: PASS

 arm-sunxi_defconfig
 ---
sun7i-a20-cubieboard2 0 min 12.3 sec: PASS
 sun4i-a10-cubieboard 0 min 12.2 sec: PASS

 arm-qcom_defconfig
 --
 qcom-apq8074-dragonboard 0 min 18.0 sec: PASS

 arm-bcm_defconfig
 -
  bcm28155-ap 0 min 23.6 sec: PASS

 arm-exynos_defconfig
 
  exynos5420-arndale-octa 0 min 30.8 sec: PASS
   exynos5250-arndale 0 min 31.4 sec: PASS
  exynos5410-smdk5410 0 min 48.2 sec: FAIL

 arm-imx_v6_v7_defconfig
 ---
   imx6dl-wandboard,wand-dual 

Re: [GIT PULL 1/5] Samsung non-critical-fixes for v3.17

[Olof Johansson]

On Sat, Jul 19, 2014 at 09:51:45AM +0900, Kukjin Kim wrote:
 The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
 
   Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)
 
 are available in the git repository at:
 

 git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/fixes-for-3.17
 
 for you to fetch changes up to 042b687f880adcca77847688aac35e2e16927944:
 
   ARM: EXYNOS: Fix build breakge with PM_SLEEP=n (2014-07-19
 04:45:02 +0900)
 
 
 Samsung non critical fixes for v3.17
 - update exynos_defconfig for remove outdated configs and
 enable most of the configs used on latest exynos platforms
 - fix build breakge for exynos_defconfig with PM_SLEEP=n

Hi,

We now separate out defconfigs (as you might have noticed if you looked
at our tree). I don't see any dependencies between these changes and
the rest so I'll cherry-pick the patches into fixes-non-critical (for
the build fix) and defconfig for that patch.

-Olof

--
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

Re: [GIT PULL 2/5] Samsung cleanup for v3.17

[Olof Johansson]

On Sat, Jul 19, 2014 at 09:52:09AM +0900, Kukjin Kim wrote:
 Note that this is based on 3.16-rc5 because of dependency with
 previous samsung fixes already merged in mainline during -rc.
 
 The following changes since commit 1795cd9b3a91d4b5473c97f491d63892442212ab:
 
   Linux 3.16-rc5 (2014-07-13 14:04:33 -0700)
 
 are available in the git repository at:
 

 git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
 tags/samsung-cleanup
 
 for you to fetch changes up to fce9e5bb25264153f9f002eada41757118d25ba9:
 
   ARM: EXYNOS: Add support for mapping PMU base address via DT
 (2014-07-15 08:40:32 +0900)

Thanks, merged.


-Olof
--
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