Hi,
On Thu, Apr 14, 2022 at 10:27 AM Xin Ji xji@analogixsemi.com wrote:
On Wed, Apr 13, 2022 at 04:28:51PM +0200, Robert Foss wrote:
On Sat, 9 Apr 2022 at 06:47, Xin Ji xji@analogixsemi.com wrote:
On Mon, Apr 04, 2022 at 12:52:14PM -0500, Rob Herring wrote:
On Mon, Mar 28, 2022 at 08:09:54PM +0800, Xin Ji wrote:
Change bus-type define for DPI.
Fixes: a43661e7e819 ("dt-bindings:drm/bridge:anx7625:add vendor define")
Signed-off-by: Xin Ji xji@analogixsemi.com
.../devicetree/bindings/display/bridge/analogix,anx7625.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml index 0d38d6fe3983..4590186c4a0b 100644 --- a/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml +++ b/Documentation/devicetree/bindings/display/bridge/analogix,anx7625.yaml @@ -106,7 +106,7 @@ properties: remote-endpoint: true
bus-type:
enum: [1, 5]
enum: [7]Changing is an ABI break, but didn't we revert adding this?
Hi Rob, sorry, what do you mean about ABI break? Do I need remove this patch in this serial? Or do I need revert patch https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork...., I don't know how to do it.
I contributed to the confusion about this, let's see if we can clear it up.
An issue was found related to which enum values were used to represent what late in the last release cycle. As a result a revert[1] patch for everything touching bus-type in anx7625 was merged.
This patch, does not apply to drm-misc-next due to the revert, and if Xin Ji rebases his work on the drm-misc-next there should be no ABI-change as this patch when fixed up will introduce bus-type to the nax7625 ABI.
Xin: Does this make sense to you?
Hi Robert Foss, yes, my work is based on drm-misc-next, all I can do, just make a fix up patch(this patch) to change the bus-type define.
The revert was applied to the soc tree and merged into Linus's tree in v5.17-rc8. It was not present in drm-misc-next until April 5 with commit 9cbbd694a58b ("Merge drm/drm-next into drm-misc-next").
So please fetch the latest drm-misc-next, rebase your patches on top, and resend.
Thanks ChenYu