Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp23237ybm; Mon, 20 May 2019 11:09:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqwlM08ce3Bx5ja8wDpqCV6J++SDWfYAnjFttoe58nWz4Y6jKOq+OKf+JDc/kZD8YzVDYsUc X-Received: by 2002:a63:754b:: with SMTP id f11mr76925246pgn.32.1558375765526; Mon, 20 May 2019 11:09:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558375765; cv=none; d=google.com; s=arc-20160816; b=DkpgZ9Zz4Vn+286NXJPmacRSGw0zokvG1Ir3KfqjAKOW8zv32CIPxx58eDB11obEBZ VNji0WvvLwitRNsWvXUVO8v8P4A1yS4kkChUTK5/ORnPCiGuKQx22BCpA0uyksDP0QOY R3N3CZEaf+NsZhiSzdejkjRQhzODlkU5fbEeY+V9hm+/ZOcDRVHxE1IdsLakgQjZg3Sw PrWFN6pIhFhgNsBFefgXbq9r+oaxdwekM7zVNO5vip07QaBUOn3a5l2idanaqFczmZSj aqztF/MMjep89EEwMD6MdQP6/7L/LQfK2cV1uD+MduiwUEfpbWEfTZcLJWQx082RECtV BC7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:in-reply-to:subject:cc:to:from:date; bh=VIvpsjPjH+ouLSxOPz89wSIogB4E7aJmn0bcmCuh6BA=; b=vBS7ZGubpfZz8tITku4iueDlkMpCm32v5+4MUeLxFDYjuuWa4utIRW6zfgsfl4uaTN qz9CCQhQdg4dcRa0tiRLQzb0RjiEaHz4vOjY/MTZ2ii0JlYz/FkSwv0zY+h0/DHykMq+ TIrzCpzhatjuHLV/RQey5UnmrOxBblNrjRSeSPjXxLdcsv8tu0k/a/KAlp9/VXA05x3x /XSttm4psEgF3lwzX137MbMRW24jgqnTJOEsN5BHZdY4zGrLJPY3KP26aYp9w5736QXh fCK0Xjjd8haFir2dZuQXJ/a2bM6DXOIuPQcpL64W0OrCuOeQ16ZT4RlKyOrsj+tFNYz0 qZ0w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q3si19478752pgg.407.2019.05.20.11.09.09; Mon, 20 May 2019 11:09:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388573AbfETOSo (ORCPT + 99 others); Mon, 20 May 2019 10:18:44 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:58780 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1733264AbfETOSn (ORCPT ); Mon, 20 May 2019 10:18:43 -0400 Received: (qmail 1770 invoked by uid 2102); 20 May 2019 10:18:42 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 May 2019 10:18:42 -0400 Date: Mon, 20 May 2019 10:18:42 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Marek Szyprowski cc: linux-usb@vger.kernel.org, , , Greg Kroah-Hartman , Bartlomiej Zolnierkiewicz , Markus Reichl , =?UTF-8?q?M=C3=A5ns=20Rullg=C3=A5rd?= , Krzysztof Kozlowski , Peter Chen Subject: Re: [PATCH v5] usb: exynos: add workaround for the USB device bindings conflict In-Reply-To: <20190520090823.17189-1-m.szyprowski@samsung.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 May 2019, Marek Szyprowski wrote: > Commit 69bec7259853 ("USB: core: let USB device know device node") added > support for attaching devicetree node for USB devices. Those nodes are > children of their USB host controller. However Exynos EHCI and OHCI > driver bindings already define child-nodes for each physical root hub > port and assigns respective PHY controller and parameters to them. Those > bindings predates support for USB device tree nodes. > > To mitigate the side-effects of the conflict between those bindings, > lets reset Exynos host controller of_node pointer before registering it > to USB subsystem. This fixes the issue raised by the commit 01fdf179f4b0 > ("usb: core: skip interfaces disabled in devicetree"), which incorrectly > disabled some devices on Exynos based boards. > > Reported-by: Markus Reichl > Suggested-by: Måns Rullgård > Signed-off-by: Marek Szyprowski > --- > v5: > - fixed error path handling as pointed by Alan Acked-by: Alan Stern This is assuming the whole approach makes sense in the first place -- I'll defer to other people's judgement on that. Alan Stern