On Fri, 8 Mar 2019 21:19:29 -0300
Renato Lui Geh wrote:
> On 03/04, Ardelean, Alexandru wrote:
> >On Sun, 2019-03-03 at 14:53 +, Jonathan Cameron wrote:
> >> [External]
> >>
> >>
> >> On Sun, 3 Mar 2019 11:01:09 -0300
> >> Renato Lui Geh wrote:
> >>
> >> > On 03/01, Ardelean, Alexandru w
On 03/04, Ardelean, Alexandru wrote:
On Sun, 2019-03-03 at 14:53 +, Jonathan Cameron wrote:
[External]
On Sun, 3 Mar 2019 11:01:09 -0300
Renato Lui Geh wrote:
> On 03/01, Ardelean, Alexandru wrote:
> > On Thu, 2019-02-28 at 11:24 -0300, Renato Lui Geh wrote:
> > >
> > >
> > > The ad7780
On Sun, 2019-03-03 at 14:53 +, Jonathan Cameron wrote:
> [External]
>
>
> On Sun, 3 Mar 2019 11:01:09 -0300
> Renato Lui Geh wrote:
>
> > On 03/01, Ardelean, Alexandru wrote:
> > > On Thu, 2019-02-28 at 11:24 -0300, Renato Lui Geh wrote:
> > > >
> > > >
> > > > The ad7780 supports both th
On Sun, 3 Mar 2019 11:01:09 -0300
Renato Lui Geh wrote:
> On 03/01, Ardelean, Alexandru wrote:
> >On Thu, 2019-02-28 at 11:24 -0300, Renato Lui Geh wrote:
> >>
> >>
> >> The ad7780 supports both the ad778x and ad717x families. Each chip has
> >> a corresponding ID. This patch provides a mask fo
On 03/01, Ardelean, Alexandru wrote:
On Thu, 2019-02-28 at 11:24 -0300, Renato Lui Geh wrote:
The ad7780 supports both the ad778x and ad717x families. Each chip has
a corresponding ID. This patch provides a mask for extracting ID values
from the status bits and also macros for the correct valu
On Thu, 2019-02-28 at 11:24 -0300, Renato Lui Geh wrote:
>
>
> The ad7780 supports both the ad778x and ad717x families. Each chip has
> a corresponding ID. This patch provides a mask for extracting ID values
> from the status bits and also macros for the correct values for the
> ad7170, ad7171, a