Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754857Ab1EJJxJ (ORCPT ); Tue, 10 May 2011 05:53:09 -0400 Received: from mail-pv0-f174.google.com ([74.125.83.174]:57726 "EHLO mail-pv0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754145Ab1EJJxH (ORCPT ); Tue, 10 May 2011 05:53:07 -0400 Message-ID: From: "Subhasish Ghosh" To: "Arnd Bergmann" Cc: "Nori, Sekhar" , , , , "Samuel Ortiz" , "open list" , "Watkins, Melissa" References: <1303474109-6212-1-git-send-email-subhasish@mistralsolutions.com> <613E2AF627DE4ABE92AD42D5D9E1BFE5@subhasishg> <201105051612.18522.arnd@arndb.de> In-Reply-To: <201105051612.18522.arnd@arndb.de> Subject: Re: [PATCH v4 01/11] mfd: add pruss mfd driver. Date: Tue, 10 May 2011 15:23:18 +0530 Organization: Mistral Solutions MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1766 Lines: 44 > Instead of passing a configuration file into the MFD driver and > calling it a firmware, I can see three other options that I believe > would be nicer: > > 1. have a single firmware blob that describes the child devices > and the code that is to be loaded into both units. If they are > acting as one device, either make sure you only create one > child node, or create one with a name that no driver binds to. > > 2. Call request_firmware separately for the two child devices, > and configure them separately based on the information in the > firmware files. In the case where they should act as a single > device, call the children e.g. "pruss-uart-a" and "pruss-uart-b", > then bind to both names in the pruss-uart drivers and only > start using the device when you have both nodes for the same > parent. > > 3. Do the configuration through sysfs files in the MFD device node, > which then cause the creation of the child devices. This means you > need extra user space scripts to write the addititonal files, but > is also the most flexible way. > Are you suggesting something like: /sys..../pruss/pru0/id /sys..../pruss/pru0/fw_name /sys..../pruss/pru0/load /sys..../pruss/pru1/id /sys..../pruss/pru1/fw_name /sys..../pruss/pru1/load I can program these configs and store them in the pru private. Then write something into load. This can load the PRU based upon the configs. But, I am not sure how to do this effectively using sysfs, I mean I don't want to end up writing six write and six read handlers. -- 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/