Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755308AbaKRRNF (ORCPT ); Tue, 18 Nov 2014 12:13:05 -0500 Received: from mail-vc0-f171.google.com ([209.85.220.171]:53703 "EHLO mail-vc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755270AbaKRRNA (ORCPT ); Tue, 18 Nov 2014 12:13:00 -0500 MIME-Version: 1.0 In-Reply-To: <20141118003305.GB11280@saruman> References: <1416264102-1323-1-git-send-email-abrestic@chromium.org> <1416264102-1323-10-git-send-email-abrestic@chromium.org> <20141117231240.GB9716@saruman> <20141118003305.GB11280@saruman> Date: Tue, 18 Nov 2014 09:12:58 -0800 X-Google-Sender-Auth: GBNWgMtJVe6-zCRATVOpwZT3EXA Message-ID: Subject: Re: [PATCH V5 09/12] usb: xhci: Add NVIDIA Tegra xHCI host-controller driver From: Andrew Bresticker To: balbi@ti.com Cc: Stephen Warren , Thierry Reding , Alexandre Courbot , "linux-tegra@vger.kernel.org" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Jassi Brar , Linus Walleij , Greg Kroah-Hartman , Mathias Nyman , Grant Likely , Alan Stern , Arnd Bergmann , Olof Johansson , Kishon Vijay Abraham I , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-usb@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 17, 2014 at 4:33 PM, Felipe Balbi wrote: >> >> +static int tegra_xhci_load_firmware(struct tegra_xhci_hcd *tegra) >> >> +{ >> >> + struct device *dev = tegra->dev; >> >> + struct tegra_xhci_fw_cfgtbl *cfg_tbl; >> >> + struct tm fw_tm; >> >> + u32 val, code_tag_blocks, code_size_blocks; >> >> + u64 fw_base; >> >> + time_t fw_time; >> >> + unsigned long timeout; >> >> + >> >> + if (csb_readl(tegra, XUSB_CSB_MP_ILOAD_BASE_LO) != 0) { >> >> + dev_info(dev, "Firmware already loaded, Falcon state 0x%x\n", >> >> + csb_readl(tegra, XUSB_FALC_CPUCTL)); >> >> + return 0; >> >> + } >> > >> > won't this prevent rmmod && insmod from succeeding ? Maybe not, as you >> > return 0 anyway, but if the firmware side craps out, it might be useful >> > to reload the firmware and reset that block. I wonder if this prevents >> > that. >> >> rmmod && insmod does work with the above since, as you mentioned, we >> return successfully if the controller is already running. Attempting >> to re-load the firmware if the controller is already running won't >> work - it requires a full power-gate/ungate sequence of the >> controller. Unfortunately, that sequence is rather complicated and I >> haven't had a chance to implement it yet. it will hopefully be coming >> later, though. > > Alright, could you add a comment on the source code stating that ? > Perhaps a REVISIT note or FIXME ? Sure, will do. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/