[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200519032936.jyav3fhopumymo4h@vireshk-i7>
Date: Tue, 19 May 2020 08:59:36 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: Felipe Balbi <balbi@...nel.org>,
Georgi Djakov <georgi.djakov@...aro.org>,
Matthias Kaehlcke <mka@...omium.org>,
Sandeep Maheswaram <sanm@...eaurora.org>,
Andy Gross <agross@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Stephen Boyd <swboyd@...omium.org>,
Doug Anderson <dianders@...omium.org>,
linux-arm-msm@...r.kernel.org, linux-usb@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Manu Gautam <mgautam@...eaurora.org>,
Chandana Kishori Chiluveru <cchiluve@...eaurora.org>
Subject: Re: [PATCH v7 2/4] usb: dwc3: qcom: Add interconnect support in dwc3
driver
On 18-05-20, 11:35, Bjorn Andersson wrote:
> This misses the case where INTERCONNECT=n and USB_DWC3_QCOM=[ym] which
> I don't see a reason for breaking.
>
> But if only INTERCONNECT where a bool, then we don't need to specify a
> depends on, because it will either be there, or the stubs will.
> We've come to this conclusion in a lot of different frameworks and I
> don't see why we should do this differently with INTERCONNECT.
INTERCONNECT is a bool now and the patch has been pushed to linux-next
already.
--
viresh
Powered by blists - more mailing lists