Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp93619imu; Tue, 22 Jan 2019 14:32:12 -0800 (PST) X-Google-Smtp-Source: ALg8bN4pRqs8pmXl6UWU5PSb0fhjO71oHAGcsBN3NJccso+BKKmWe3ReLxym4V1zhSdx2Bu+CXn0 X-Received: by 2002:a17:902:780a:: with SMTP id p10mr36895694pll.54.1548196332432; Tue, 22 Jan 2019 14:32:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548196332; cv=none; d=google.com; s=arc-20160816; b=c0BofGP4PNU4Tf/NKgEM2x8rR7F9XpC9MvgMDkssOtAIZQyym1Y/QxAPbO9CArxHGf ugwhaZv1IXTyHNzL6nbRO6JramReJPBZrxjqkeEnqpVQA24cGWv4Pgm5EMFd2PtpdWV4 JIn8XlOoZav+R72N7fc4xl18ny77l83tjNKhXhWwwZqGlAgYX3pi5sVrlvYi+D6J6Jag eZcKILptmLD9VAczpJkYfbpf+zcRaDvHYV7ok3YZBkXe1SjqksHE+9y+MwFIuD6fAl2f O+b3arK5GJ9euKJ4qzyypFj9Y0kp6XyX5ObF31xjZGrAGRXpittkwhmXgClWkAB9BF5w Mfhw== 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=KfJaF5rZw1WpHVeU/lKvjOAxKYjfNoAOiPQJd080AZ4=; b=RCfr0Hpmfmjz4hc03tFZ8G4eglDRyo+oKxHPrGGyPo86DkHuu8caW/EOmsSU0097Qp zgd6cS3u3qJj387p7GYIwGllnXQ8dJYF6PnnAYtWUyzxC/mVVHuy3QxJSNWcK8LOgrcX H2H5FwT8cVDmfuWN+Y+XvmvwIi9wsdWEm9+M3kDnrAOU2Ez1vpZ+4pZb4R9GgOVtksIa r+VhXWHJIGEU8GI5Q+yZDZimEbnyn6kPlEGvXHMJms9k3SPrg1C2Lq5VxbHSN6xKgedK CqT5NaEkTzgkRsbC0GOgDBgZWyrTUZXYYTvoNnhHnIWQLtzlgag2rQFeO0Sk/IefJmPV fzLw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=s09DgXtq; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w7si11206243pfw.200.2019.01.22.14.31.54; Tue, 22 Jan 2019 14:32:12 -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=@google.com header.s=20161025 header.b=s09DgXtq; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726945AbfAVWaT (ORCPT + 99 others); Tue, 22 Jan 2019 17:30:19 -0500 Received: from mail-lf1-f67.google.com ([209.85.167.67]:44308 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726825AbfAVWaT (ORCPT ); Tue, 22 Jan 2019 17:30:19 -0500 Received: by mail-lf1-f67.google.com with SMTP id z13so100913lfe.11 for ; Tue, 22 Jan 2019 14:30:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KfJaF5rZw1WpHVeU/lKvjOAxKYjfNoAOiPQJd080AZ4=; b=s09DgXtqesxzUaza8JYBpsdlUDWrSwx53RNeaveBTAs4fzYVQLbg6Gcp0hzLpdtCTK DA7gqLbUWqunLgFl1Zhk6DnwBQ6sjDMyvZI8hYrEXzbghUmt+NfR+GInFq8RbHux1iqi 6nMez5BHpcdnLkC5/TqfVEba47uLTriutWpDsQs3t9aMFpqZl1cTqnYvnTVuhM46E3d3 f8qSvMoODQLxS770Zq+o3FjKXuORKLmcnw5YJ8NR8JtGnqeC156uuGbs72wpGYIDPPIn wH6uuugwfZGf9txAMsAlOtrO6ErUKHtL35UkyduyPBuUgHka35zt4QkxZ2FiKJmvIQjr dhmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KfJaF5rZw1WpHVeU/lKvjOAxKYjfNoAOiPQJd080AZ4=; b=f17/K9FehX9FgNuithh901KQ6HuvcEB9UljZzCo4GBfBGtGUf4XIcC6tMZI67HDjqU h2Xo1/n7+B+qw6My1DUIw0W4ofC6y8bX4zU54P7VP1YIqZqvFyKvxZnqmZ42zPuSwB0c lQdrpxw6etGhYTL+tl8RyMi8JkhgYDx6v1v17SsEbtZgtUaVmnzCZjELY7boJEo3+lTS R+LN0a4Zp/x93vsJTrvsAuE8G2vvpXn8dx+dY942jnvFFkw1GT35azhQvnLcmgloXuTx sSXHTDTCMXfDY1S9TVSY33MaPR0mK2u26IPoHKLlsMvDfyYDWXjruQzvCmt8+SA7aHOp dF5A== X-Gm-Message-State: AJcUukdsyTnHotKlsnmWnHisKztqokFWWQld9Urlts9Ua/wSG2/uIlfG LYUVzGrIiSiXCrEW5OK++9Hoh8Yok6vF8vSV1Xz27g== X-Received: by 2002:a19:db82:: with SMTP id t2mr23272607lfi.130.1548196216989; Tue, 22 Jan 2019 14:30:16 -0800 (PST) MIME-Version: 1.0 References: <20181117010748.24347-1-rajatja@google.com> <20190118223407.64818-1-rajatja@google.com> <20190118223407.64818-2-rajatja@google.com> <77FFC08C-D038-4BBE-9153-FBA1701D3168@holtmann.org> In-Reply-To: <77FFC08C-D038-4BBE-9153-FBA1701D3168@holtmann.org> From: Rajat Jain Date: Tue, 22 Jan 2019 14:29:40 -0800 Message-ID: Subject: Re: [PATCH v4 2/5] usb: assign ACPI companions for embedded USB devices To: Marcel Holtmann Cc: Johan Hedberg , Greg Kroah-Hartman , "David S. Miller" , Dmitry Torokhov , Alex Hung , linux-bluetooth@vger.kernel.org, Linux Kernel Mailing List , linux-usb@vger.kernel.org, netdev@vger.kernel.org, Rajat Jain , Dmitry Torokhov , raghuram.hegde@intel.com, chethan.tumkur.narayan@intel.com, "Ghorai, Sukumar" 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 Sat, Jan 19, 2019 at 11:51 AM Marcel Holtmann wrote: > > Hi Rajat, > > > USB devices permanently connected to USB ports may be described in ACPI > > tables and share ACPI devices with ports they are connected to. See [1] > > for details. > > > > This will allow us to describe sideband resources for devices, such as, > > for example, hard reset line for BT USB controllers. > > > > [1] https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/other-acpi-namespace-objects#acpi-namespace-hierarchy-and-adr-for-embedded-usb-devices > > > > Signed-off-by: Dmitry Torokhov > > Signed-off-by: Rajat Jain (changed how we get the usb_port) > > Acked-by: Greg Kroah-Hartman > > Tested-by: Sukumar Ghorai > > --- > > v4: Add Acked-by and Tested-by in signatures. > > v3: same as v1 > > v2: same as v1 > > > > drivers/usb/core/usb-acpi.c | 44 +++++++++++++++++++++++++++++-------- > > 1 file changed, 35 insertions(+), 9 deletions(-) > > same question here. Which tree is suppose to take this? Just responded to the 1st patch. Since the subsequent patches use this feature, may be best to push this via your tree. Greg or Dmitry can suggest if they have any other suggestions. > > Regards > > Marcel >