Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp750746ybb; Wed, 8 Apr 2020 09:10:38 -0700 (PDT) X-Google-Smtp-Source: APiQypKmRgiBRBNc/8aBIPqJ0O4CLXAvPD5PaianXmqwWpL8gL1jEWepbgUP4VQmkFlhozAHuW2E X-Received: by 2002:a05:6830:1313:: with SMTP id p19mr450069otq.179.1586362238033; Wed, 08 Apr 2020 09:10:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586362238; cv=none; d=google.com; s=arc-20160816; b=lN25Yw5qy26Cf8wi0WCXQxFOxbbKO4IEW2PIuesr2H9anH5r7e0rugaPjvHNGaUnSc wNM2I3ex5MvN/zQoDhUtksaAXUa5oDuMsg2OL89VJ02D/vtBnIQzfikOIwpt47KXj6Ub Kx+1pC8VNRb9tMkRAo4FnNR4NPVtrWk2K9McfVYyBCMrK2OBdLR/DNU2hEu8/F6MA+8D Y1N10aDXUzMs+dB7Kq1XzGM1MSd0JG/i9yQoYTJaOiZN7uRPzKi6jMAHPVNR682//C9Z hCDus+XD2psi5yGkoD5hzeBClk92O8pldBmH1U1PNB06pBByEtYXxdQPRA8UlVLlLVW2 33XQ== 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:mime-version :message-id:date:subject:cc:to:from:ironport-sdr:ironport-sdr; bh=6xEALJhSeXQEn+E75/MR3+vL9dzoSG5ZdoX7qXHqyQ0=; b=bjgYml69to1CYF99nTCnnBsmsUmStzQUKc2y+XQuQJveDs+QRZvKm/pKwAZ8ALhgh6 7DZasIQb+DqyAwFFt/RwLRgyTr9fCyxrsE1E2DIwrPwk2SVtVqIIXTDf0fhdkPBDHQHb 2na0ESmyHf+BNij6gUE19SGH6mcdfgvrkY37C2gei9sju933opxovGFKxcmtfBusj4Pu x5Uk2Ta0yT7fuWTiLvV6l2Dz8IEZ3hxC9q4yM43iYitqTNCUTjgmeFFc35JaECMGcT+m 4AGC1ZupgXOsL1m+TrHH1WBrO0n2sd1TsnSOYk76NCXJRgwwwXBnEJOT6HD2AEVn/WD/ p8EQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e22si2711848otr.6.2020.04.08.09.10.14; Wed, 08 Apr 2020 09:10:38 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730203AbgDHQJd (ORCPT + 99 others); Wed, 8 Apr 2020 12:09:33 -0400 Received: from mga02.intel.com ([134.134.136.20]:63799 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729808AbgDHQJa (ORCPT ); Wed, 8 Apr 2020 12:09:30 -0400 IronPort-SDR: 4JwhL5J0cj7U9/H0d2MbteuZBwQADikyRU8uEFWZ+INTNMqeUE/VsyD3h1dP7yNhbw9Tnx0R+a 7GR1EPpaMXcg== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Apr 2020 09:09:28 -0700 IronPort-SDR: 5iOVPGhhfw7aAOWYoReV+Bj+iDDvUXL4ajrWE57V2LowKP+KHPRgapnX4x+N3K4Ocb+WIKmTwN ixrWxoSLj/JQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.72,359,1580803200"; d="scan'208";a="451655833" Received: from black.fi.intel.com ([10.237.72.28]) by fmsmga005.fm.intel.com with ESMTP; 08 Apr 2020 09:09:26 -0700 Received: by black.fi.intel.com (Postfix, from userid 1003) id 66064130; Wed, 8 Apr 2020 19:09:25 +0300 (EEST) From: Andy Shevchenko To: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , linux-acpi@vger.kernel.org, Heikki Krogerus , Hans de Goede , platform-driver-x86@vger.kernel.org, Darren Hart Cc: Andy Shevchenko Subject: [PATCH v1 0/6] platform/x86: intel_cht_int33fe: clean up series Date: Wed, 8 Apr 2020 19:09:00 +0300 Message-Id: <20200408160905.12101-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When I started looking into the intel_cht_int33fe driver for an example of use software node API, I have noticed that it's hard to get and code a bit messy. Here is a clean up, main part of which is to introduce node groups and API to register and unregister them. This and some pre-existing APIs can be used in the driver. So, because of cross-subsystem nature of this series, I may recommend to create myself the immutable branch which can be pulled to Rafael's and Greg's trees respectively. I'm also open for other proposals how to proceed. Andy Shevchenko (6): device property: export set_secondary_fwnode() to modules software node: Allow register and unregister software node groups platform/x86: intel_cht_int33fe: Convert software node array to group platform/x86: intel_cht_int33fe: Convert to use set_secondary_fwnode() platform/x86: intel_cht_int33fe: Switch to use acpi_dev_hid_uid_match() platform/x86: intel_cht_int33fe: Fix spelling issues drivers/base/core.c | 1 + drivers/base/swnode.c | 48 ++++++++ .../platform/x86/intel_cht_int33fe_typec.c | 106 +++++++++--------- include/linux/property.h | 3 + 4 files changed, 108 insertions(+), 50 deletions(-) -- 2.25.1