Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0EE7AC433EF for ; Tue, 4 Jan 2022 14:13:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234050AbiADONm (ORCPT ); Tue, 4 Jan 2022 09:13:42 -0500 Received: from ivanoab7.miniserver.com ([37.128.132.42]:36342 "EHLO www.kot-begemot.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232716AbiADONj (ORCPT ); Tue, 4 Jan 2022 09:13:39 -0500 Received: from [192.168.18.6] (helo=jain.kot-begemot.co.uk) by www.kot-begemot.co.uk with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n4kZ7-0008zn-RG; Tue, 04 Jan 2022 14:13:34 +0000 Received: from jain.kot-begemot.co.uk ([192.168.3.3]) by jain.kot-begemot.co.uk with esmtp (Exim 4.94.2) (envelope-from ) id 1n4kZ3-001PmU-PR; Tue, 04 Jan 2022 14:13:27 +0000 Subject: Re: [PATCH] um: virtio_uml: allow probing from devicetree To: Vincent Whitchurch , Johannes Berg Cc: Jeff Dike , Richard Weinberger , Rob Herring , kernel , "devicetree@vger.kernel.org" , "linux-um@lists.infradead.org" , "linux-kernel@vger.kernel.org" References: <20211221090447.1567-1-vincent.whitchurch@axis.com> <5f104044649ec60ba93648e68c3df2183e032072.camel@sipsolutions.net> <20211222103417.GB25135@axis.com> From: Anton Ivanov Message-ID: Date: Tue, 4 Jan 2022 14:13:25 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: <20211222103417.GB25135@axis.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Clacks-Overhead: GNU Terry Pratchett Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22/12/2021 10:34, Vincent Whitchurch wrote: > On Tue, Dec 21, 2021 at 09:48:26PM +0100, Johannes Berg wrote: >> On Tue, 2021-12-21 at 10:04 +0100, Vincent Whitchurch wrote: >>> Allow the virtio_uml device to be probed from the devicetree so that >>> sub-devices can be specified using the standard virtio bindings, for >>> example: >>> >>> virtio@1 { >>> compatible = "virtio,uml"; >>> socket-path = "i2c.sock"; >>> virtio-device-id = <0x22>; >>> >> >> Given this, maybe it should modify >> Documentation/devicetree/bindings/virtio/virtio-device.yaml? Or actually >> add a new Documentation/devicetree/bindings/virtio/uml.yaml I guess? >> >> +Rob, because I'm not really into any of this. >> >> Also, I'm not even sure we should/need to document the DT bits that are >> basically only used for testing in the first place? If we start adding the UML devices themselves to the DT, we might as well add all of them. In the doc patch have described the DT support as mostly for development at this point. It can be a good alternative to the endless command line (especially for complex devices like f.e. l2tpv3). > > I wasn't sure either, but Rob was OK with not documenting some other > bindings which are only used for testing[0], so I assumed that that > applied here too: > > [0] https://lore.kernel.org/all/5baa1ae6.1c69fb81.847f2.3ab1@mx.google.com/ > > Also, DT bindings are supposed to be generic and based on what the > hardware has, but here we have no hardware and something very Linux and > UML-specific. > >> Code looks good to me. > > Thanks! > Brgds, -- Anton R. Ivanov Cambridgegreys Limited. Registered in England. Company Number 10273661 https://www.cambridgegreys.com/