All of lore.kernel.org
 help / color / mirror / Atom feed
From: halli manjunatha <manjunatha_halli@ti.com>
To: balbi@ti.com
Cc: mchehab@infradead.org, hverkuil@xs4all.nl,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources
Date: Tue, 11 Jan 2011 17:46:10 +0530	[thread overview]
Message-ID: <AANLkTimbqsDJ1KNSwzJ_RTQ3ON=-XUj0CZpZHAkeH9dP@mail.gmail.com> (raw)
In-Reply-To: <20110111112434.GE2385@legolas.emea.dhcp.ti.com>

an 11, 2011 at 4:54 PM, Felipe Balbi <balbi@ti.com> wrote:
> Hi,
>
> On Tue, Jan 11, 2011 at 06:31:23AM -0500, manjunatha_halli@ti.com wrote:
>> From: Manjunatha Halli <manjunatha_halli@ti.com>
>>
>> These are the sources for the common interfaces required by the
>> FM V4L2 driver for TI WL127x and WL128x chips.
>>
>> These implement the FM channel-8 protocol communication with the
>> chip. This makes use of the Shared Transport as its transport.
>>
>> Signed-off-by: Manjunatha Halli <manjunatha_halli@ti.com>
>> Reviewed-by: Hans Verkuil <hverkuil@xs4all.nl>
>
> looks like this is implementing a "proprietary" (by that I mean: for
> this driver only) IRQ API. Why aren't you using GENIRQ with threaded
> IRQs support ?
>
> Core IRQ Subsystem would handle a lot of stuff for you.

There is no concept of Interrupts/IRQ as such here, Hence no question of using
GENIRQ.

The FM device WL128x is interfaced via the UART,
(Internally inside the WL128x chip the BT-core on the chip
communicates with FM chip via i2C, and would have dedicated interrupt
lines may be...)

So, Whenever we refer to interrupt or IRQ or handlers in the driver,
It pretty much means a receive callback for the UART frame which
constitutes the FM interrupt event.
i.e FM interrupt would have occurred, If I receive a frame over UART
which starts with 0x08 as 1st byte and has 0xFF as its 3rd byte.

I hope this clarifies the non-usage of GENIRQ with threaded support.

> --
> balbi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Regards
Halli

  reply	other threads:[~2011-01-11 12:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 11:31 [RFC V10 0/7] FM V4L2 drivers for WL128x manjunatha_halli
2011-01-11 11:31 ` [RFC V10 1/7] drivers:media:radio: wl128x: FM Driver common header file manjunatha_halli
2011-01-11 11:17   ` Felipe Balbi
2011-01-11 11:31   ` [RFC V10 2/7] drivers:media:radio: wl128x: FM Driver V4L2 sources manjunatha_halli
2011-01-11 11:21     ` Felipe Balbi
2011-01-11 11:31     ` [RFC V10 3/7] drivers:media:radio: wl128x: FM Driver Common sources manjunatha_halli
2011-01-11 11:24       ` Felipe Balbi
2011-01-11 12:16         ` halli manjunatha [this message]
2011-01-11 12:42         ` Raja Mani
2011-01-17 10:15           ` halli manjunatha
2011-01-17 10:33             ` Hans Verkuil
2011-01-17 10:33               ` Hans Verkuil
2011-01-18 13:19               ` halli manjunatha
2011-01-19 19:12                 ` Mauro Carvalho Chehab
2011-01-20  9:39                   ` halli manjunatha
2011-01-11 11:31       ` [RFC V10 4/7] drivers:media:radio: wl128x: FM driver RX sources manjunatha_halli
2011-01-11 11:31         ` [RFC V10 5/7] drivers:media:radio: wl128x: FM driver TX sources manjunatha_halli
2011-01-11 11:31           ` [RFC V10 6/7] drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driver manjunatha_halli
2011-01-11 11:30             ` Felipe Balbi
2011-01-11 11:31             ` [RFC V10 7/7] drivers:media:radio: Update Kconfig and Makefile for wl128x FM driver manjunatha_halli
2011-03-18 16:18       ` [PATCH -next] drivers:media:radio: wl128x: fix printk format and text Randy Dunlap
2011-03-22 18:23         ` Mauro Carvalho Chehab

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='AANLkTimbqsDJ1KNSwzJ_RTQ3ON=-XUj0CZpZHAkeH9dP@mail.gmail.com' \
    --to=manjunatha_halli@ti.com \
    --cc=balbi@ti.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    /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.