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 105C3C433DF for ; Sun, 2 Aug 2020 11:55:43 +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 D06392075B for ; Sun, 2 Aug 2020 11:55:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="SUSOBWKR" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D06392075B 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=OM0KGlt49pdzuBeG1C+0vgEzG6BFtSfVBR5cMdTzLkA=; b=SUSOBWKR5TUtYtJGs82rye5Av IRiFGCOIv9M1bzlsQS0L++k6LdEpF+rMNzEgA7cZoFEHcjwGc0r35m9WQp1xrGZ4jLbXIBe6lt6PS WYCS88elxJ1bJri7mWMliW6rcZ8FZScuhmlcm9rnVl9z95zS7bHDWgvWvGnJQAWFPYbCVCwxsqnea BVk+eaiVhQYXQEic9yAUlxtcuVotzjgUKOKGKPvNUKdLL6/AeRBDNwIi/1JdQnwIz3uec+jx/hmrT FL3KvbJ+7xEUdm6JWe/lbYAgyBxFcvkAnhPtvbZgWCRYMTllIIrGrmMAUok+ZzxlwKiZkFKyVzwkO ZRj8I1fcA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1k2CYf-0000S9-Jd; Sun, 02 Aug 2020 11:53:41 +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 1k2CYc-0000Rj-OF for linux-arm-kernel@lists.infradead.org; Sun, 02 Aug 2020 11:53:39 +0000 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id AEA661C0BDA; Sun, 2 Aug 2020 13:53:36 +0200 (CEST) Date: Sun, 2 Aug 2020 13:53:30 +0200 From: Pavel Machek To: Grzegorz Jaszczyk Subject: Re: [PATCH 0/6] Add TI PRUSS platform driver Message-ID: <20200802115330.GA1090@bug> References: <1596020528-19510-1-git-send-email-grzegorz.jaszczyk@linaro.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1596020528-19510-1-git-send-email-grzegorz.jaszczyk@linaro.org> 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_075338_927055_BD4CFA0D X-CRM114-Status: GOOD ( 13.13 ) 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 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... 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