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=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 F2DBEC433DF for ; Sun, 2 Aug 2020 11:58:30 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 C09B42075B for ; Sun, 2 Aug 2020 11:58:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="gSHY3/jg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C09B42075B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=9I8F2BFdopl82b9CLBKZZBkKhBv++WeAt1NY1ZwdBVU=; b=gSHY3/jgDGKUs3ioRtZleYxOH cQjAbO1pnGYU4rxa6qR8v7nUR0ecNGTmzqmSe6y1MVa2/KaevvXsSgh6GB5MKSTSvhSliKITA+030 oLMKseJzq9QwKjG7xHpPr/gFOn6ZepuwCSijMi74l4vUtVupBt3bsCOQY+JMmyXm38cY1OKCSKYX3 1RhTh90b6lSAzKSrl3Y0+esGmr6n/M2LMah4iWMzs+tq314dZODwo3KXSi6IAInq74bowW8dKkAax P8odQN7uhqFk5i0vfQYPMBs39rPWm0a+IebiKJqC+1IrJO9vPwiEkOGzOWkSTUfG68S+mOL013JrV oQn/mO89g==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2Cc4-0000it-4m; Sun, 02 Aug 2020 11:57:12 +0000 Received: from jabberwock.ucw.cz ([46.255.230.98]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2Cc1-0000iJ-5z for linux-arm-kernel@lists.infradead.org; Sun, 02 Aug 2020 11:57:09 +0000 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 40AAC1C0BE1; Sun, 2 Aug 2020 13:57:08 +0200 (CEST) Date: Sun, 2 Aug 2020 13:57:01 +0200 From: Pavel Machek To: Grzegorz Jaszczyk Subject: Re: [PATCH 0/6] Add TI PRUSS platform driver Message-ID: <20200802115701.GD1162@bug> References: <1596020528-19510-1-git-send-email-grzegorz.jaszczyk@linaro.org> <20200802115330.GA1090@bug> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200802115330.GA1090@bug> User-Agent: Mutt/1.5.23 (2014-03-12) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200802_075709_356005_07C78330 X-CRM114-Status: GOOD ( 15.79 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org, praneeth@ti.com, santosh.shilimkar@oracle.com, linux-kernel@vger.kernel.org, robh+dt@kernel.org, ssantosh@kernel.org, lee.jones@linaro.org, wmills@ti.com, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sun 2020-08-02 13:53:30, Pavel Machek wrote: > Hi! > > > A typical usage scenario would be to load the application firmware into one or > > more of the PRU cores, initialize one or more of the peripherals and perform I/O > > through shared RAM from either a kernel driver or directly from userspace. > > > > This series contains the PRUSS platform driver. This is the parent driver for > > the entire PRUSS and is used for managing the subsystem level resources like > > various memories and the CFG module. It is responsible for the creation and > > deletion of the platform devices for the child PRU devices and other child > > devices (like Interrupt Controller, MDIO node and some syscon nodes) so that > > they can be managed by specific platform drivers. > > > drivers/soc/ti/Kconfig | 11 + drivers/soc/ti/Makefile | 1 + drivers/soc/ti/pruss.c | > > Is drivers/soc right place for that? We already have subsystem for various > programmable accelerators... ....see drivers/remoteproc. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel