From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=gp+X=WL=vger.kernel.org=linux-kernel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id CE2C0C3A589
	for <linux-kernel@archiver.kernel.org>; Thu, 15 Aug 2019 20:56:22 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 991F02089E
	for <linux-kernel@archiver.kernel.org>; Thu, 15 Aug 2019 20:56:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1565902582;
	bh=CurYYhwg/rTAP0CdgcbXS3++QbH1EutUlsXldHCNbaA=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=jF3irwikErEvQTnJD5jTPcVsRHXurM9mJ4UDKRY/fz+8SJISenmrLvAXsXLv1qmce
	 ekiEA5uc1B9CBijRm0otuJ5F18lOkkpy4QQTopjzWgx2tuCYiVbHvM5qtyJxq9UjZU
	 2d1suAhtZkHDASlT+AfJ0i9m+f7ov2k3Evaw2Ti4=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1732964AbfHOU4V (ORCPT
        <rfc822;linux-kernel@archiver.kernel.org>);
        Thu, 15 Aug 2019 16:56:21 -0400
Received: from mail.kernel.org ([198.145.29.99]:42144 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1730540AbfHOU4V (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 15 Aug 2019 16:56:21 -0400
Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id 4F84D2086C;
        Thu, 15 Aug 2019 20:56:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1565902580;
        bh=CurYYhwg/rTAP0CdgcbXS3++QbH1EutUlsXldHCNbaA=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=J7yaYGqLZ8WizZ5FBQ2faP59qa6jwrcpYkOF99kaTrn0FUVPA9SFsJFHb5tcdhetP
         k8tFlSqW3CmNBjFqtSY1zd7fVHqhMrNdOxBVKBORTm2ppqSDA21gdYovncrIWyTZH2
         kMGxTokkljHjq/H1PZsLBeQycFPpztdYRc7fQ6Oc=
Date:   Thu, 15 Aug 2019 22:56:18 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Daniel Mack <daniel@zonque.org>
Cc:     devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: uio_pdrv_genirq: Make UIO name controllable via DT
 node property
Message-ID: <20190815205618.GA11877@kroah.com>
References: <20190811110213.5537-1-daniel@zonque.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190811110213.5537-1-daniel@zonque.org>
User-Agent: Mutt/1.12.1 (2019-06-15)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, Aug 11, 2019 at 01:02:13PM +0200, Daniel Mack wrote:
> When probed via DT, the uio_pdrv_genirq driver currently uses the name
> of the node and exposes that as name of the UIO device to userspace.
> 
> This doesn't work for systems where multiple nodes with the same name
> (but different unit addresses) are present, or for systems where the
> node names are auto-generated by a third-party tool.
> 
> This patch adds the possibility to read the UIO name from the optional
> "linux,uio-name" property.

Does that need to be documented anywhere?

thanks,

greg k-h