From: Matthias Brugger <matthias.bgg@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: "Enric Balletbo Serra" <eballetbo@gmail.com>,
"Jitao Shi" <jitao.shi@mediatek.com>,
"David Airlie" <airlied@linux.ie>,
"Thierry Reding" <treding@nvidia.com>,
"Mark Rutland" <mark.rutland@arm.com>,
stonea168@163.com, dri-devel <dri-devel@lists.freedesktop.org>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Ajay Kumar" <ajaykumar.rs@samsung.com>,
"Vincent Palatin" <vpalatin@chromium.org>,
"cawa cheng" <cawa.cheng@mediatek.com>,
"Bibby Hsieh (謝濟遠)" <bibby.hsieh@mediatek.com>,
"CK Hu (胡俊光)" <ck.hu@mediatek.com>,
"Russell King" <rmk+kernel@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Pawel Moll" <pawel.moll@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Inki Dae" <inki.dae@samsung.com>,
"Rob Herring" <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"Yingjoe Chen" <yingjoe.chen@mediatek.com>,
"Eddie Huang (黃智傑)" <eddie.huang@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Rahul Sharma" <rahul.sharma@samsung.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Kumar Gala" <galak@codeaurora.org>,
"Sean Paul" <seanpaul@chromium.org>
Subject: Re: [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge
Date: Mon, 7 Nov 2016 17:53:42 +0100 [thread overview]
Message-ID: <3e2dfdfd-9d87-b49a-4012-6027bdca10f5@gmail.com> (raw)
In-Reply-To: <CAGS+omDmFdqzuFqcCe9gFGemZc88Yt0_3_o2KwOgW=GN_kCakQ@mail.gmail.com>
On 05/11/16 00:21, Daniel Kurtz wrote:
> On Tue, Oct 25, 2016 at 6:23 AM, Matthias Brugger
> <matthias.bgg@gmail.com> wrote:
>>
>> On 10/18/2016 04:37 PM, Enric Balletbo Serra wrote:
>> [...]
>>>> --- /dev/null
>>>> +++ b/drivers/gpu/drm/bridge/parade-ps8640.c
>> [...]
>>>>
>>>> +
>>>> +/* Firmware */
>>>> +#define PS_FW_NAME "ps864x_fw.bin"
>>>> +
>>>
>>> From where I can download this firmware image?
>>
>> I suppose this FW bits have to be added to linux-firmware repository first, before this patch can be accepted.
>
> All PS8640 devices should already ship with working firmware.
> The firmware update procedure is only used in the unlikely event where
> one wants to update the bridge to a different firmware provided by
> Parade.
>
> Why must the lack of firmware really block landing this driver?
>
> If this is really so, can we just land the functional part of the
> driver first, and add the firmware update in a follow-up patch.
>
After checking other users of request_firmware and check them against
linux-firmware I think we don't need the FW in linux-firmware to get the
driver merged. Especially as there already is a working FW stored on the
device.
Regards,
Matthias
next prev parent reply other threads:[~2016-11-07 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 6:44 [v17 1/2] Documentation: bridge: Add documentation for ps8640 DT properties Jitao Shi
2016-08-27 6:44 ` [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge Jitao Shi
2016-10-18 14:37 ` Enric Balletbo Serra
2016-10-25 12:23 ` Matthias Brugger
2016-11-04 23:21 ` Daniel Kurtz
2016-11-07 16:53 ` Matthias Brugger [this message]
2016-11-10 16:39 ` Enric Balletbo Serra
2016-11-11 6:02 ` Archit Taneja
2016-11-14 13:50 ` Jitao Shi
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=3e2dfdfd-9d87-b49a-4012-6027bdca10f5@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=airlied@linux.ie \
--cc=ajaykumar.rs@samsung.com \
--cc=andy.yan@rock-chips.com \
--cc=bibby.hsieh@mediatek.com \
--cc=cawa.cheng@mediatek.com \
--cc=ck.hu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eballetbo@gmail.com \
--cc=eddie.huang@mediatek.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inki.dae@samsung.com \
--cc=jitao.shi@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=rahul.sharma@samsung.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=srv_heupstream@mediatek.com \
--cc=stonea168@163.com \
--cc=treding@nvidia.com \
--cc=vpalatin@chromium.org \
--cc=yingjoe.chen@mediatek.com \
/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
Powered by JetHome