Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751158AbbEFQMn (ORCPT ); Wed, 6 May 2015 12:12:43 -0400 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.163]:44102 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750730AbbEFQMk convert rfc822-to-8bit (ORCPT ); Wed, 6 May 2015 12:12:40 -0400 X-RZG-AUTH: :JGIXVUS7cutRB/49FwqZ7WcKdUCnXG6JabOfSXKWrat+gdPsz+SM X-RZG-CLASS-ID: mo00 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [Gta04-owner] [PATCH 0/3] tty slave device support - version 3. From: "Dr. H. Nikolaus Schaller" In-Reply-To: <20150506142849.GA14839@amd> Date: Wed, 6 May 2015 18:12:34 +0200 Cc: List for communicating with real GTA04 owners , NeilBrown , Mark Rutland , One Thousand Gnomes , Arnd Bergmann , Greg Kroah-Hartman , Sebastian Reichel , Grant Likely , Jiri Slaby , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: References: <20150318055437.21025.13990.stgit@notabene.brown> <55492001.30806@hurleysoftware.com> <20150506092738.GB4508@amd> <20150506142849.GA14839@amd> To: Pavel Machek X-Mailer: Apple Mail (2.1878.6) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2879 Lines: 82 Hi Pavel, Am 06.05.2015 um 16:28 schrieb Pavel Machek : > On Wed 2015-05-06 13:50:29, Dr. H. Nikolaus Schaller wrote: >> Hi Pavel, >> >> Am 06.05.2015 um 11:27 schrieb Pavel Machek : >> >>> On Wed 2015-05-06 07:19:31, Dr. H. Nikolaus Schaller wrote: >>>> Hi Peter, >>>> >>>> Am 05.05.2015 um 21:54 schrieb Peter Hurley : >>>> >>>>> Hi Neil, >>>>> >>>>> On 03/18/2015 01:58 AM, NeilBrown wrote: >>>>>> here is version 3 of support for tty-slaves. >>>>> >>>>> Is there a v4 of this that I missed? >>>> >>>> We did have a lengthy discussion about [PATCH 3/3] how to best (1) >>>> represent the slave device in the device tree but as far as I am concerned, >>>> I do not see that we have a consensus (2) and the device tree maintainers >>>> have no comments or clear guidelines so far. >>> >>> Yes. Everyone and their dog disagrees >> >> What a wonderful argument? >> I still ask myself who the dog is. > > Ok, so now device tree maintainers spoke and told you, you are wrong, did they already say that and have more convincing arguments? So far I have always identified a flaw in the argumentation or a contradiction with practice (e.g. busses are usually addressable, McBSP and PHY do uses phandle and not subnodes). > and you still argue? And as long as I think the others are still wrong (focussed to see and model UART like a ?bus?), I tell them and explain my arguments where and why I disagree with what they say or propose. Especially if I feel that their arguments are not technically convincing (me). Although all this is less about technical solutions but design principles: what makes a good DT design. Well, Linux will survive with any solution, but what are you interested in? Users/contributors who keep quiet and accept a bad solution or those who argue for a (initially in their opinion) better one? Or stop as soon as Pavel says to do so? > You'll only attrack more "wonderful" arguments > that way. None was ?wonderful?. They were valid concerns about my proposal and I have replied to them how I see it. Generally, if you are not interested in people dedicated and committed to fight for the better solution with (technical) arguments and concrete proposals how it should be in their opinion, then please just tell and I will shut up. But only then. Or if some DT maintainer makes a decision and says: I have listened and understood all arguments pro and con and I decide this or that way (preferrably with giving reasons of decision as a guidance for similar problems in the future). Then we all can go to implementation. BR, Nikolaus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/