From mboxrd@z Thu Jan 1 00:00:00 1970 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 shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EE154C83F12 for ; Tue, 29 Aug 2023 16:59:17 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96) (envelope-from ) id 1qb23W-0002Hm-1k; Tue, 29 Aug 2023 12:59:06 -0400 Received: from mail-pf1-x433.google.com ([2607:f8b0:4864:20::433]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qb23V-0002HG-1r for kernelnewbies@kernelnewbies.org; Tue, 29 Aug 2023 12:59:05 -0400 Received: by mail-pf1-x433.google.com with SMTP id d2e1a72fcca58-68a520dba33so3693932b3a.0 for ; Tue, 29 Aug 2023 09:58:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693328330; x=1693933130; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=paxHkl9y2rDIp7HpM9Y4D/xsoPXG5cj2zJSSiRscTdc=; b=Rb/ledpjvT/roI7gNsOfurY1IGO+gjnz4BLyHxOO+Vm0T+pZHC8BwuWEuKu++GXSoF wj5t/zzx7eCYTADI9gJys7ilZCmGolbzaj1+/oNeHzZtB+OGN5ezusjAKQafZ79YVmhV liuzskdOR+tP6oohwxalPBqmrYF7zzKMZHCiszz9LQUNXmYqyKnXTHI1nU4ZvmCxcy1m KezMONtBsUyKgI8ula5efLLsfMximVSyDxwsTChjGR8T7jL5Mgr8kf/oB4XssRUPD17f 0GDGfV2EPZBJ8LjyWUrtJxHgWxWvmc2G8Fr3DknOwkNnFMzvVYjREmSjn6QOlzeZRUg/ 15Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693328330; x=1693933130; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=paxHkl9y2rDIp7HpM9Y4D/xsoPXG5cj2zJSSiRscTdc=; b=EW4Vmj0Tp7gDLV5hOOqYqGhB+jkv4FtLnP83Tcty5hYtJ+1U70blDK1w2m2tFaD6fu BNlW9ZIo3T+GrQYl6wKQPtc8kJp2pjxjjpr9fr04kckNXgUCu7UaYJQHgKqAC3sS0uXa n8mg0s+bcLJ0f5wao5Fesmo/X/f50PLc3aYZu7Zjc1/ZUJI0RAMGJtIlQ5mMiyjuy9P2 MIlAV6uOLqnOUOsGnYrrcYn9q83BI7WAJSl+RnwMyetLdceGHa2svH/SJTHxxMYElERv ZYKRJ7SdSDPn3WjE5cojt6U8H0IoHBErboz3L1LbR2ydvx+JJaezs6xPUIJj3Ls537rk PcOw== X-Gm-Message-State: AOJu0YyT3zJLAphYiXlzYrewDFKfUGMoSAc7SbS0IGkbcoBBtAP7QK6b 2EKyZswcan70f+PABRf9wPcPH5tZW/ZrmQ== X-Google-Smtp-Source: AGHT+IHjoU45NQBn1P5xyvlvzXnco5ZLypAXVEmU+4uoyGVNdRwQ6v9I87kEFvfTaADAPhcRLDiuvw== X-Received: by 2002:a05:6a00:22d4:b0:68b:ed83:9017 with SMTP id f20-20020a056a0022d400b0068bed839017mr18002996pfj.8.1693328329986; Tue, 29 Aug 2023 09:58:49 -0700 (PDT) Received: from [172.16.116.58] ([103.15.228.92]) by smtp.gmail.com with ESMTPSA id x22-20020a62fb16000000b0064fd4a6b306sm8647516pfm.76.2023.08.29.09.58.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Aug 2023 09:58:49 -0700 (PDT) Message-ID: <1e8badf8-dfea-bd37-ab1d-c8d8f9de6f9b@gmail.com> Date: Tue, 29 Aug 2023 22:28:46 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Content-Language: en-US To: kernelnewbies@kernelnewbies.org From: Ayush Singh Subject: Adding compatible string to standard UART X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: kernelnewbies-bounces@kernelnewbies.org Hello everyone. I have been working on submitting my GSoC23 driver [1] to be merged upstream. BeaglePlay has a specific UART that is connected to the CC1352 Co-processor. This UART is used to communicate with CC1352 co-processor. It is also used to flash stuff to this co-processor using bsl. Thus, it should be possible to disable it with an overlay and show it as a normal ttyS* device. Currently, the beagle kernel uses the following dts [3]. My driver uses this UART and thus I need to patch the devicetree. However, I am not too sure what I need to do to submit my device tree patch upstream. I read the Submitting Devicetree (DT) binding patches' doc [2], but I don't understand a few things: 1. Should I even be using device tree? Maybe there is a better method? 2. Is there some naming convention? I was thinking of `beagle,cc1352-uart` 3. Do I need a documentation entry at `Documentation/devicetree/bindings`? If yes, should it go under serial? 4. I think I am supposed to use YAML now and not txt? 5. What are the required fields in this doc file? Ayush Singh [1]: https://github.com/Ayush1325/linux/tree/gb-beagleplay [2]: https://docs.kernel.org/devicetree/bindings/submitting-patches.html [3]: https://git.beagleboard.org/beagleboard/linux/-/blob/v5.10.168-ti-arm64-r103/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts#L1206 _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies