From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: "Togorean, Bogdan" <Bogdan.Togorean@analog.com>
Cc: "Laurent.pinchart@ideasonboard.com"
<Laurent.pinchart@ideasonboard.com>,
"a.hajda@samsung.com" <a.hajda@samsung.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"sam@ravnborg.org" <sam@ravnborg.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"allison@lohutok.net" <allison@lohutok.net>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"matt.redfearn@thinci.com" <matt.redfearn@thinci.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>
Subject: Re: [PATCH v2 2/2] drm: bridge: adv7511: Add support for ADV7535
Date: Wed, 27 Nov 2019 14:46:43 +0000 [thread overview]
Message-ID: <fc1b73b2-def6-2e54-defc-30fe73b8d82e@kontron.de> (raw)
In-Reply-To: <d8470738b044d6559aa8e7b07f8d50ce6791f980.camel@analog.com>
On 27.11.19 15:22, Togorean, Bogdan wrote:
> Hi Frieder,
>
> I'm glad to find there are other persons interested in this driver and
> especially support for ADV7535. Unfortunately I had to put on hold the
> development due to other activities but I'll send V3 tomorrow.
Great to hear that. Thanks for your effort. I will try to test your v3
when I have received the new hardware and got it up and running.
>
> I also started work on HDCP support for this driver and hope to send
> soon a patch for that.
>
> Best regards,
> Bogdan
>
> On Wed, 2019-11-27 at 11:52 +0000, Schrempf Frieder wrote:
>> [External]
>>
>> Hi Bogdan,
>>
>> On 21.08.19 07:34, Togorean, Bogdan wrote:
>>> On Tue, 2019-08-20 at 10:53 +0200, Daniel Vetter wrote:
>>>> [External]
>>>>
>>>> On Mon, Aug 19, 2019 at 12:46:16PM +0200, Sam Ravnborg wrote:
>>>>> Hi Bogdan.
>>>>>
>>>>>>>> adv7533_detach_dsi(adv7511);
>>>>>>>> i2c_unregister_device(adv7511->i2c_cec);
>>>>>>>> if (adv7511->cec_clk)
>>>>>>>> @@ -1266,8 +1278,9 @@ static const struct i2c_device_id
>>>>>>>> adv7511_i2c_ids[] = {
>>>>>>>> { "adv7511", ADV7511 },
>>>>>>>> { "adv7511w", ADV7511 },
>>>>>>>> { "adv7513", ADV7511 },
>>>>>>>> -#ifdef CONFIG_DRM_I2C_ADV7533
>>>>>>>> +#ifdef CONFIG_DRM_I2C_ADV753x
>>>>>>>> { "adv7533", ADV7533 },
>>>>>>>> + { "adv7535", ADV7535 },
>>>>>>>> #endif
>>>>>>>
>>>>>>> This ifdef may not be needed??
>>>>>>> If we did not get this type we will not look it up.
>>>>>> But if we have defined in DT adv7533/5 device but
>>>>>> CONFIG_DRM_I2C_ADV753x not selected probe will fail with
>>>>>> ENODEV.
>>>>>> That
>>>>>> would be ok?
>>>>>
>>>>> What do we gain from this complexity in the end.
>>>>> Why not let the driver always support all variants.
>>>>>
>>>>> If this result in a simpler driver, and less choices in Kconfig
>>>>> then it is a win-win.
>>>>
>>>> Yeah in general we don't Kconfig within drivers in drm to disable
>>>> specific
>>>> code-paths. It's not worth the pain.
>> >
>>> Ack,
>>> Thank you for clarification. Will remove in V3.
>>
>> Are you still working on this? Do you plan to send a v3?
>> I will soon lay my hands on a board with the ADV7535 and would like
>> to
>> see this merged.
>> Also for patch 1/2, it seems you already have a R-b for v1 from
>> Laurent,
>> but you didn't carry the tag to v2.
>>
>> Thanks,
>> Frieder
prev parent reply other threads:[~2019-11-27 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 14:16 [PATCH v2 0/2] drm: bridge: adv7511: Add support For ADV7535 Bogdan Togorean
2019-08-09 14:16 ` [PATCH v2 1/2] dt-bindings: drm: bridge: adv7511: Add ADV7535 support Bogdan Togorean
2019-08-09 14:16 ` [PATCH v2 2/2] drm: bridge: adv7511: Add support for ADV7535 Bogdan Togorean
2019-08-09 15:25 ` Sam Ravnborg
2019-08-19 8:59 ` Togorean, Bogdan
2019-08-19 10:46 ` Sam Ravnborg
2019-08-20 8:53 ` Daniel Vetter
2019-08-21 5:34 ` Togorean, Bogdan
2019-11-27 11:52 ` Schrempf Frieder
2019-11-27 14:22 ` Togorean, Bogdan
2019-11-27 14:46 ` Schrempf Frieder [this message]
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=fc1b73b2-def6-2e54-defc-30fe73b8d82e@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=Bogdan.Togorean@analog.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=allison@lohutok.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.redfearn@thinci.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®