From: Krzysztof Kozlowski <krzk@kernel.org> Date: 2016-12-17 19:32:25
Hi,
After our discussions about not-breaking out-of-tree DTB with SCU
change in DeviceTree, I prepared an updated pull request without
the questioned changes.
Ten days ago I prepared a tag, pushed it... and apparently forgot to send pull
request. At least, I don't have such email in my outbox. Dunno.
So let's send it now, better late then never. With just few commits (without
the DT SCU changes). These were sitting in the next for very long.
Best regards,
Krzysztof
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-soc-4.10-2
for you to fetch changes up to da6b21e97e39d42f90ab490ce7b54a0fe2c3fe35:
ARM: Drop fixed 200 Hz timer requirement from Samsung platforms (2016-12-07 18:42:11 +0200)
----------------------------------------------------------------
Samsung mach/soc update for v4.10:
1. Minor cleanup in smp_operations.
2. Another step in switching s3c24xx to new DMA API.
3. Drop fixed requirement for HZ=200 on Samsung platforms.
----------------------------------------------------------------
Krzysztof Kozlowski (1):
ARM: Drop fixed 200 Hz timer requirement from Samsung platforms
Pankaj Dubey (1):
ARM: EXYNOS: Remove smp_init_cpus hook from platsmp.c
Sylwester Nawrocki (1):
ARM: S3C24XX: Add DMA slave maps for remaining s3c24xx SoCs
arch/arm/Kconfig | 3 +-
arch/arm/mach-exynos/platsmp.c | 31 -----------------
arch/arm/mach-s3c24xx/common.c | 76 ++++++++++++++++++++++++++++++++++++++++++
3 files changed, 77 insertions(+), 33 deletions(-)
From: Krzysztof Kozlowski <krzk@kernel.org> Date: 2016-12-30 15:53:20
On Sat, Dec 17, 2016 at 09:32:12PM +0200, Krzysztof Kozlowski wrote:
Hi,
After our discussions about not-breaking out-of-tree DTB with SCU
change in DeviceTree, I prepared an updated pull request without
the questioned changes.
Ten days ago I prepared a tag, pushed it... and apparently forgot to send pull
request. At least, I don't have such email in my outbox. Dunno.
So let's send it now, better late then never. With just few commits (without
the DT SCU changes). These were sitting in the next for very long.
Any comments on this? I guess it won't come as late-late-4.10, so can
you pull it for v4.11?
Best regards,
Krzysztof
Best regards,
Krzysztof
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-soc-4.10-2
for you to fetch changes up to da6b21e97e39d42f90ab490ce7b54a0fe2c3fe35:
ARM: Drop fixed 200 Hz timer requirement from Samsung platforms (2016-12-07 18:42:11 +0200)
----------------------------------------------------------------
Samsung mach/soc update for v4.10:
1. Minor cleanup in smp_operations.
2. Another step in switching s3c24xx to new DMA API.
3. Drop fixed requirement for HZ=200 on Samsung platforms.
----------------------------------------------------------------
Krzysztof Kozlowski (1):
ARM: Drop fixed 200 Hz timer requirement from Samsung platforms
Pankaj Dubey (1):
ARM: EXYNOS: Remove smp_init_cpus hook from platsmp.c
Sylwester Nawrocki (1):
ARM: S3C24XX: Add DMA slave maps for remaining s3c24xx SoCs
arch/arm/Kconfig | 3 +-
arch/arm/mach-exynos/platsmp.c | 31 -----------------
arch/arm/mach-s3c24xx/common.c | 76 ++++++++++++++++++++++++++++++++++++++++++
3 files changed, 77 insertions(+), 33 deletions(-)
We need this patch in v4.10 to avoid possible I2S and MMC regressions
on selected s3c24xx SoC, since the DMA clients are already modified.
If the patch goes in only for v4.11 it would be good to mark it for
inclusion in v4.10 stable kernels.
--
Thanks,
Sylwester
We need this patch in v4.10 to avoid possible I2S and MMC regressions
on selected s3c24xx SoC, since the DMA clients are already modified.
If the patch goes in only for v4.11 it would be good to mark it for
inclusion in v4.10 stable kernels.
You didn't mention any strict dependencies when sending this patch...
What do you mean by "needing patch in v4.10"? Is the code already
not bisectable? Already broken?
Best regards,
Krzysztof
We need this patch in v4.10 to avoid possible I2S and MMC regressions
on selected s3c24xx SoC, since the DMA clients are already modified.
If the patch goes in only for v4.11 it would be good to mark it for
inclusion in v4.10 stable kernels.
You didn't mention any strict dependencies when sending this patch...
What do you mean by "needing patch in v4.10"? Is the code already
not bisectable? Already broken?
Yes, unfortunately on s3c2410, s3c2412 and s3c2443. I didn't notice
when sending patches for the s3c24xx-iis and s3c2440-sdi drivers
the dma_slave maps were only added for s3c2440 (commit 34681d84a0f7cc2
dmaengine: s3c24xx: Add dma_slave_map for s3c2440 devices) and not for
remaining SoCs covered by these DMA client drivers.
--
Thanks,
Sylwester
We need this patch in v4.10 to avoid possible I2S and MMC regressions
on selected s3c24xx SoC, since the DMA clients are already modified.
If the patch goes in only for v4.11 it would be good to mark it for
inclusion in v4.10 stable kernels.
You didn't mention any strict dependencies when sending this patch...
What do you mean by "needing patch in v4.10"? Is the code already
not bisectable? Already broken?
Yes, unfortunately on s3c2410, s3c2412 and s3c2443. I didn't notice
when sending patches for the s3c24xx-iis and s3c2440-sdi drivers
the dma_slave maps were only added for s3c2440 (commit 34681d84a0f7cc2
dmaengine: s3c24xx: Add dma_slave_map for s3c2440 devices) and not for
remaining SoCs covered by these DMA client drivers.
Okay, so either entire pull goes into v4.10 or I will need a resend of
this one patch with a little bit extended message why this is a v4.10
fix.
BR,
Krzysztof
On Saturday, December 17, 2016 9:32:12 PM CET Krzysztof Kozlowski wrote:
After our discussions about not-breaking out-of-tree DTB with SCU
change in DeviceTree, I prepared an updated pull request without
the questioned changes.
Ten days ago I prepared a tag, pushed it... and apparently forgot to send pull
request. At least, I don't have such email in my outbox. Dunno.
So let's send it now, better late then never. With just few commits (without
the DT SCU changes). These were sitting in the next for very long.
Sorry for the delay. The patches in here are all straightforward, so
I'm applying them for fixes now.
Arnd