Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp87288imj; Thu, 14 Feb 2019 15:57:34 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia1TlqH169TeMfSEiEj9Fofhp5KvuBjT9PGnVoLzPqrUJ7+Rp/Z2x4B9QnnQyK2cQ/4mC5x X-Received: by 2002:a63:7909:: with SMTP id u9mr2539079pgc.243.1550188654691; Thu, 14 Feb 2019 15:57:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550188654; cv=none; d=google.com; s=arc-20160816; b=T+/m97TmVHtIgWpXiOsuPWXkY7p4OWQRxmGmFfGL8rNET/2QBIwZNpFrjbkTMO8TCb 8WLz+BNPnLGBaaGARoglcLiB5WboEpcrGDbZq8tUUKm707bIBa+pmYdaeBQvQkVJtSTr zaga9fsYIGL2RaXFqrNtAIoMtcraCctyVwrP1+N7HSgMy4T6PrxokNF5gKi7OstpXxLU 2z5FxL3+5Dn7S5bIhEaVD7J7+umHOPgJ5CHLvGaOE4h27YYaG1EwTFaKN29cHaFHVjxL COX1IXWUYhqvR64BgVfIYQ82K35DJaHPp3MM8CBEgmrjbaSaipKUGo1Qy76n1+SIqL9z 20ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=9EUuUrJHWrEk9alEU5LDm2lgx67/+qK6n6oVJcUIqKE=; b=xsw9zrD8Xq024xX65V9S76enQQ3T3UcRlpcl/MtMQi9DwsIyx3VZ0dcJ6FFvGZ8Tq3 Brrnjsa1cry+Hw0CuwQYU0/6NAmmOO4beppnLUk0vMERP9R1DnNpQS8mn3voofzD2LZB Uc0RdO6SB+qSCXpSv3ii2clb8kOiMBNKEJU3pgBfIXhVrteg89ZKPGAmAHN5D3J9y3MU fNJFtoiQMJEsqWOLLj0B1v30kSGzSpME/InFEe+2SUrKBf57B7srvIoxfnBj1FwJ0tO6 gq/Pjj61xdJko++SVlzeWFEAFkX/EpF3fvk4XR4bAfUn+VHTEjaEr+hxpkkHg81sxiwt aELQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Svz+Gibv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g10si4057022plb.375.2019.02.14.15.57.18; Thu, 14 Feb 2019 15:57:34 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=Svz+Gibv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2439110AbfBNOBI (ORCPT + 99 others); Thu, 14 Feb 2019 09:01:08 -0500 Received: from mail.kernel.org ([198.145.29.99]:39104 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2439061AbfBNOBH (ORCPT ); Thu, 14 Feb 2019 09:01:07 -0500 Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D336F222DE; Thu, 14 Feb 2019 14:01:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550152866; bh=6dtKPkH/uDQESpU6qBBIquRox/r60tN5RWiDWKr0Ogg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Svz+Gibv/h5Sr+AabfgVnLWAxlyrKKkIVa++AshGEKKYQ0VuXCZ8+SZnmnMTiPHr/ BgE/Io/CHxYT4O5mTgdqcT27EMzouU1kAtrpoSEFTpg1iVNr4+YP9b4EidM4d4S/9A exT4XYjrP+sGSqsoFLd4+uC3LIbvvJIv+ixAVXls= Received: by mail-qt1-f180.google.com with SMTP id y4so6874664qtc.10; Thu, 14 Feb 2019 06:01:05 -0800 (PST) X-Gm-Message-State: AHQUAuahuUWUzKxRY8+dg17BilfbhL2tralBch5j8RJ+QY9OkoRN8b3C UnZCAs66eZyKWCcgKnbBk/3+ajzaczPABy2idQ== X-Received: by 2002:ac8:2a39:: with SMTP id k54mr3215870qtk.26.1550152864928; Thu, 14 Feb 2019 06:01:04 -0800 (PST) MIME-Version: 1.0 References: <1548935553-452-1-git-send-email-pawell@cadence.com> <1548935553-452-2-git-send-email-pawell@cadence.com> <20190213224841.GA9319@bogus> In-Reply-To: From: Rob Herring Date: Thu, 14 Feb 2019 08:00:52 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 1/6] dt-bindings: add binding for USBSS-DRD controller. To: Pawel Laszczak Cc: "devicetree@vger.kernel.org" , "gregkh@linuxfoundation.org" , "mark.rutland@arm.com" , "linux-usb@vger.kernel.org" , "hdegoede@redhat.com" , "heikki.krogerus@linux.intel.com" , "andy.shevchenko@gmail.com" , "rogerq@ti.com" , "linux-kernel@vger.kernel.org" , "jbergsagel@ti.com" , "nsekhar@ti.com" , "nm@ti.com" , Suresh Punnoose , "peter.chen@nxp.com" , Pawel Jez , Rahul Kumar Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 14, 2019 at 12:08 AM Pawel Laszczak wrote: > > Hi Rob, > >On Thu, Jan 31, 2019 at 11:52:28AM +0000, Pawel Laszczak wrote: > >> This patch aim at documenting USB related dt-bindings for the > >> Cadence USBSS-DRD controller. > >> > >> Signed-off-by: Pawel Laszczak > >> --- > >> .../devicetree/bindings/usb/cdns-usb3.txt | 33 +++++++++++++++++++ > >> 1 file changed, 33 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/usb/cdns-usb3.txt > >> > >> diff --git a/Documentation/devicetree/bindings/usb/cdns-usb3.txt b/Documentation/devicetree/bindings/usb/cdns-usb3.txt > >> new file mode 100644 > >> index 000000000000..6dc38be77f5c > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/usb/cdns-usb3.txt > >> @@ -0,0 +1,33 @@ > >> +Binding for the Cadence USBSS-DRD controller > >> + > >> +Required properties: > >> + - reg: Physical base address and size of the controller's register areas. > >> + Controller has 3 different regions: > >> + region 1 - HOST registers area > >> + region 2 - DEVICE registers area > >> + region 3 - OTG/DRD registers area > >> + - reg-names - register memory area names: > >> + "xhci" - for HOST registers space > >> + "dev" - for DEVICE registers space > >> + "otg" - for OTG/DRD registers space > >> + - compatible: Should contain: "cdns,usb3-1.0.0" or "cdns,usb3-1.0.1" > >> + - interrupts: Interrupt specifier. Refer to interrupt bindings. > >> + Driver supports only single interrupt line. > > > >Driver supports or h/w only has 1 interrupt? > > h/w internally has 3 separate interrupt line, but in my testing board > they are ored. So physically driver sees only one h/w interrupt line and > assumes that h/w has single common interrupt line. If it is possible for others to have 3 separate lines then you should have 3. Just repeat the connection 3 times. Or the binding can support 1 or 3 interrupts based on the h/w. Either way it's not about what the driver supports, but what the h/w looks like. > >> + This single interrupt is shared between Device, > >> + host and OTG/DRD part of driver. > >> + > >> +Optional properties: > >> + - maximum-speed : valid arguments are "super-speed", "high-speed" and > >> + "full-speed"; refer to usb/generic.txt > >> + - dr_mode: Should be one of "host", "peripheral" or "otg". > >> + - phys: reference to the USB PHY > >> + > >> +Example: > >> + usb@f3000000 { > >> + compatible = "cdns,usb3"; > > > >Doesn't match above. > Right, should be: > Compatible = " cdns,usb3-1.0.0", "cdns,usb3-1.0.1"; No, that doesn't match either. Above you said "or". Rob