Received: by 10.223.185.116 with SMTP id b49csp2482689wrg; Mon, 5 Mar 2018 03:47:13 -0800 (PST) X-Google-Smtp-Source: AG47ELs0zLlBfea4MsLWerv45ymeb545Fez2YxQEl2KOlUDEs/THFgZxQqB6clX6Y66+bvCoG1Ex X-Received: by 10.98.217.211 with SMTP id b80mr15325330pfl.107.1520250432939; Mon, 05 Mar 2018 03:47:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520250432; cv=none; d=google.com; s=arc-20160816; b=c7iE+KK5DYA71xj8SjA92iI52uw000Gv2upXZshdNI9j7RSllOWfpoY5D3j7IKXUE7 6coNhtdllQ0fpX2R5fRXLdaLfOK72ND8vIN7+q3lm39fc7Fa5ASYtEQteephRcmUy27n aeeAHyJviDtw170yHjZBZ6OLDHmhNMA9S3gw8o4HRUaRA3PrHQxF/w62KvlDvIUScjxa 4qUCSZ7EBdrrxIx5moNIgcThrb70XfIjqOJiMJ9VhUNLmFjCtvUNT460wzQtXFGXHeac QKqc84fHSXeBGw3uVd2F4QIGICTZhwrpdAdpRni4wkQ5ajcSU1HpLOHJ+QDTGSi0nxYw 6DeA== 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 :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=L1XCiu8gOLSJjmHbg8UJ+WPqXKN+OSVWGG+B6O0GBs0=; b=SnC2iw6RPnBLB43nH0Zpk+rxS+l3YWr8ORQ4xzE/UKU10hg4kYhoq88TIQ0VOcQs2n KKXZhFOZ4IwFQiV2QPfqBOoJ8OIqxHm47Yn0unZmOVHuUt5Zcdr3sazoAHst7VUEJTXp JU9XmGWA0efFifGgugME4iMxylBw7yF5cOCDPHCSgRixj3GjwoesI02x22AUQyx272d1 PGoYVn/pQ2ZT2It4wg4LIB/NKxXpVNXnGHwZs7lTMBNKWBmEwsgvonrm/OgZ9XfKFKoA me/A9NDjGLjCTDv2Ju7nuFTSPJnBgwh+HLGO/i2hnbRBWNlteJYXwbRdZdo1c2vBdEr+ 8Ekg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dowhile0-org.20150623.gappssmtp.com header.s=20150623 header.b=eMvFVRp2; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t74si404746pfk.160.2018.03.05.03.46.56; Mon, 05 Mar 2018 03:47: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=@dowhile0-org.20150623.gappssmtp.com header.s=20150623 header.b=eMvFVRp2; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933030AbeCELAG (ORCPT + 99 others); Mon, 5 Mar 2018 06:00:06 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:36448 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752423AbeCELAE (ORCPT ); Mon, 5 Mar 2018 06:00:04 -0500 Received: by mail-it0-f67.google.com with SMTP id u5so9499755itc.1 for ; Mon, 05 Mar 2018 03:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dowhile0-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L1XCiu8gOLSJjmHbg8UJ+WPqXKN+OSVWGG+B6O0GBs0=; b=eMvFVRp2zYrCrMrmLZprwe7pRoU/9MjpQZzlqcvq3DsjyT9yklvSkuHQTThcSh2Cnd lXxur7vDGE2ed7QL+VtFPzHD2a3V/iGUeXr3KlXEED2voXuj3D/1qfTrUgqjmXCf1ktU B4zagcy+l0ityqlO+KRCKXkWACpUFTL77rFu2hS04unq8P84IQR52e7JdMtZJrBKWFbp y0GlHKpE+z2Uoho5ZPi9eOwLabf7BuEnHAHI5FHehObFsjn9Z0ZFxGbNdbuk5rhHorAH OjTMWLksGY5w/lL0nRrU58bqjmKLz+9eembo0ecqqO4lyPOrSVLcCbJP3DxO6wUxmCD6 riZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L1XCiu8gOLSJjmHbg8UJ+WPqXKN+OSVWGG+B6O0GBs0=; b=iGwITus7TGcvgBG3IkEErolUTcDranyYogHPV0TlaE8g/Xn4HbQ+vqGMtVqfff7fJf CGerlnm/IJI0Tlactd9r1gPhmZBEtKxQVezunglq8kVH5TJ9fmc12xw7Wb3L8AMToAo9 cEIDC62RSuhiti3tRLpRk3V06YjQkMOLPeB7qI1RTA2hl08QFYlsuojCKO37JfbPCAEa u0L26uuJOjoj/yA3TiO9UEqawx5J4nN1KgYyJKnHqN3eLV+woLkiYAs/tNheFB3/G2Hx jLNrTZK4xyawxVsD6R4bpVSmTEMjR62q7LQJOeXXn6ncYLYAoM9XygE1FQo8zMHgtTfj 7WBw== X-Gm-Message-State: AElRT7EPPYWocVcPk47V9s19t77J2t7jt7XpL/wE/0/ahGocN0Zoy7QT AdX56kT9zAjhGQ+lgbVXfydmp0G9UdZb7Xu7UH+jwg== X-Received: by 10.36.69.234 with SMTP id c103mr12881419itd.57.1520247604326; Mon, 05 Mar 2018 03:00:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.158.133 with HTTP; Mon, 5 Mar 2018 03:00:03 -0800 (PST) X-Originating-IP: [90.77.100.34] In-Reply-To: References: <20171203214050.11482-1-javierm@redhat.com> From: Javier Martinez Canillas Date: Mon, 5 Mar 2018 12:00:03 +0100 Message-ID: Subject: Re: [PATCH] i2c: core: report OF style module alias for devices registered via OF To: Wolfram Sang Cc: Linux Kernel , Linux I2C , Javier Martinez Canillas 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 Hello Wolfram, On Sun, Jan 7, 2018 at 2:17 PM, Javier Martinez Canillas wrote: > > On Sun, Dec 3, 2017 at 10:40 PM, Javier Martinez Canillas > wrote: >> The buses should honor the firmware interface used to register the device, >> but the I2C core reports a MODALIAS of the form i2c: even for I2C >> devices registered via OF. >> >> This means that user-space will never get an OF stype uevent MODALIAS even >> when the drivers modules contain aliases exported from both the I2C and OF >> device ID tables. For example, an Atmel maXTouch Touchscreen registered by >> a DT node with compatible "atmel,maxtouch" has the following module alias: >> >> $ cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias >> i2c:maxtouch >> >> So udev won't be able to auto-load a module for an OF-only device driver. >> Many OF-only drivers duplicate the OF device ID table entries in an I2C ID >> table only has a workaround for how the I2C core reports the module alias. >> >> This patch changes the I2C core to report an OF related MODALIAS uevent if >> the device was registered via OF. So for the previous example, after this >> patch, the reported MODALIAS for the Atmel maXTouch will be the following: >> >> $ cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias >> of:NtrackpadTCatmel,maxtouch >> >> NOTE: This patch may break out-of-tree drivers that were relying on this >> behavior, and only had an I2C device ID table even when the device >> was registered via OF. There are no remaining drivers in mainline >> that do this, but out-of-tree drivers have to be fixed and define >> a proper OF device ID table to have module auto-loading working. >> >> Signed-off-by: Javier Martinez Canillas >> --- > > Any comments on this patch? > Is this patch under your radar? Should I keep pushing for it or just give up? Best regards, Javier