From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sunxi: Re-enable SID driver in multi_v7_defconfig
Date: Wed, 18 Nov 2015 10:09:22 +0900 [thread overview]
Message-ID: <564BCFC2.8050506@samsung.com> (raw)
In-Reply-To: <20151117090309.09ACC6C80816@dd34104.kasserver.com>
On 17.11.2015 18:03, Timo Sigurdsson wrote:
> Hi,
>
> Krzysztof Kozlowski schrieb am 17.11.2015 09:21:
>
> [...]
>
>>>>> @@ -450,8 +431,7 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
>>>>> CONFIG_MEDIA_CONTROLLER=y
>>>>> CONFIG_VIDEO_V4L2_SUBDEV_API=y
>>>>> CONFIG_MEDIA_USB_SUPPORT=y
>>>>> -CONFIG_USB_VIDEO_CLASS=y
>>>>> -CONFIG_USB_GSPCA=y
>>>>> +CONFIG_USB_VIDEO_CLASS=m
>>>>> CONFIG_V4L_PLATFORM_DRIVERS=y
>>>>> CONFIG_SOC_CAMERA=m
>>>>> CONFIG_SOC_CAMERA_PLATFORM=m
>>>>> @@ -465,28 +445,25 @@ CONFIG_DRM=y
>>>>> CONFIG_DRM_I2C_ADV7511=m
>>>>> # CONFIG_DRM_I2C_CH7006 is not set
>>>>> # CONFIG_DRM_I2C_SIL164 is not set
>>>>> -CONFIG_DRM_NXP_PTN3460=m
>>>>> -CONFIG_DRM_PARADE_PS8622=m
>>>>> CONFIG_DRM_NOUVEAU=m
>>>>> CONFIG_DRM_EXYNOS=m
>>>>> -CONFIG_DRM_EXYNOS_DSI=y
>>>>> CONFIG_DRM_EXYNOS_FIMD=y
>>>>> -CONFIG_DRM_EXYNOS_HDMI=y
>>>>
>>>> I would prefer leaving the EXYNOS_HDMI. Dependencies are now not enabled
>>>> but we are fixing it in:
>>>> http://www.spinics.net/lists/dri-devel/msg93299.html
>>>
>>> I think the problem here is that I don't see this patch in linux-next
>>> yet.
>>>
>>
>> Indeed... and I don't know when it will go there so actually maybe it
>> should be removed... but in the same time removing DRM_EXYNOS_HDMI
>> will probably make some conflicts because mentioned patch will go
>> through Exynos DRM tree or Samsung SoC.
>
> Since you suggested to split my patch into two, I might as well just
> hold off the "cleanup" patch until Andrzejs patch hits linux-next.
> Is that ok?
>From my point of view - OK. However this may take time... I don't know
when Andrzej's patch will be applied so for me would work also
savedefconfig without removing HDMI.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Timo Sigurdsson <public_timo.s@silentcreek.de>
Cc: arnd@arndb.de, javier@osg.samsung.com, kgene@kernel.org,
linux@arm.linux.org.uk, olof@lixom.net, geert+renesas@glider.be,
lee.jones@linaro.org, sjoerd.simons@collabora.co.uk,
alexandre.belloni@free-electrons.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, maxime.ripard@free-electrons.com,
linux-sunxi@googlegroups.com, wens@csie.org
Subject: Re: [PATCH] ARM: sunxi: Re-enable SID driver in multi_v7_defconfig
Date: Wed, 18 Nov 2015 10:09:22 +0900 [thread overview]
Message-ID: <564BCFC2.8050506@samsung.com> (raw)
In-Reply-To: <20151117090309.09ACC6C80816@dd34104.kasserver.com>
On 17.11.2015 18:03, Timo Sigurdsson wrote:
> Hi,
>
> Krzysztof Kozlowski schrieb am 17.11.2015 09:21:
>
> [...]
>
>>>>> @@ -450,8 +431,7 @@ CONFIG_MEDIA_CAMERA_SUPPORT=y
>>>>> CONFIG_MEDIA_CONTROLLER=y
>>>>> CONFIG_VIDEO_V4L2_SUBDEV_API=y
>>>>> CONFIG_MEDIA_USB_SUPPORT=y
>>>>> -CONFIG_USB_VIDEO_CLASS=y
>>>>> -CONFIG_USB_GSPCA=y
>>>>> +CONFIG_USB_VIDEO_CLASS=m
>>>>> CONFIG_V4L_PLATFORM_DRIVERS=y
>>>>> CONFIG_SOC_CAMERA=m
>>>>> CONFIG_SOC_CAMERA_PLATFORM=m
>>>>> @@ -465,28 +445,25 @@ CONFIG_DRM=y
>>>>> CONFIG_DRM_I2C_ADV7511=m
>>>>> # CONFIG_DRM_I2C_CH7006 is not set
>>>>> # CONFIG_DRM_I2C_SIL164 is not set
>>>>> -CONFIG_DRM_NXP_PTN3460=m
>>>>> -CONFIG_DRM_PARADE_PS8622=m
>>>>> CONFIG_DRM_NOUVEAU=m
>>>>> CONFIG_DRM_EXYNOS=m
>>>>> -CONFIG_DRM_EXYNOS_DSI=y
>>>>> CONFIG_DRM_EXYNOS_FIMD=y
>>>>> -CONFIG_DRM_EXYNOS_HDMI=y
>>>>
>>>> I would prefer leaving the EXYNOS_HDMI. Dependencies are now not enabled
>>>> but we are fixing it in:
>>>> http://www.spinics.net/lists/dri-devel/msg93299.html
>>>
>>> I think the problem here is that I don't see this patch in linux-next
>>> yet.
>>>
>>
>> Indeed... and I don't know when it will go there so actually maybe it
>> should be removed... but in the same time removing DRM_EXYNOS_HDMI
>> will probably make some conflicts because mentioned patch will go
>> through Exynos DRM tree or Samsung SoC.
>
> Since you suggested to split my patch into two, I might as well just
> hold off the "cleanup" patch until Andrzejs patch hits linux-next.
> Is that ok?
>From my point of view - OK. However this may take time... I don't know
when Andrzej's patch will be applied so for me would work also
savedefconfig without removing HDMI.
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-11-18 1:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 1:49 [PATCH] ARM: sunxi: Re-enable SID driver in multi_v7_defconfig Timo Sigurdsson
2015-11-17 1:49 ` Timo Sigurdsson
2015-11-17 2:10 ` Krzysztof Kozlowski
2015-11-17 2:10 ` Krzysztof Kozlowski
2015-11-17 8:01 ` Timo Sigurdsson
2015-11-17 8:01 ` Timo Sigurdsson
2015-11-17 8:21 ` Krzysztof Kozlowski
2015-11-17 8:21 ` Krzysztof Kozlowski
2015-11-17 9:03 ` Timo Sigurdsson
2015-11-17 9:03 ` Timo Sigurdsson
2015-11-18 1:09 ` Krzysztof Kozlowski [this message]
2015-11-18 1:09 ` Krzysztof Kozlowski
2015-11-17 8:07 ` Lee Jones
2015-11-17 8:07 ` Lee Jones
2015-11-17 8:38 ` Timo Sigurdsson
2015-11-17 8:38 ` Timo Sigurdsson
2015-11-19 21:33 ` [PATCH v2] " Timo Sigurdsson
2015-11-19 21:33 ` Timo Sigurdsson
2015-11-20 0:01 ` Krzysztof Kozlowski
2015-11-20 0:01 ` Krzysztof Kozlowski
2015-11-20 11:45 ` Maxime Ripard
2015-11-20 11:45 ` Maxime Ripard
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=564BCFC2.8050506@samsung.com \
--to=k.kozlowski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.