public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Sebastien Jan <s-jan@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC PATCH 0/9] MIPI HSI device support for OMAP platforms
Date: Fri, 30 Oct 2009 14:57:50 +0200	[thread overview]
Message-ID: <20091030125750.GL31472@nokia.com> (raw)
In-Reply-To: <1256896808-20152-1-git-send-email-s-jan@ti.com>

On Fri, Oct 30, 2009 at 10:59:59AM +0100, ext Sebastien Jan wrote:
> This is an RFC for a series of patch to add the support of MIPI HSI and SSI
> devices to OMAP platforms.
> The patch includes the HSI device driver and the device files for MIPI HSI and
> SSI.
> 
> The driver is made of 2 distinct modules:
>  - omap_hsi: is the Low-Level Driver (or hardware driver). It provides a
>    kernel functional interface, to be used by other kernel modules and
>    abstracts the HW.
>    This part of the patch is based on Nokia SSI driver, already submitted as
>    RFC by Carlos Chinea [1].
>  - hsi-char: is a char device driver proposing a user-space interface for
>    using the HSI and relies on omap_hsi.
>    This part of the patch is based on a development from Andras Domokos.
> The intent is to propose a single HSI driver that can support MIPI HSI 1.1 as
> well as previous implementations (SSI) for OMAP platforms (OMAP3 / OMAP4).
> 
> The driver core functionalities are there and ready for review. The following
> updates will come in the following weeks / months:
>  - Clocks and Power Management support for OMAP4 platform (HSI device file)
>  - HSI-char interface documentation
> 
> Validation: The driver is validated on 3430 SDP (with a HW loopback on the SSI
> device), and is being validated on 4430 Virtio platform (MIPI HSI device).
> 
> [1] http://lwn.net/Articles/301918/

pass all your drivers on checkpatch.pl --strict and to sparse as well.

-- 
balbi

  parent reply	other threads:[~2009-10-30 12:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30  9:59 [RFC PATCH 0/9] MIPI HSI device support for OMAP platforms Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 1/9] HSI: Low Level Driver interface Sebastien Jan
2009-10-30 12:49   ` Felipe Balbi
2009-10-30 10:00 ` [RFC PATCH 2/9] HSI: Low Level Driver core Sebastien Jan
2009-10-30 12:56   ` Felipe Balbi
2009-10-30 10:00 ` [RFC PATCH 3/9] HSI: Low Level Driver device management Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 4/9] HSI: Low Level Driver debugfs support Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 5/9] HSI: Low Level Driver documentation Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 6/9] HSI: character driver interface Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 7/9] HSI: character driver low level interface Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 8/9] HSI: HSI device support Sebastien Jan
2009-10-30 10:00 ` [RFC PATCH 9/9] HSI: SSI device support and integration on 3430SDP platform Sebastien Jan
2009-10-30 12:57 ` Felipe Balbi [this message]
2009-10-30 14:32   ` [RFC PATCH 0/9] MIPI HSI device support for OMAP platforms Sebastien Jan
2009-10-30 17:58     ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091030125750.GL31472@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=s-jan@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox