All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Naidu Tellapati <naidu.tellapati@gmail.com>
Cc: linux-pwm@vger.kernel.org
Subject: Re: quick help on PDM DAC driver
Date: Tue, 23 Sep 2014 09:27:53 +0200	[thread overview]
Message-ID: <20140923072752.GK30514@ulmo> (raw)
In-Reply-To: <CAC3mp01gADb-SPJhd9dYwKg2fQgmmeGDQ+xt8qYahRovNSpXMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Mon, Sep 22, 2014 at 07:28:43PM +0530, Naidu Tellapati wrote:
> Hi Thierry,
> 
> Many thanks for your continued help in this regard.
> 
> Each bit in my 12-bit input value to the PDM block does not in anyway
> corresponds to fixed interval. My hardware PDM block works with the
> following simple logic
> 
> counter [12:0] = counter [11:0] + pluse_in [11:0]     /* pulse_in is a
> 12-bit input value to PDM block */
> pdm_out = counter [12]
> 
> The above logic runs for every pdm_clk cycle.

I don't see how this could reasonably fake a PWM. The best you can
probably get is a 0%, 50% and 100% duty-cycles.

> And hence I am of the opinion that I need to have a Linux PDM
> Framework which is similar to PWM Framework and which provides
> pulse_in as device attribute to the Linux User Space.

Given the peculiarity of the device I don't think adding a framework is
necessary. But you could perhaps add a driver to drivers/misc that
exposes the pulse_in parameter in sysfs.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-23  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 11:07 quick help on PDM DAC driver Naidu Tellapati
2014-09-22 11:27 ` Thierry Reding
2014-09-22 13:58   ` Naidu Tellapati
2014-09-23  7:27     ` Thierry Reding [this message]
2014-09-23  7:45       ` Naidu Tellapati

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=20140923072752.GK30514@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-pwm@vger.kernel.org \
    --cc=naidu.tellapati@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.