From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942721AbdAJTVc (ORCPT ); Tue, 10 Jan 2017 14:21:32 -0500 Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:35659 "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S942424AbdAJTUi (ORCPT ); Tue, 10 Jan 2017 14:20:38 -0500 Subject: Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling To: Krzysztof Kozlowski References: <20170110022131.31042-1-shuahkh@osg.samsung.com> <2265318.ybtxfiNn3d@amdc3058> <1659345.4CcVdVckN5@amdc3058> <23cf318d-b83f-55e6-e980-13133f0ceb8b@osg.samsung.com> <20170110185943.qxwnzjg6zzy4zbki@kozik-lap> Cc: Bartlomiej Zolnierkiewicz , Anand Moon , linux-arm-kernel , Felipe Balbi , Greg Kroah-Hartman , Kukjin Kim , Javier Martinez Canillas , "linux-samsung-soc@vger.kernel.org" , Linux USB Mailing List , Linux Kernel , Shuah Khan From: Shuah Khan Message-ID: Date: Tue, 10 Jan 2017 12:20:35 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20170110185943.qxwnzjg6zzy4zbki@kozik-lap> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/10/2017 11:59 AM, Krzysztof Kozlowski wrote: > On Tue, Jan 10, 2017 at 11:37:24AM -0700, Shuah Khan wrote: >> On 01/10/2017 11:23 AM, Bartlomiej Zolnierkiewicz wrote: >>> I also think that regardless of what is decided on making susp_clk >>> non-optional for some Exynos SoCs we should probably remove the debug >>> message as it doesn't bring useful information and may be confusing. >>> >>> Shuah, can you take care of this? >> >> Yes. This message as it reads now is not only confusing, but also can >> lead users to think something is wrong. >> >> I can get rid of it or I could change it from info to debug and change >> it to read: >> >> "Optional Suspend clock isn't found. Diver operation isn't impacted" > > It is even more confusing. If the clock is required (by binding, by > hardware) - make it an error. If it is completely not important - do not > print anything. If it is optional but helpful (enabling clock gives > someything) then print something... but it is not that case. > > Best regards, > Krzysztof > Sounds fair. I will send a patch to remove the message. -- Shuah