Re: Work on iio: stating: frequency: ad9832

2019-04-02 Thread Marcelo Schmitt
On 04/02, Alexandru Ardelean wrote: > On Mon, Apr 1, 2019 at 7:13 PM Jonathan Cameron > wrote: > > > > On Mon, 1 Apr 2019 11:25:29 -0300 > > Marcelo Schmitt wrote: > > > > > Hello, > > > > > > I was looking for some work on staging: iio: ad9832 and made some > > > observations while reading the

Re: Work on iio: stating: frequency: ad9832

2019-04-02 Thread Alexandru Ardelean
On Mon, Apr 1, 2019 at 7:13 PM Jonathan Cameron wrote: > > On Mon, 1 Apr 2019 11:25:29 -0300 > Marcelo Schmitt wrote: > > > Hello, > > > > I was looking for some work on staging: iio: ad9832 and made some > > observations while reading the driver. > > > > Apparently it had no devicetree

Re: Work on iio: stating: frequency: ad9832

2019-04-01 Thread Jonathan Cameron
On Mon, 1 Apr 2019 11:25:29 -0300 Marcelo Schmitt wrote: > Hello, > > I was looking for some work on staging: iio: ad9832 and made some > observations while reading the driver. > > Apparently it had no devicetree documentation so I tried to elaborate > one. > It uses a platform_data variable

Work on iio: stating: frequency: ad9832

2019-04-01 Thread Marcelo Schmitt
Hello, I was looking for some work on staging: iio: ad9832 and made some observations while reading the driver. Apparently it had no devicetree documentation so I tried to elaborate one. It uses a platform_data variable to load external clock frequency (I tried to make it use linux's clock