From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 15/17] video: fbdev: s3c-fb: remove s5pc100 related fimd and fb codes
Date: Tue, 01 Jul 2014 11:05:04 +0900 [thread overview]
Message-ID: <00a401cf94d0$df8d94e0$9ea8bea0$%han@samsung.com> (raw)
In-Reply-To: <1404163947-3105-16-git-send-email-kgene.kim@samsung.com>
On Tuesday, July 01, 2014 6:32 AM, Kukjin Kim wrote:
>
> This patch removes fimd and fb codes for s5pc100 SoC.
>
> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Jingoo Han <jg1.han@samsung.com>
Best regards,
Jingoo Han
> ---
> .../devicetree/bindings/video/samsung-fimd.txt | 1 -
> drivers/video/fbdev/Kconfig | 2 +-
> drivers/video/fbdev/s3c-fb.c | 35 --------------------
> include/video/samsung_fimd.h | 2 +-
> 4 files changed, 2 insertions(+), 38 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/video/samsung-fimd.txt
> b/Documentation/devicetree/bindings/video/samsung-fimd.txt
> index 741f4a6..7794260 100644
> --- a/Documentation/devicetree/bindings/video/samsung-fimd.txt
> +++ b/Documentation/devicetree/bindings/video/samsung-fimd.txt
> @@ -8,7 +8,6 @@ Required properties:
> - compatible: value should be one of the following
> "samsung,s3c2443-fimd"; /* for S3C24XX SoCs */
> "samsung,s3c6400-fimd"; /* for S3C64XX SoCs */
> - "samsung,s5pc100-fimd"; /* for S5PC100 SoC */
> "samsung,s5pv210-fimd"; /* for S5PV210 SoC */
> "samsung,exynos4210-fimd"; /* for Exynos4 SoCs */
> "samsung,exynos5250-fimd"; /* for Exynos5 SoCs */
> diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
> index 11506e5..79708b2 100644
> --- a/drivers/video/fbdev/Kconfig
> +++ b/drivers/video/fbdev/Kconfig
> @@ -2019,7 +2019,7 @@ config FB_TMIO_ACCELL
> config FB_S3C
> tristate "Samsung S3C framebuffer support"
> depends on FB && (CPU_S3C2416 || ARCH_S3C64XX || \
> - ARCH_S5PC100 || ARCH_S5PV210 || ARCH_EXYNOS)
> + ARCH_S5PV210 || ARCH_EXYNOS)
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> select FB_CFB_IMAGEBLIT
> diff --git a/drivers/video/fbdev/s3c-fb.c b/drivers/video/fbdev/s3c-fb.c
> index a0cde41..b33abb0 100644
> --- a/drivers/video/fbdev/s3c-fb.c
> +++ b/drivers/video/fbdev/s3c-fb.c
> @@ -1805,38 +1805,6 @@ static struct s3c_fb_driverdata s3c_fb_data_64xx = {
> .win[4] = &s3c_fb_data_64xx_wins[4],
> };
>
> -static struct s3c_fb_driverdata s3c_fb_data_s5pc100 = {
> - .variant = {
> - .nr_windows = 5,
> - .vidtcon = VIDTCON0,
> - .wincon = WINCON(0),
> - .winmap = WINxMAP(0),
> - .keycon = WKEYCON,
> - .osd = VIDOSD_BASE,
> - .osd_stride = 16,
> - .buf_start = VIDW_BUF_START(0),
> - .buf_size = VIDW_BUF_SIZE(0),
> - .buf_end = VIDW_BUF_END(0),
> -
> - .palette = {
> - [0] = 0x2400,
> - [1] = 0x2800,
> - [2] = 0x2c00,
> - [3] = 0x3000,
> - [4] = 0x3400,
> - },
> -
> - .has_prtcon = 1,
> - .has_blendcon = 1,
> - .has_clksel = 1,
> - },
> - .win[0] = &s3c_fb_data_s5p_wins[0],
> - .win[1] = &s3c_fb_data_s5p_wins[1],
> - .win[2] = &s3c_fb_data_s5p_wins[2],
> - .win[3] = &s3c_fb_data_s5p_wins[3],
> - .win[4] = &s3c_fb_data_s5p_wins[4],
> -};
> -
> static struct s3c_fb_driverdata s3c_fb_data_s5pv210 = {
> .variant = {
> .nr_windows = 5,
> @@ -1975,9 +1943,6 @@ static struct platform_device_id s3c_fb_driver_ids[] = {
> .name = "s3c-fb",
> .driver_data = (unsigned long)&s3c_fb_data_64xx,
> }, {
> - .name = "s5pc100-fb",
> - .driver_data = (unsigned long)&s3c_fb_data_s5pc100,
> - }, {
> .name = "s5pv210-fb",
> .driver_data = (unsigned long)&s3c_fb_data_s5pv210,
> }, {
> diff --git a/include/video/samsung_fimd.h b/include/video/samsung_fimd.h
> index b039320..8af0c61 100644
> --- a/include/video/samsung_fimd.h
> +++ b/include/video/samsung_fimd.h
> @@ -107,7 +107,7 @@
> #define VIDCON2_ORGYCbCr (1 << 8)
> #define VIDCON2_YUVORDCrCb (1 << 7)
>
> -/* PRTCON (S3C6410, S5PC100)
> +/* PRTCON (S3C6410)
> * Might not be present in the S3C6410 documentation,
> * but tests prove it's there almost for sure; shouldn't hurt in any case.
> */
> --
> 1.7.10.4
next prev parent reply other threads:[~2014-07-01 2:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:32 [PATCH 00/17] ARM: S5P64X0, S5PC100: no more support in mainline Kukjin Kim
2014-06-30 13:34 ` Arnd Bergmann
2014-06-30 14:22 ` Thierry Reding
2014-06-30 14:31 ` Arnd Bergmann
2014-07-01 2:08 ` Kukjin Kim
2014-06-30 15:31 ` Tushar Behera
2014-07-01 2:08 ` Kukjin Kim
2014-06-30 21:32 ` [PATCH 02/17] gpio: samsung: remove s5p64x0 related gpio codes Kukjin Kim
2014-07-07 16:05 ` Linus Walleij
2014-06-30 21:32 ` [PATCH 03/17] spi: s3c64xx: remove s5p64x0 related spi codes Kukjin Kim
2014-06-30 21:32 ` [PATCH 04/17] ASoC: samsung: no more support for S5P6440 and S5P6450 SoCs Kukjin Kim
2014-06-30 21:32 ` [PATCH 05/17] pwm: samsung: remove s5p64x0 related pwm codes Kukjin Kim
2014-07-04 8:10 ` Tomasz Figa
2014-07-07 22:23 ` Kukjin Kim
2014-07-08 15:43 ` Tomasz Figa
2014-06-30 21:32 ` [PATCH 06/17] video: fbdev: s3c-fb: remove s5p64x0 related fimd codes Kukjin Kim
2014-07-01 2:04 ` Jingoo Han
2014-07-01 6:25 ` Tomi Valkeinen
2014-06-30 21:32 ` [PATCH 07/17] serial: samsung: no more support for S5P6440 and S5P6450 SoCs Kukjin Kim
2014-06-30 21:32 ` [PATCH 09/17] gpio: samsung: remov s5pc100 related gpio codes Kukjin Kim
2014-07-07 16:05 ` Linus Walleij
2014-06-30 21:32 ` [PATCH 10/17] spi: s3c64xx: remove s5pc100 related spi codes Kukjin Kim
2014-06-30 21:32 ` [PATCH 11/17] pwm: samsung: remove s5pc100 related pwm codes Kukjin Kim
2014-07-03 12:44 ` Tomasz Figa
2014-07-04 7:32 ` Kukjin Kim
2014-07-04 8:07 ` Tomasz Figa
2014-06-30 21:32 ` [PATCH 12/17] serial: samsung: no more support for S5PC100 SoC Kukjin Kim
2014-06-30 21:32 ` [PATCH 13/17] ata: pata_samsung_cf: removes s5pc100 related ata codes Kukjin Kim
2014-06-30 14:49 ` Tejun Heo
2014-06-30 21:32 ` [PATCH 14/17] mtd: onenand: remove s5pc100 related onenand codes Kukjin Kim
2014-07-12 7:12 ` Brian Norris
2014-06-30 21:32 ` [PATCH 15/17] video: fbdev: s3c-fb: remove s5pc100 related fimd and fb codes Kukjin Kim
2014-07-01 2:05 ` Jingoo Han [this message]
2014-06-30 21:32 ` [PATCH 16/17] [media] exynos4-is: removes s5pc100 related fimc codes Kukjin Kim
2014-06-30 14:03 ` Sylwester Nawrocki
2014-06-30 21:32 ` [PATCH 17/17] ASoC: Samsung: remove s5pc100 related codes Kukjin Kim
2014-07-14 18:05 ` Mark Brown
2014-07-02 18:02 ` [PATCH 00/17] ARM: S5P64X0, S5PC100: no more support in mainline Tomasz Figa
2014-07-02 22:46 ` Kukjin Kim
2014-07-03 3:35 ` Sachin Kamat
2014-07-04 8:43 ` Kukjin Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00a401cf94d0$df8d94e0$9ea8bea0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).