On Monday, August 23, 2010 08:53:37 Matti J. Aaltonen wrote:
> Hi.
>
> On Fri, 2010-08-20 at 14:04 +0200, ext pramodh ag wrote:
> > Hello,
> >
> > > +static ssize_t wl1273_fm_fops_write(struct file *file, const char __user
> > *buf,
> > > + size_t count, loff_t *ppos)
> > > +{
> > > + struct wl1273_device *radio = video_get_drvdata(video_devdata(file));
> > > + u16 val;
> > > + int r;
> > > +
> > > + dev_dbg(radio->dev, "%s\n", __func__);
> > > +
> > > + if (radio->core->mode != WL1273_MODE_TX)
> > > + return count;
> > > +
> > > + if (!radio->rds_on) {
> > > + dev_warn(radio->dev, "%s: RDS not on.\n", __func__);
> > > + return 0;
> > > + }
> >
> > Aren't you planning to use extended controls "V4L2_CID_RDS_TX_RADIO_TEXT",
> > "V4L2_CID_RDS_TX_PI", etc to handle FM TX RDS data?
>
> In principle yes, but we haven't yet decided to implement those now, at
> the moment the RDS interpretation is left completely to user space
> applications.
Matti, is it even possible to use the current FM TX RDS API for this chip?
That API expects that the chip can generate the correct RDS packets based on
high-level data. If the chip can only handle 'raw' RDS packets (requiring a
userspace RDS encoder), then that API will never work.
But if this chip can indeed handle raw RDS only, then we need to add some
capability flags to signal that to userspace.
Regards,
Hans
>
> Best Regards,
> Matti
>
> >
> > Thanks and regards,
> > Pramodh
> >
> >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-media" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
