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 X-Spam-Level: X-Spam-Status: No, score=-0.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 83694C47254 for ; Tue, 5 May 2020 14:40:08 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 43590206A5 for ; Tue, 5 May 2020 14:40:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="guuDitOb" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 43590206A5 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1jVyj3-0000qh-JX; Tue, 05 May 2020 10:39:13 -0400 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1jVyj0-0000qY-SD for kernelnewbies@kernelnewbies.org; Tue, 05 May 2020 10:39:11 -0400 Received: by mail-wm1-x342.google.com with SMTP id x4so2584016wmj.1 for ; Tue, 05 May 2020 07:39:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=UMD0nPkXr8us13eQBlROKA3dkuxgmZXpWLQwX72L2lw=; b=guuDitObC451yV4Kro4fo926AQSZYAzbNkC1W8ESXPgxu8rndKwrOGLWNF3IyvIN70 cCfRHR+O91maB28DOh5xA+Vhd60SB0WEQ75rkvCy3NlrqEx1LRY1qQVhcd5lRWlpm0yn Glo3HXNHUVZdFLT1sSBgjhYKHoJ9VO1i9/8P9+vyFK50myMRkDJmZ9i0cNjvaJEVArqF XQKgVaq/ompb8LCoYE0jcT9l6GsSI8+UGUXfnH1xwhdjxMuEEjgPJwxQ6LM9hYAq3scz X8pIzozPUaGJW1kqnQD/3zIH9xvXN9Mzv12ECfyaiqF9xzwpwBgUrYxmhnL1IM0ksSms iwUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=UMD0nPkXr8us13eQBlROKA3dkuxgmZXpWLQwX72L2lw=; b=IfWFiity2mZ/DvIo4yuuTZGMoQfE1IlOxELI+or03KEkncYctYqo3rqhUVvJ3WVIIE uqZ09SEYfK2FSGXurznfEimXplFi73e2N6Cl5rFu5iAaG0+iikUmMfYeINtF+FXSgpoJ qTRzyx+k6V7F9r5NP22LRf7T0GhiPpNp8YLBYZPHbDLLRPzUFMvyLnuq8sACRXpUS5TM mp44PyGIYjq5cqVM+EhWs/7pVdCtB7VEjzL21W36NSv3vgFS7DxFCA6Eaca9bUplXeZq JCcg+1tqYsOB8QJaEsfs23kzznni60AFvfNubEyyMJKx7K68a2lfsSu2DX0Cx+G+n1Tc 0FaA== X-Gm-Message-State: AGi0PuacsHYX21NsgHo9uetUn3xQdABj5ifLuoIt7ATJXDhX5la+T4oq NU3v3Zv15XfIpfH29G6Slsq9dfjT X-Google-Smtp-Source: APiQypIpf7sW7nXDu6CPrhk1IMVrKzIoqMbXRn1toW+G2VV6Yb6dyLrKMkIR41D26xRpQToOpQPQLQ== X-Received: by 2002:a1c:750a:: with SMTP id o10mr3607667wmc.161.1588689488560; Tue, 05 May 2020 07:38:08 -0700 (PDT) Received: from vasteMachine (s559503e2.adsl.online.nl. [85.149.3.226]) by smtp.gmail.com with ESMTPSA id l5sm3884782wmi.22.2020.05.05.07.38.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 May 2020 07:38:07 -0700 (PDT) Date: Tue, 5 May 2020 16:38:06 +0200 From: Jacko Dirks To: Greg KH Subject: Re: Location of files for a new driver Message-ID: <20200505143806.GA589943@vasteMachine> References: <20200505135828.GA466217@vasteMachine> <20200505142032.GA793696@kroah.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200505142032.GA793696@kroah.com> Cc: kernelnewbies@kernelnewbies.org 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Tue, May 05, 2020 at 04:20:32PM +0200, Greg KH wrote: > drivers/staging/ is only for code that needs lots and lots of work to > get into the "real" part of the kernel. It also requires a TODO file > that lists what is left to do to get it out of that location. Oh, I did not know that staging was optional. Well, I will attempt to skip staging in that case > It all depends on what you are writing. What exactly does this code do? > That will determine where it goes in the kernel tree. The code is a driver for the Broadcom BSC, which lives on the Raspberry Pi 3 & 4 (at least, maybe also on 1 & 2). This device can act as an I2C slave. To "announce" the device (tell the device tree which pins need to be configured how, etcetera) I need to change existing dts/dtsi files, to actually be able to enable the device I need to create a new overlay. Finally, the actual driver needs to be created in drivers/i2c/busses. And then there is also some makefile, documentation and kconfig. Does that sound right? > thanks, No, thank you! Jacko Dirks _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies