Received: by 2002:a25:b323:0:0:0:0:0 with SMTP id l35csp2433344ybj; Mon, 23 Sep 2019 03:51:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqyKmYRQM+E2U/mteZn6dEXwpdo4WVHVvm8g4xGWx9ukh51FRHckzme/uArFj5IPU2ofNfru X-Received: by 2002:a17:906:129b:: with SMTP id k27mr28939508ejb.42.1569235899348; Mon, 23 Sep 2019 03:51:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569235899; cv=none; d=google.com; s=arc-20160816; b=LJMokO/rDjyrtE92/dQV4iEP8U+2bdS7dngDC15FD//YoBxegdBJejCwLeasKuRnHt mxfbBkKqweaJ+G48StOsQfJ9yuaw6pFVWYvC/4dSI602edOFUcl29hAa81D6TDGqqj3m 3q4Bs+YBxOXmnSZn3H7R8jNhg9jOBdaAHAmDObMCML979WcfCnvmg5LGz9y0xEyryEXw DsMl9kRlGMHD/jFeYh7v0El+3PQR8+5pg+Cgrv5VCsC/0a/viMbYtwrQcD1Cd2+I7WCp iQbs89H9Qm2/mNxNCIpLpmvb3DvgiIYlqoJdv2/Fn9zwFHDMdo1WytvVH/M7DybV/8+w 4vXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=YmwvldoBPWC/WT/RXbjQtuTjZqYBNPW2mhbUP/g7mkk=; b=xHZLg5LC9DCPCAeL8dEz5pts5I7OCJQE0BMFYQSUQinXQZKEdDA3vtGtWSo9XY8Uf0 /ohqUSwd2Ba8gPAQiu1jROJIyqIxDlWLAcIyFPC1Q2Y9EbnynxWaMrf5Ye+BRHUoh0V0 PskUlNQW/Q7e7xBrW7zuAvsp3WGOR+88z/eheULaeRBaIxCmP8eQxKxFdHFNhna7NXPe y/3Q3kVzxj5sNM48ZHrveE/ouC98l5tr2yr8WQ2B5dWUH0CaNrBfQMh4nst1Fs01HO1s BlVLmEkFmMMqEcPH1u1K1OV7Ojtgwn1Zar7WDUhdPtRpAjLGBlzeRfA2wsaH4MrnlBOJ 2HJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=KXKI5iR+; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e23si6314700edq.344.2019.09.23.03.51.15; Mon, 23 Sep 2019 03:51:39 -0700 (PDT) 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=@gmail.com header.s=20161025 header.b=KXKI5iR+; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728458AbfITUPP (ORCPT + 99 others); Fri, 20 Sep 2019 16:15:15 -0400 Received: from mail-wr1-f65.google.com ([209.85.221.65]:35946 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbfITUPP (ORCPT ); Fri, 20 Sep 2019 16:15:15 -0400 Received: by mail-wr1-f65.google.com with SMTP id y19so8030093wrd.3; Fri, 20 Sep 2019 13:15:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=YmwvldoBPWC/WT/RXbjQtuTjZqYBNPW2mhbUP/g7mkk=; b=KXKI5iR+QlI/KdDF+TIMTQSlIAEIU2NwdpjFNc77gTncHwCvgnKDhePDMeIjIZE21o fk7io/Zq82vh7JgzlX7ZEaben9WMf+nAuHjT3Kcf5JbG8OeNxKDLguEe/SForVK9sxJN eKjU2vhPKI14DwZoFCvVEEfjdKrB0Al82TRTLedoaxeFX9V9S5he7TT7P5/HEpcX8hhI 3FPCkC75lqUP/F06P9hAFD+dMVV2J38iSSaGjASUVGzZx4LMax+pjJWk8FmWBIUMlXDN zwyumFFjA/Of7xc3IQnBgohzEsoEh1RwmIKet7Xwdp+c2+BRqZbMle2gp17fMmw8HC/2 D+uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YmwvldoBPWC/WT/RXbjQtuTjZqYBNPW2mhbUP/g7mkk=; b=M5Tv3HC6LRQo+eFHrSNhtIyFbmEzfN0IFYWWxAhW0jmjcursKm/ZUjzFlSBCby4r9J 7VFD8iBU23vsuiyoZj0cWXKMZhtXKQ4Tv+4X2N2GmqomFhnMDn/Moloz4QrRRZlFJT9k 8AIoAQysTI18AXkEoi9qU/JGyW3zF/jO6Xio+3SAQMmJpI1XatHIAjRDbdwsng3uxrOx 93xSiX03SJWHdYOzIOPK9GBCk/qbX0jvLfNngK4IykXBiZ21tsjnLlAmJb3bK+xM5Cxl tmeUqc8HvXgvERmc8AzaAk3RgECVEsAp0DJkTxoTEKg9pvp6N68foKaZrDDFu25zRxMP kI8A== X-Gm-Message-State: APjAAAXSE9OIGN0I7fcGZXe7iauv8fX7/eFjQZNBdt8ITrX1Do9Ntifl 0pFSP7NwaKDO0BNc5Z5SNn1jy/wr X-Received: by 2002:adf:f406:: with SMTP id g6mr12752046wro.325.1569010512960; Fri, 20 Sep 2019 13:15:12 -0700 (PDT) Received: from [192.168.2.202] (pD9E5A855.dip0.t-ipconnect.de. [217.229.168.85]) by smtp.gmail.com with ESMTPSA id w22sm2121846wmc.16.2019.09.20.13.15.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Sep 2019 13:15:12 -0700 (PDT) Subject: Re: [PATCH] serdev: Add ACPI devices by ResourceSource field To: Hans de Goede Cc: Rob Herring , Greg Kroah-Hartman , Jiri Slaby , Johan Hovold , "Rafael J . Wysocki" , Len Brown , linux-serial@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190919195624.1140941-1-luzmaximilian@gmail.com> <79c9533f-882d-f2b2-b6f3-b94fa49b4367@redhat.com> From: Maximilian Luz Message-ID: Date: Fri, 20 Sep 2019 22:15:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <79c9533f-882d-f2b2-b6f3-b94fa49b4367@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 9/20/19 10:50 AM, Hans de Goede wrote: > Also I will give this a test-run on some of the existing devices > which rely on the instantiation of serdev devices for ACPI > devices which are childs of the uart device. Thank you for testing! Will get to your other mail shortly. > Given the above I think you may want to also limit your patch to > only instantiate a "struct device" for the first UARTSerialBusV2 > in an ACPI "Device()"'s . Right, I will change this for a v2 once the issue revealed by your testing has been resolved. > I hope this sheds some clarity on the (muddy) situation wrt > I2cSerialBusV2 handling. Thank you again, this has definitely helped clear things up for me and your write-up is much appreciated! Maximilian