On Tuesday 29 December 2015 15:03:17 Krzysztof Kozlowski wrote:
> Samsung DeviceTree updates and improvements for 4.5
> 1. eMMC/SDIO minor fixes usage of bindings on Snow and Peach
>Chromebooks.
> 2. Remove FIMD from Odroid XU3-family because on XU3 it cannot be used
>yet and on XU3-Lite
On Monday 28 December 2015 10:54:10 Krzysztof Kozlowski wrote:
> On 18.12.2015 23:46, Arnd Bergmann wrote:
> > I got one randconfig build that failed to compile plat-samsung/pm-debug.c
> > on s3c64xx:
> >
> > In file included from arch/arm/plat-samsung/pm-debug.c:27:0
On Monday 28 December 2015 10:02:57 Krzysztof Kozlowski wrote:
> On 18.12.2015 23:45, Arnd Bergmann wrote:
> > For a long time, gcc has warned about odd configurations on s3c64xx:
> >
> > In file included from arch/arm/plat-samsung/pm.c:34:0:
> > arch/arm/mach-s3c64xx/
ings have become easier now that it's only
s3c24xx
and s3c64xx that use them at all, so I've tried to rearrange the definitions to
make it more obvious what is going on.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
This fixes a very old and harmless warning, please apply to a cleanup bran
declaration
of function 'udelay' [-Werror=implicit-function-declaration]
udelay(10);
I have not investigated why this does not show up much more often, I
guess the headers are usually included from elsewhere, but adding
explicit #include statements is an obvious fix.
Signed-off-by: Arnd Bergmann
On Wednesday 02 December 2015 01:04:05 Kukjin Kim wrote:
> Krzysztof Kozlowski wrote:
> >
> Hi Krzysztof,
>
> Looks good to me, but I have no other fixes in my tree so this would be sent
> to
> out arm-soc directly
>
> Hi Arnd, Olof, Kevin,
> Please pull this for v4.4.
>
Pulled into fixes
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
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 su
and they
can only be built as loadable modules if V4L2 or any other of the
dependencies itself is a module.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
diff --git a/drivers/media/platform/exynos4-is/Kconfig
b/drivers/media/platform/exynos4-is/Kconfig
index 40423c6c5324..57d42c6172c5
On Tuesday 01 December 2015 09:34:18 Krzysztof Kozlowski wrote:
> On 26.11.2015 01:06, Arnd Bergmann wrote:
> > diff --git a/arch/arm/plat-samsung/Kconfig b/arch/arm/plat-samsung/Kconfig
> > index 57729b915003..83697414bfa0 100644
> > --- a/arch/arm/plat-samsung/Kconfig
&g
On Tuesday 01 December 2015 09:24:24 Krzysztof Kozlowski wrote:
> > +static struct platform_driver smartq_driver = {
> > + .driver = {
> > + .name = "smartq-audio",
> > + .owner = THIS_MODULE,
>
> The owner should not be needed (coccicheck should also complain). Rest
>
After all preparation work is done, we can finally move the Kconfig
option for s3c64xx into ARCH_MULTIPLATFORM. This implies allowing
SAMSUNG_ATAGS for multiplatform again, but now disallowing the
ADC driver below it, as that still has dependencies on header files.
Signed-off-by: Arnd Bergmann
ed on real hardware to see if it works.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/arm/Kconfig | 1 +
arch/arm/mach-s3c64xx/common.c | 1 +
arch/arm/mach-s3c64xx/dev-uart.c | 1 +
arch/arm/mach-s3c64xx/include/mac
S3C_ADC is only available on machines that don't do ARCH_MULTIPLATFORM,
so changing the 'select' into 'depends on' here helps us move to
ARCH_MULTIPLATFORM without introducing regressions.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Acked-by: Dmitry Torokhov <dmitry.torok...@
resources in the opposite order
and pass the platform data in the adc device node.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/arm/mach-s3c64xx/mach-mini6410.c | 3 +--
arch/arm/mach-s3c64xx/mach-real6410.c | 3 +--
arch/arm/mach-s3c64xx/mach-sm
On Wednesday 25 November 2015 16:31:14 Mark Brown wrote:
> On Wed, Nov 25, 2015 at 05:06:45PM +0100, Arnd Bergmann wrote:
> > I've posted the series before and we got a few people to test it
> > the last time, though I think the touchscreen portion is still
> > untested.
>
module_platform_driver
and register the platform device using platform_device_register_simple
and register the gpios through the gpiod API.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Acked-by: Mark Brown <broo...@kernel.org>
---
arch/arm/mach-s3c64xx/mach-smartq.c | 13 +++
sound/soc/samsung/sma
ght happen.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/arm/plat-samsung/Kconfig | 3 +++
arch/arm/plat-samsung/Makefile | 2 ++
{drivers/gpio => arch/arm/plat-samsung}/gpio-samsung.c | 0
drivers/gpio/Kconfig
The uart on s3c64xx is essentially the same as on s3c24xx,
so we can share a single assembler file. However, the addresses
are different, and we need to add the respective Kconfig magic
to get the right addresses.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/arm/Kconfig
can build them into a combined kernel.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
arch/arm/mach-s3c64xx/common.c | 4 ++--
arch/arm/mach-s3c64xx/cpuidle.c | 5 -
arch/arm/mach-s3c64xx/irq-pm.c | 2 +-
arch/arm/mach-s3c64xx/mach-crag6410-mo
uses the IS_REACHABLE() that is
going to be introduced in the linux-media tree, please
comment this out for testing.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Acked-by: Dmitry Torokhov <dmitry.torok...@gmail.com>
---
.../devicetree/bindings/arm/samsung/exynos-adc.txt | 3 +
dri
On Wednesday 18 November 2015 11:13:18 Krzysztof Kozlowski wrote:
>
> I also tested entire patchset on Exynos4412/Trats2 board (custom kernel
> with audio working) for regressions and it worked fine. However, since
> this was not a S3C24xx/S3C64xx board, I don't find that testing
> sufficient for
On Wednesday 18 November 2015 13:43:27 Krzysztof Kozlowski wrote:
> On 18.11.2015 00:48, Arnd Bergmann wrote:
> > struct platform_device s3c64xx_device_spi0 = {
> > @@ -1135,11 +1133,13 @@ void __init s3c64xx_spi0_set_platdata(int
> > (*cfg_gpio)(void), int src_clk_
The s3c64xx platform data already contains a pointer to the
DMA filter function, but not to the associated data.
This simplifies the code and makes it more generic by
passing the data along with the filter function like
we do for other drivers.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
ut
gets cast to resource_size_t so we can pass it as a resource, and it
then gets converted back to a pointer. In contrast, the data we pass
for s3c24xx is an index into a device specific table, and we artificially
convert that into a pointer for the filter function.
Signed-off-by: Arnd Bergmann <a...@arn
ently it should have been used by mach-jive.c, but that
never happened. My patch at this point leaves the current state
unchanged, we can decide whether to fix or delete the jive
driver and s3c2412-i2s another time.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Reviewed-by: Krzysztof Kozlowsk
ently it should have been used by mach-jive.c, but that
never happened. My patch at this point leaves the current state
unchanged, we can decide whether to fix or delete the jive
driver and s3c2412-i2s another time.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Reviewed-by: Krzysztof Kozlowsk
On Tuesday 17 November 2015 16:54:16 Arnd Bergmann wrote:
> +#include
>
My randconfig test setup has now found the typo above. Resending the
fixed version.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a m
in thet same system at runtime, but is nonetheless ugly.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Reviewed-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
---
v2 changes:
v2: avoid possibly NULL pdata
diff --git a/arch/arm/mach-s3c64xx/dev-audio.c
b/arch/arm/mach-s3c64xx
in thet same system at runtime, but is nonetheless ugly.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Reviewed-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
---
Same patch as the previous submission that did not apply. I don't
know what went wrong, but I have rebased on top o
ut
gets cast to resource_size_t so we can pass it as a resource, and it
then gets converted back to a pointer. In contrast, the data we pass
for s3c24xx is an index into a device specific table, and we artificially
convert that into a pointer for the filter function.
Signed-off-by: Arnd Bergmann <a...@a
ently it should have been used by mach-jive.c, but that
never happened. My patch at this point leaves the current state
unchanged, we can decide whether to fix or delete the jive
driver and s3c2412-i2s another time.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
v2: check for NULL pdata
in thet same system at runtime, but is nonetheless ugly.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
v2: avoid possibly NULL pdata
diff --git a/arch/arm/mach-s3c64xx/dev-audio.c
b/arch/arm/mach-s3c64xx/dev-audio.c
index 9a42736ef4ac..b57783371d52 100644
--- a/arch/arm/mach-s3c64
On Monday 16 November 2015 17:00:21 Arnd Bergmann wrote:
> The s3c64xx platform data already contains a pointer to the
> DMA filter function, but not to the associated data.
>
> This simplifies the code and makes it more generic by
> passing the data along with the filter functi
The s3c64xx platform data already contains a pointer to the
DMA filter function, but not to the associated data.
This simplifies the code and makes it more generic by
passing the data along with the filter function like
we do for other drivers.
Signed-off-by: Arnd Bergmann <a...@arndb
, NULL)
This removes the #ifdef and instead marks the functions as
__maybe_unused, which does the right thing in all cases and
also looks nicer.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Fixes: ("drm/exynos: add pm_runtime to Mixer")
diff --git a/drivers/gpu/drm/exynos/e
]
This removes them too.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
Fixes: 186ba87a6e31 ("drm/exynos: add pm_runtime to DECON 5433")
diff --git a/drivers/gpu/drm/exynos/exynos5433_drm_decon.c
b/drivers/gpu/drm/exynos/exynos5433_drm_decon.c
index edfd6e390ef7..2ac1d4d14368 100644
--- a
On Tuesday 17 November 2015 09:45:26 Krzysztof Kozlowski wrote:
> On 14.11.2015 02:24, Arnd Bergmann wrote:
> > diff --git a/sound/soc/samsung/i2s.c b/sound/soc/samsung/i2s.c
> > index 0945b5de39e7..5a4133b6e6a6 100644
> > --- a/sound/soc/samsung/i2s.c
> > ++
On Tuesday 17 November 2015 10:16:36 Krzysztof Kozlowski wrote:
> On 14.11.2015 02:22, Arnd Bergmann wrote:
> > ARM64 allmodconfig produces a bunch of warnings when building the
> > samsung ASoC code:
> >
> > sound/soc/samsung/dmaengine.c: In function 'samsung_asoc_in
On Tuesday 17 November 2015 10:57:48 Krzysztof Kozlowski wrote:
> On 17.11.2015 07:17, Arnd Bergmann wrote:
> > On Monday 16 November 2015 23:36:42 Rafael J. Wysocki wrote:
> >>
> >> This should go in through the Samsung tree, so I'll leave it for them to
>
On Tuesday 17 November 2015 10:36:46 Krzysztof Kozlowski wrote:
> On 14.11.2015 02:23, Arnd Bergmann wrote:
> > This is a minor cleanup to make the s3c2412-i2s and s3c24xx-i2s
> > drivers independent of the mach/dma.h header file and to allow
> > removing the dependency on t
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
I send this one ages ago but never got a reaction. I rebased it several
times when the driver changed, and it still seems to be needed.
diff --git a/drivers/gpu/drm/exynos/exynos7_drm_decon.c
b/drivers/gpu/drm/exynos/exynos7_drm_decon.c
index
The s3c64xx platform data already contains a pointer to the
DMA filter function, but not to the associated data.
This simplifies the code and makes it more generic by
passing the data along with the filter function like
we do for other drivers.
Signed-off-by: Arnd Bergmann <a...@arndb
On Monday 16 November 2015 09:00:45 Mauro Carvalho Chehab wrote:
> Let's not mix platform_data headers with the core headers. Instead, let's
> create a subdir at linux/platform_data and move the headers to that
> common place, adding it to MAINTAINERS.
>
Acked-by: Arnd Bergmann &l
_csi2.h include/media/sh_vou.h \
> include/media/si476x.h include/media/soc_mediabus.h \
> include/media/tea575x.h include/media/drv-intf/
>
Acked-by: Arnd Bergmann <a...@arndb.de>
I probably would have left soc_mediabus.h where it is, but I can
see there are reasons to
On Monday 16 November 2015 23:36:42 Rafael J. Wysocki wrote:
>
> This should go in through the Samsung tree, so I'll leave it for them to pick
> it up (at least for the time being).
Ok, fair enough. Kukjin or Krzysztof, can you pick this up?
Arnd
--
To unsubscribe from this list: send
.
This removes the __init annotation from s3c2410_plls_add as well as the
__initdata section annotations from s3c2440_plls_12 and s3c2440_plls_169344,
which in turn are referenced from s3c2410_plls_add.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
It would be nice to get this merged t
in thet same system at runtime, but is nonetheless ugly.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
diff --git a/arch/arm/mach-s3c64xx/dev-audio.c
b/arch/arm/mach-s3c64xx/dev-audio.c
index 9a42736ef4ac..b57783371d52 100644
--- a/arch/arm/mach-s3c64xx/dev-audio.c
+++ b/arch/arm/mach-s
ently it should have been used by mach-jive.c, but that
never happened. My patch at this point leaves the current state
unchanged, we can decide whether to fix or delete the jive
driver and s3c2412-i2s another time.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
diff --git a/arch/arm/plat-sams
ut
gets cast to resource_size_t so we can pass it as a resource, and it
then gets converted back to a pointer. In contrast, the data we pass
for s3c24xx is an index into a device specific table, and we artificially
convert that into a pointer for the filter function.
Signed-off-by: Arnd Bergmann <a...@arndb.
On Friday 13 November 2015 17:13:41 Mauro Carvalho Chehab wrote:
> Em Wed, 11 Nov 2015 21:26:31 +0100
> Arnd Bergmann <a...@arndb.de> escreveu:
>
> include/media/{ => drv-intf}/cx2341x.h | 0
> include/media/{ => drv-intf}/cx25840.h
On Wednesday 11 November 2015 15:14:48 Mauro Carvalho Chehab wrote:
> rename include/media/{ => platform}/exynos-fimc.h (100%)
> rename include/media/{ => platform}/mmp-camera.h (100%)
> rename include/media/{ => platform}/omap1_camera.h (100%)
> rename include/media/{ => platform}/omap4iss.h
On Monday 09 November 2015 22:09:26 Laurent Pinchart wrote:
> Hi Arnd,
>
> Thank you for the patch.
>
> On Thursday 17 September 2015 23:19:40 Arnd Bergmann wrote:
> > C libraries with 64-bit time_t use an incompatible format for
> > struct omap3isp_stat_data. T
On Tuesday 03 November 2015 09:40:02 Daniel Lezcano wrote:
> On 11/03/2015 01:59 AM, Krzysztof Kozlowski wrote:
> > On 03.11.2015 09:30, Krzysztof Kozlowski wrote:
> >> On 02.11.2015 21:56, Daniel Lezcano wrote:
> >>> Let the platform's Kconfig to select the clock instead of having a reverse
> >>>
On Saturday 17 October 2015 08:30:34 Kukjin Kim wrote:
> Hello Arnd, Olof, Kevin
>
> Here is 2nd Samsung fixes for v4.3 and it is including fix of exynos
> thermal driver with exynos thermal driver maintainer(Lukasz)'s ack.
>
> Please pull.
>
> Thanks,
> Kukjin
>
>
> The following changes
On Monday 19 October 2015 16:18:35 Alim Akhtar wrote:
> Spam Status: CRM114
> CONFIG_BLK_DEV_RAM_SIZE is currently set to 8K, which is a bit on the
> smaller side, lets bump it up to 64K so that a bigger RAM_DISK can
> be used with defconfig.
>
> Signed-off-by: Alim Akhtar
On Tuesday 13 October 2015 04:59:27 Kukjin Kim wrote:
> Samsung DT updates for v4.4
>
> - New board support
> : add exynos5250-snow-rev5 DT file to support Snow Rev5+ board
> : add exynos5422-odroidxu4 DT file to support Odroid XU4 board
> : split exynos5422-odroidxu3-audio DT file from
On Friday 09 October 2015 09:14:33 Anand Moon wrote:
> As long as we use correct exynos5422-odroidxu4.dtb is used in the
> boot.scr/boot.ini ethernet come up,
> build and tested using CONFIG_USB_RTL8152=m using multi_v7_defconfig.
>
> Not sure what is the policy for NFS booting.
>
> Do you want
On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>
> > I realize that building things as modules is a hassle, it is so for
> > some things more than for others, so I keep asking the question
> > to everyone to find out what a good balance is to make as much as
> > possible modules without
On Thursday 08 October 2015 03:48:36 Anand Moon wrote:
> diff --git a/arch/arm/configs/exynos_defconfig
> b/arch/arm/configs/exynos_defconfig
> index 1ff2bfa..5d1937b 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -61,6 +61,7 @@ CONFIG_BLK_DEV_DM=y
On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> On 08.10.2015 16:41, Arnd Bergmann wrote:
> > On Thursday 08 October 2015 03:48:36 Anand Moon wrote:
> >> diff --git a/arch/arm/configs/exynos_defconfig
> >> b/arch/arm/configs/exynos_defconfig
> &g
On Thursday 08 October 2015 11:27:13 Sjoerd Simons wrote:
> On Thu, 2015-10-08 at 10:37 +0200, Arnd Bergmann wrote:
> > On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> > > On 08.10.2015 16:41, Arnd Bergmann wrote:
> > > > On Thursday 08 October
On Tuesday 06 October 2015 12:44:54 Pavel Fedin wrote:
> Hello!
>
> > My feeling is that is shouldn't be keyed off the presence of the device in
> > DT
> > though. Maybe we can find a way that allows you to put the device into DT
> > but not have it used by default unless the user explicitly
On Tuesday 06 October 2015 07:57:33 Kukjin Kim wrote:
> Samsung fixes for v4.3
>
> - fix invalid clock used for FIMD IOMMU
> - fix thermal boot issue smdk5250-smdk5250
> - fix S2R on exynos4412 trats2 boards
> - fix LEDs on exynos5422-odroidxu3-common
> - fix booting of all 8 cores on exynos542x
On Monday 05 October 2015 12:24:40 Sylwester Nawrocki wrote:
> On 03/10/15 00:25, Arnd Bergmann wrote:
> > On Thursday 01 October 2015 19:17:27 Mauro Carvalho Chehab wrote:
> >> > diff --git a/drivers/media/platform/exynos4-is/mipi-csis.c
> >> > b/drivers/medi
On Thursday 01 October 2015 19:17:27 Mauro Carvalho Chehab wrote:
> diff --git a/drivers/media/platform/exynos4-is/mipi-csis.c
> b/drivers/media/platform/exynos4-is/mipi-csis.c
> index d74e1bec3d86..4b85105dc159 100644
> --- a/drivers/media/platform/exynos4-is/mipi-csis.c
> +++
On Friday 18 September 2015 09:18:45 Hans Verkuil wrote:
> Hi Arnd,
>
> Thanks once again for working on this! Unfortunately, this approach won't
> work, see my comments below.
>
> BTW, I would expect to see compile errors when compiling for 32 bit. Did
> you try that?
I only tested on 32-bit,
On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
> Ah, OK. Got it.
>
> I think this is dependent on the upcoming media workshop next month. If we
> decide to redesign v4l2_buffer anyway, then we can avoid timeval completely.
> And the only place where we would need to convert it in the
On Friday 18 September 2015 11:52:28 Hans Verkuil wrote:
> On 09/18/15 11:43, Arnd Bergmann wrote:
> > On Friday 18 September 2015 11:27:40 Hans Verkuil wrote:
> >> Ah, OK. Got it.
> >>
> >> I think this is dependent on the upcoming media workshop next
On Friday 18 September 2015 11:49:50 Hans Verkuil wrote:
> *If* the conversion takes place only in v4l2-ioctl.c, then it makes sense
> have these structs + ioctls moved to v4l2-ioctl.h.
Ok.
> I noticed that v4l2-compat-ioctl32.c wasn't changed. Is that right? I have
> unfortunately no time to
code.
Fortunately, the command code includes the size of the structure,
so the difference gets handled automatically.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/platform/omap3isp/isph3a_aewb.c | 2 ++
drivers/media/platform/omap3isp/isph3a_af.c | 2 ++
drivers/media/pl
not added support for the new binary layout of v4l2_timeval
to v4l2-compat-ioctl32 yet, that is something I can do when the
basic approach has been agreed on.
Arnd
Arnd Bergmann (9):
[media] dvb: use ktime_t for internal timeout
[media] dvb: remove unused systime() function
[media] dvb
for both
32-bit and 64-bit time_t. This patch should have no impact on generated
code in either user space or kernel.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/pci/bt8xx/bttv-driver.c | 2 +-
drivers/media/pci/meye/meye.h | 2 +-
drivers/media/pci/zoran/z
The systime function uses struct timespec, which we want to stop
using in the kernel because it overflows in 2038. Fortunately,
this use in dibx000_common is in a function that is never called,
so we can just remove it.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/dvb-fro
() is more consistent
and reduces the amount of code duplication, and most importantly
simplifies the following changes.
If desired, this patch can easily be split up into one patch per
driver.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/pci/bt8xx/bttv-driver.c
user space binaries when time_t
gets changed.
If anybody ever starts using this field, they have to make sure not
to use 1970 based seconds in there, as those overflow in 2038.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
include/uapi/linux/dvb/video.h | 3 ++-
1 file changed, 2 inse
base to avoid both the race and the overflow.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/dvb-core/demux.h | 2 +-
drivers/media/dvb-core/dmxdev.c| 2 +-
drivers/media/dvb-core/dvb_demux.c | 17 ++---
drivers/media/dvb-core/dvb_demux.h | 4 ++--
d
is well-defined and contains no padding that might
leak kernel stack data.
We now need the handling for VIDIOC_DQEVENT32 on both 32-bit
and 64-bit architectures, so the handling for that is moved from
v4l2-compat-ioctl32.c to v4l2-ioctl.c and v4l2-subdev.c.
Signed-off-by: Arnd Bergmann <a...@arndb
to the 32-bit compat handling on 64-bit
architectures, but those also have to modify other fields of
the structure. For now, I leave that compat code alone, as it
handles the normal case (32-bit compat_time_t) correctly, this
has to be done as a follow-up.
Signed-off-by: Arnd Bergmann <a...@arndb
the driver to use the normal v4l2_get_timestamp()
function like all other drivers.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/platform/exynos4-is/fimc-capture.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/media/platform/exynos4-i
On Wednesday 16 September 2015 10:12:00 Hans Verkuil wrote:
>
> Are you also attending the ELCE in Dublin? We could have a quick talk there.
> I think the discussion whether to switch to a new v4l2_buffer struct isn't
> really
> dependent on anything y2038.
No, unfortunately I won't be there.
On Wednesday 16 September 2015 08:51:14 Hans Verkuil wrote:
> > a) Similar to my first attempt, define a new struct v4l2_timeval, but
> >only use it when building with a y2038-aware libc, so we don't break
> >existing environments:
> >
> > /* some compile-time conditional that we
, but both would work
equally well here.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/v4l2-core/v4l2-event.c | 20 +---
include/uapi/linux/videodev2.h | 8 +++-
2 files changed, 20 insertions(+), 8 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-e
be taken care of later.
Arnd
Arnd Bergmann (7):
[media] dvb: use ktime_t for internal timeout
[media] dvb: remove unused systime() function
[media] dvb: don't use 'time_t' in event ioctl
[media] exynos4-is: use monotonic timestamps as advertized
[media] use v4l2_get_timestamp where
user space binaries when time_t
gets changed.
If anybody ever starts using this field, they have to make sure not
to use 1970 based seconds in there, as those overflow in 2038.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
include/uapi/linux/dvb/video.h | 3 ++-
1 file changed, 2 inse
base to avoid both the race and the overflow.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/dvb-core/demux.h | 2 +-
drivers/media/dvb-core/dmxdev.c| 2 +-
drivers/media/dvb-core/dvb_demux.c | 17 ++---
drivers/media/dvb-core/dvb_demux.h | 4 ++--
d
to this patch is to leave the structure using
'struct timeval', but then we have to rework the kernel to let
it handle both 32-bit and 64-bit time_t for 32-bit user space
processes.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/pci/bt8xx/bttv-driver.c | 2 +-
drivers
The systime function uses struct timespec, which we want to stop
using in the kernel because it overflows in 2038. Fortunately,
this use in dibx000_common is in a function that is never called,
so we can just remove it.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/dvb-fro
() is more consistent
and reduces the amount of code duplication, and most importantly
simplifies the following changes.
If desired, this patch can easily be split up into one patch per
driver.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/pci/bt8xx/bttv-driver.c
the driver to use the normal v4l2_get_timestamp()
function like all other drivers.
Signed-off-by: Arnd Bergmann <a...@arndb.de>
---
drivers/media/platform/exynos4-is/fimc-capture.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/media/platform/exynos4-i
On Tuesday 15 September 2015 19:55:35 Andreas Oberritter wrote:
> > /* show speed every SPEED_PKTS_INTERVAL packets */
> > if (!(demux->speed_pkts_cnt % SPEED_PKTS_INTERVAL)) {
> > - cur_time = current_kernel_time();
> > + cur_time =
On Tuesday 15 September 2015 18:27:19 Hans Verkuil wrote:
> On 09/15/2015 05:49 PM, Arnd Bergmann wrote:
> > The v4l2 API uses a 'struct timeval' to communicate time stamps to user
> > space. This is broken on 32-bit architectures as soon as we have a C library
> > that def
On Tuesday 15 September 2015 18:32:36 Hans Verkuil wrote:
> >
> > - ktime_get_ts();
> > + ktime_get_ts64();
> > + vts.tv_sec = timestamp.tv_sec;
> > + vts.tv_nsec = timestamp.tv_nsec;
>
> I prefer to take this opportunity to create a v4l2_get_timespec helper
> function, just
On Thursday 04 June 2015 10:47:07 Kevin Hilman wrote:
But I wonder why is not working, shouldn't the driver defer and
be probed again once the PHY driver probe succeeds?
Yeah, I'm not sure why that isn't working, and didn't look into it.
FWIW, the same problem happens when both are
On Monday 01 June 2015 09:56:57 Krzysztof Kozlowski wrote:
Fix for Exynos3250 RTC wake-up interrupts after converting PMU
wakeup to stacked domains. This allows waking up the device from
suspend to RAM using S3C RTC driver (the RTC on SoC).
The patch should be applied some time ago,
On Monday 01 June 2015 09:09:00 Tina Ruchandani wrote:
@@ -1518,10 +1519,11 @@ static int ipp_send_event(struct exynos_drm_ippdrv
*ippdrv,
e = list_first_entry(c_node-event_list,
struct drm_exynos_ipp_send_event, base.link);
- do_gettimeofday(now);
-
On Monday 01 June 2015 08:36:18 Tina Ruchandani wrote:
- do_gettimeofday(now);
+ getnstimeofday64(now);
e-event.tv_sec = now.tv_sec;
- e-event.tv_usec = now.tv_usec;
+ e-event.tv_usec = (now.tv_nsec / NSEC_PER_USEC);
e-event.cmdlist_no = cmdlist_no;
On Saturday 23 May 2015 12:08:42 Kukjin Kim wrote:
Samsung fix for v4.1
- Set display clock correctly for exynos4412-trats2
: fix the following error
exynos-drm: No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
Pulled into
On Saturday 23 May 2015 11:18:58 Kukjin Kim wrote:
On 05/22/15 18:11, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 05/22/2015 02:48 AM, Krzysztof Kozlowski wrote:
Enable the Exynos DSI and S6E8AA0 panel for full X11 display on Trats2.
Signed-off-by: Krzysztof Kozlowski
On Thursday 21 May 2015 12:07:33 Kukjin Kim wrote:
Here is multi_v7_defconfig update and mostly including regarding exynos
stuff based on savedefconfig which could remove useless configs based on
checking of dependencies.
This series is based on v4.1-rc1 and I can provide resolution of
1 - 100 of 753 matches
Mail list logo
