Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Parshuram Raju Thombare <pthombar@cadence.com>
To:     Rob Herring <robh@kernel.org>
CC:     "robert.foss@linaro.org" <robert.foss@linaro.org>,
        "laurent.pinchart@ideasonboard.com" 
        <laurent.pinchart@ideasonboard.com>,
        "airlied@linux.ie" <airlied@linux.ie>,
        "daniel@ffwll.ch" <daniel@ffwll.ch>,
        "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>,
        "a.hajda@samsung.com" <a.hajda@samsung.com>,
        "narmstrong@baylibre.com" <narmstrong@baylibre.com>,
        "nikhil.nd@ti.com" <nikhil.nd@ti.com>,
        "kishon@ti.com" <kishon@ti.com>,
        Swapnil Kashinath Jakhade <sjakhade@cadence.com>,
        Milind Parab <mparab@cadence.com>
Subject: RE: [PATCH v5 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding
 changes for HDCP
Thread-Topic: [PATCH v5 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding
 changes for HDCP
Thread-Index: AQHXHKOi/86dAQ9N3U2czyHmDrT9E6qSMz8AgBZ3t0A=
Date:   Wed, 7 Apr 2021 06:03:29 +0000
Message-ID: <MWHPR07MB276881500489CBFE1F297C1FC1759@MWHPR07MB2768.namprd07.prod.outlook.com>
References: <1616146664-6941-1-git-send-email-pthombar@cadence.com>
 <1616146709-7227-1-git-send-email-pthombar@cadence.com>
 <20210323224546.GA1485576@robh.at.kernel.org>
In-Reply-To: <20210323224546.GA1485576@robh.at.kernel.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9bda3544-3356-4aa5-93ac-08d8f98ade24
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2021 06:03:29.5139
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d36035c5-6ce6-4662-a3dc-e762e61ae4c9
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: lQT87Av9a6LonauQ5xVEZckuNUtcx0/9oT0KMzvVe6LudHMR9lLerjRyYeWXbcCY0ZQ2TchVPb+mMrN+2diEEBQQ6399TnP56Qah7udBXH4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR07MB4012
X-Proofpoint-GUID: mRQJscMliHonHEV1FSiNHdahvzoLtwsw
X-Proofpoint-ORIG-GUID: mRQJscMliHonHEV1FSiNHdahvzoLtwsw
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.761
 definitions=2021-04-07_03:2021-04-06,2021-04-07 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_check_notspam policy=outbound_check score=0 phishscore=0
 clxscore=1015 adultscore=0 impostorscore=0 spamscore=0 suspectscore=0
 priorityscore=1501 bulkscore=0 malwarescore=0 lowpriorityscore=0
 mlxscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-2104060000 definitions=main-2104070044
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Rob,

Thanks for your comment and sorry for late response.

>> -    minItems: 1
>> -    maxItems: 2
>> +    minItems: 2
>> +    maxItems: 3
>
>1 entry was valid and now it is not? That's not a compatible change and
>needs an explanation at a minimum.

Yes, as the driver returns error in the absence of SAPB port address range,=
 this
may break the driver on platform without SAPB port. This IP needs SAPB port
to support HDCP feature using embedded HDCP crypto module.

So, to maintain backward compatibility I will modify the driver and allow i=
t
to proceed without HDCP feature, instead of returning an error, in case of =
no SAPB port.

Regards,
Parshuram Thombare