From: "Guido Günther" <agx@sigxcpu.org> To: Swapnil Kashinath Jakhade <sjakhade@cadence.com> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>, "airlied@linux.ie" <airlied@linux.ie>, "daniel@ffwll.ch" <daniel@ffwll.ch>, "Laurent.pinchart@ideasonboard.com" <Laurent.pinchart@ideasonboard.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "a.hajda@samsung.com" <a.hajda@samsung.com>, "narmstrong@baylibre.com" <narmstrong@baylibre.com>, "jonas@kwiboo.se" <jonas@kwiboo.se>, "jernej.skrabec@siol.net" <jernej.skrabec@siol.net>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Milind Parab <mparab@cadence.com>, Yuti Suresh Amonkar <yamonkar@cadence.com>, "praneeth@ti.com" <praneeth@ti.com>, "nsekhar@ti.com" <nsekhar@ti.com>, "jsarha@ti.com" <jsarha@ti.com>, "sandor.yu@nxp.com" <sandor.yu@nxp.com> Subject: Re: [PATCH v8 0/3] drm: Add support for Cadence MHDP DPI/DP bridge and J721E wrapper. Date: Tue, 25 Aug 2020 09:32:19 +0200 [thread overview] Message-ID: <20200825073219.GA5528@bogon.m.sigxcpu.org> (raw) In-Reply-To: <DM6PR07MB61542D7CC2B319142CC5E0CAC5560@DM6PR07MB6154.namprd07.prod.outlook.com> Hi Swapnil, On Mon, Aug 24, 2020 at 07:16:31AM +0000, Swapnil Kashinath Jakhade wrote: [..snip..] > Following are the differences between MHDP IPs from Cadence for Rockchip, TI and NxP: > > The Rockchip and NXP MHDP Core shares the same part (IP8501) which is DP v1.3 SST > Controller with HDCP 2.2/1.x. NXP's version additionally supports HDMI. > TI uses a different part (IP8546A), which is DP v1.4 with HDCP 2.2/1.x. > TI DP Controller adds support for additional features such as Multi Stream Support (MST), > Forward Error Correction (FEC) and Compression (DSC). > > Also, FW used for TI has significant differences than FW used for Rockchip or NXP. > NxP and TI firmware are developed and maintained separately by Cadence and are in > active support. > > From the Linux driver perspective, given the differences, it would make sense to have > TI driver maintained separately. Thanks for the clarification, that indeed helps a lot. So the rockchip and nxp drivers can be merged while the ti one should stay separate. Cheers, -- Guido > > Thanks, > Swapnil > > > > > > I'm worried that if there are IP differences, even if not great ones, > > > and if the FWs are different and developed separately, it'll be a > > > constant "fix X for SoC A, and accidentally break Y for SoC B and C", > > especially if too much code is shared. > > > > > > In the long run I'm all for a single driver (or large shared parts), > > > but I'm not sure if we should start with that approach. > > > > > > > > > > > > > > Tomi > > > > > > -- > > > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. > > > Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki > > > >
WARNING: multiple messages have this Message-ID (diff)
From: "Guido Günther" <agx@sigxcpu.org> To: Swapnil Kashinath Jakhade <sjakhade@cadence.com> Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "jernej.skrabec@siol.net" <jernej.skrabec@siol.net>, "praneeth@ti.com" <praneeth@ti.com>, Yuti Suresh Amonkar <yamonkar@cadence.com>, "narmstrong@baylibre.com" <narmstrong@baylibre.com>, "airlied@linux.ie" <airlied@linux.ie>, Tomi Valkeinen <tomi.valkeinen@ti.com>, "jonas@kwiboo.se" <jonas@kwiboo.se>, "nsekhar@ti.com" <nsekhar@ti.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "a.hajda@samsung.com" <a.hajda@samsung.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "Laurent.pinchart@ideasonboard.com" <Laurent.pinchart@ideasonboard.com>, "sandor.yu@nxp.com" <sandor.yu@nxp.com>, "jsarha@ti.com" <jsarha@ti.com>, Milind Parab <mparab@cadence.com> Subject: Re: [PATCH v8 0/3] drm: Add support for Cadence MHDP DPI/DP bridge and J721E wrapper. Date: Tue, 25 Aug 2020 09:32:19 +0200 [thread overview] Message-ID: <20200825073219.GA5528@bogon.m.sigxcpu.org> (raw) In-Reply-To: <DM6PR07MB61542D7CC2B319142CC5E0CAC5560@DM6PR07MB6154.namprd07.prod.outlook.com> Hi Swapnil, On Mon, Aug 24, 2020 at 07:16:31AM +0000, Swapnil Kashinath Jakhade wrote: [..snip..] > Following are the differences between MHDP IPs from Cadence for Rockchip, TI and NxP: > > The Rockchip and NXP MHDP Core shares the same part (IP8501) which is DP v1.3 SST > Controller with HDCP 2.2/1.x. NXP's version additionally supports HDMI. > TI uses a different part (IP8546A), which is DP v1.4 with HDCP 2.2/1.x. > TI DP Controller adds support for additional features such as Multi Stream Support (MST), > Forward Error Correction (FEC) and Compression (DSC). > > Also, FW used for TI has significant differences than FW used for Rockchip or NXP. > NxP and TI firmware are developed and maintained separately by Cadence and are in > active support. > > From the Linux driver perspective, given the differences, it would make sense to have > TI driver maintained separately. Thanks for the clarification, that indeed helps a lot. So the rockchip and nxp drivers can be merged while the ti one should stay separate. Cheers, -- Guido > > Thanks, > Swapnil > > > > > > I'm worried that if there are IP differences, even if not great ones, > > > and if the FWs are different and developed separately, it'll be a > > > constant "fix X for SoC A, and accidentally break Y for SoC B and C", > > especially if too much code is shared. > > > > > > In the long run I'm all for a single driver (or large shared parts), > > > but I'm not sure if we should start with that approach. > > > > > > > > > > > > > > Tomi > > > > > > -- > > > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. > > > Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki > > > > _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-25 7:32 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-06 11:34 [PATCH v8 0/3] drm: Add support for Cadence MHDP DPI/DP bridge and J721E wrapper Swapnil Jakhade 2020-08-06 11:34 ` Swapnil Jakhade 2020-08-06 11:34 ` [PATCH v8 1/3] dt-bindings: drm/bridge: Document Cadence MHDP bridge bindings Swapnil Jakhade 2020-08-06 11:34 ` Swapnil Jakhade 2020-08-11 0:36 ` Laurent Pinchart 2020-08-11 0:36 ` Laurent Pinchart 2020-08-14 7:13 ` Tomi Valkeinen 2020-08-14 7:13 ` Tomi Valkeinen 2020-08-06 11:34 ` [PATCH v8 2/3] drm: bridge: Add support for Cadence MHDP DPI/DP bridge Swapnil Jakhade 2020-08-06 11:34 ` Swapnil Jakhade 2020-08-07 1:15 ` kernel test robot 2020-08-07 1:15 ` kernel test robot 2020-08-07 1:15 ` kernel test robot 2020-08-07 9:38 ` Tomi Valkeinen 2020-08-07 9:38 ` Tomi Valkeinen 2020-08-11 2:36 ` Laurent Pinchart 2020-08-11 2:36 ` Laurent Pinchart 2020-08-14 8:22 ` Tomi Valkeinen 2020-08-14 8:22 ` Tomi Valkeinen 2020-08-24 2:17 ` Laurent Pinchart 2020-08-24 2:17 ` Laurent Pinchart 2020-08-14 9:29 ` Tomi Valkeinen 2020-08-14 9:29 ` Tomi Valkeinen 2020-08-24 2:18 ` Laurent Pinchart 2020-08-24 2:18 ` Laurent Pinchart 2020-08-26 7:26 ` Tomi Valkeinen 2020-08-26 7:26 ` Tomi Valkeinen 2020-08-06 11:34 ` [PATCH v8 3/3] drm: bridge: cdns-mhdp: Add j721e wrapper Swapnil Jakhade 2020-08-06 11:34 ` Swapnil Jakhade 2020-08-11 2:41 ` Laurent Pinchart 2020-08-11 2:41 ` Laurent Pinchart 2020-08-12 8:39 ` [PATCH v8 0/3] drm: Add support for Cadence MHDP DPI/DP bridge and J721E wrapper Guido Günther 2020-08-12 8:39 ` Guido Günther 2020-08-12 10:47 ` Tomi Valkeinen 2020-08-12 10:47 ` Tomi Valkeinen 2020-08-12 13:56 ` Guido Günther 2020-08-12 13:56 ` Guido Günther 2020-08-24 7:16 ` Swapnil Kashinath Jakhade 2020-08-24 7:16 ` Swapnil Kashinath Jakhade 2020-08-25 7:32 ` Guido Günther [this message] 2020-08-25 7:32 ` Guido Günther
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=20200825073219.GA5528@bogon.m.sigxcpu.org \ --to=agx@sigxcpu.org \ --cc=Laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jernej.skrabec@siol.net \ --cc=jonas@kwiboo.se \ --cc=jsarha@ti.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mparab@cadence.com \ --cc=narmstrong@baylibre.com \ --cc=nsekhar@ti.com \ --cc=praneeth@ti.com \ --cc=robh+dt@kernel.org \ --cc=sandor.yu@nxp.com \ --cc=sjakhade@cadence.com \ --cc=tomi.valkeinen@ti.com \ --cc=yamonkar@cadence.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: linkBe 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.