From owner-freebsd-embedded@FreeBSD.ORG Tue Oct 8 22:37:38 2013 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 81AB43AF; Tue, 8 Oct 2013 22:37:38 +0000 (UTC) (envelope-from ilya@bakulin.de) Received: from olymp.kibab.com (olymp6.kibab.com [IPv6:2a01:4f8:160:84c1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4090D27A2; Tue, 8 Oct 2013 22:37:37 +0000 (UTC) X-DKIM: OpenDKIM Filter v2.5.2 olymp.kibab.com DD94C3F458 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bakulin.de; s=default; t=1381271853; bh=NC1JHDM2thtfcYgbo+GcEbi7/WUatYgJJpL7oSm25+w=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=jYtSFSS2DFYNLM7QTLwtoQ56DFcEs32i2/tk3LgQ1v4MT5lK/L9k4A+WHhl1VF6LD 3XMLsOofRfr2x5vMR54lXZXYuY+7EaS3BNALeb+ABD898fGjw1kUos3JMjje7DMiFG VIcX4/q8mviJzUHD1HTnzCYFMGQy1uPZPp5ogYqE= Message-ID: <5254892B.3050507@bakulin.de> Date: Wed, 09 Oct 2013 00:37:31 +0200 From: Ilya Bakulin MIME-Version: 1.0 To: Warner Losh Subject: Re: SDIO for FreeBSD References: <5251A9D3.1080803@bakulin.de> <5251C911.6020003@FreeBSD.org> <4FB11076-DD88-43F2-A449-E41D2088A4DD@bsdimp.com> In-Reply-To: <4FB11076-DD88-43F2-A449-E41D2088A4DD@bsdimp.com> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , Alexander Motin , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:37:38 -0000 On 07.10.13 01:19, Warner Losh wrote: > I've often thought that having an SDIO protocol for CAM would be where we'd wind up because once you start adding in GPIO pin interrupt signalling, message "interrupt" signaling, message completion, etc, it looks a lot like many of the mechanisms we have in CAM... I'm not at all sure that USB is the right model to use, frankly... But it does have some superficial similarities... > > Warner The idea seems to be interesting -- at least we can reuse the CAM queues and interrupt handling algorithms... One thing that I'd like to ask after initial reading about CAM in FreeBSD: is it possible for SIM devices to initiate data transfer? the CAM subsystem is primarily used for storage devices, where the host issues a SCSI command, schedules it to the SIM, and then SIM receives an interrupt from the h/w and updates the existing CCB, signaling command completion. In SDIO case we can have the interrupts from the card that are not associated with any previous command. Is it possible to handle such situation using CAM framework? -- Regards, Ilya Bakulin