Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753010AbbKZJFo (ORCPT ); Thu, 26 Nov 2015 04:05:44 -0500 Received: from mail-io0-f181.google.com ([209.85.223.181]:36290 "EHLO mail-io0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752193AbbKZJFd (ORCPT ); Thu, 26 Nov 2015 04:05:33 -0500 MIME-Version: 1.0 X-Originating-IP: [62.219.232.49] In-Reply-To: <1440810499-24327-1-git-send-email-stefan@agner.ch> References: <1440810499-24327-1-git-send-email-stefan@agner.ch> From: Ohad Ben-Cohen Date: Thu, 26 Nov 2015 11:05:13 +0200 Message-ID: Subject: Re: [PATCH] remoteproc: report error if resource table doesn't exist To: Stefan Agner Cc: linux-arm , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1081 Lines: 30 Hi Stefan, On Sat, Aug 29, 2015 at 4:08 AM, Stefan Agner wrote: > Currently, if the resource table is completely missing in the > firmware, powering up the remoteproc fails silently. Add a message > indicating that the resource table is missing in the firmware. > > Signed-off-by: Stefan Agner Applied to remoteproc-next, thanks. > This also opens up a more general question: Is it mandatory to have > a resource table in the firmware? The implementation we have today does require it, but that's just because this is what we had to support so far. > Theoretically a remoteproc could > also work completely independent, all what would be used from the > remoteproc framework is the loading and starting capabilities... Sure. Feel free to add support for your hardware as needed. Thanks, Ohad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/