From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752661AbbJWULf (ORCPT <rfc822;w@1wt.eu>);
	Fri, 23 Oct 2015 16:11:35 -0400
Received: from mout.kundenserver.de ([212.227.17.10]:58287 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752370AbbJWUKt (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 23 Oct 2015 16:10:49 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, arm@kernel.org,
        Russell King <linux@arm.linux.org.uk>, devicetree@vger.kernel.org,
        Kumar Gala <galak@codeaurora.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
        Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH 2/3] ARM: dts: uniphier: add ProXstream2 Vodka board support
Date: Fri, 23 Oct 2015 22:10:01 +0200
Message-ID: <4176900.TvBCpZCKl2@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAK7LNAQG-aqu0khSMZYLqd0P_Oz4MPuQccTMb0nYeR5JthnKhA@mail.gmail.com>
References: <1444899934-4754-1-git-send-email-yamada.masahiro@socionext.com> <CAK7LNARJhpz0AmLDL9j5c20cnv=+7CGiJMgGHhreJEd0rG3zSw@mail.gmail.com> <CAK7LNAQG-aqu0khSMZYLqd0P_Oz4MPuQccTMb0nYeR5JthnKhA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:vbZtFGokKGaPFeG0mWZ3T8jz0OOD3FSyXSzTas4Z3r203pdXKhB
 PK4u4B5GZ7NVqPZ/A4b67H1fuHWUXVpkJGwH6WKKlX64i39sD63/26P7qxsl5TFDlGyHFp0
 XH2gDifV9vcU8xib5QqDM+x5gdZAeUdbXvhX/iaI0G2mn5pD2seV4olWWsghYKpY1km8N9u
 g9LK2BmPo6AZobfV0t2oA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:75DPS4gErIE=:ZYY18rVYHM4BHK4yDaNrpr
 JaDJis1gcZugRiuDL5Euj13+K5MAY0mCBptjglg3e1fN12xuBTt6M5hpAwpj66J+wbVF7XPO4
 9WgKuMaJeiZweFxI/M/21cwZ47ax8d8lujX3tGu5N61ys/DbnCcjq3pjv5seGR1PzfjVA8uRn
 Lg5QQj+deuZEmF2qehONfU0bZYqV4o3UQEnwgCwYNrApneen9ihjGy2T8aGWUmAili2HeIIFN
 0lSKs9EKe9Fi03N13A+svzUhbaqaGkE2bh5u7LeLvQakjnF0abB2X6RzO4jUmJCgKV0QM4V7c
 HP5DFTccgfNPJnLW2p/5zvKqFjOEuD1NodU9IRRRaNw8VXZOIUdxZ2cgyQ4ZjqMMQsV2UEt6+
 /FpayWfqzCTIR/9ZKposnzYHBK5A9Rio8bPgW6tHZjq7qQ4GfDxkI15Ru1JdPkL9yF85L/hsO
 uhC5M+C0V57DG7fWeKXluYQFVVAW/FDKSyjrNiAXvIj8QhV7VSAwTSBQj89Cp5wim33+GY4eo
 gUVMIkKMzmfo2y38mqIXqGSsFrMiaT0xx85/EJSk5Ep/a0Zg+iCwBR/5tK1NHfamohq7UCmWi
 OMtErGjtnmt/UWPanoSPg0y8vv9Rkr9a4cygkQAC5AHqVzW9HYngSY8tBxS0FricTsy+N7piL
 PxvL2wLORja3dsWHu2OtljbqmaiLMwmJ8l6u5zZiO3tM/g5F136JjHHnfdVEmhgmdCo4IfMT2
 U2gVqVwig9SCWj5p
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wednesday 21 October 2015 17:49:12 Masahiro Yamada wrote:
> > Right.  In-kernel drivers can handle it nicely.
> >
> > Also, we can write a device tree that specifies device connection
> > hierarchy like follows.
> > The device names will appear under /sys/ directory and user-land
> > applications can check them.
> >
> > &i2c4 {
> >         demodulator {
> >                  compatible = "...";
> >
> >         };
> > };
> >
> > &i2c6 {
> >          hdmi_tx {
> >
> >                    compatible = "...";
> >          };
> > }
> >
> >
> > I understand that I2C bus number assumption is avoidable,
> > but I am still not fully convinced.
> >
> > Matching /dev/i2c* and the real hardware block ID (this is written in
> > the SoC spec book)
> > makes things clearer, I think.
> >
> 
> 
> Anyway, this version is unacceptable, right?

Sorry for the late reply.

I would not call it unacceptable, just a bit unpleasant. We can merge it
if you cannot come up with a nicer way to do this. It was a good idea
to split to resend the series without this patch, but the replacement
to delete the aliases also doesn't look nice. If we can't come up with
a better way to do this, I'd suggest you re-send this patch and add a
bit more explanation into the changelog as to why you want this to
be done in an unusual way.

	Arnd