On Thu, Jun 02, 2016 at 02:47:24PM +0200, Clemens Gruber wrote:
> Instead of checking the SGTL5000 chip revision, we should only check if
> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
> if the regulator is missing.
It looks like there's multiple patches needed here from
On Thu, Jun 02, 2016 at 02:47:24PM +0200, Clemens Gruber wrote:
> Instead of checking the SGTL5000 chip revision, we should only check if
> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
> if the regulator is missing.
It looks like there's multiple patches needed here from
On Mon, Jun 6, 2016 at 1:45 PM, Clemens Gruber
wrote:
> Yes, I think so too. However I am unsure if we should also remove
> SGTL5000_CHIP_LINREG_CTRL from the defaults as in Eric's patch 3/6 or
> only keep the parts of the patch dealing with SGTL5000_CHIP_ANA_POWER.
On Mon, Jun 6, 2016 at 1:45 PM, Clemens Gruber
wrote:
> Yes, I think so too. However I am unsure if we should also remove
> SGTL5000_CHIP_LINREG_CTRL from the defaults as in Eric's patch 3/6 or
> only keep the parts of the patch dealing with SGTL5000_CHIP_ANA_POWER.
> What do you think?
I think
Hi Fabio,
On Sun, Jun 05, 2016 at 10:22:55PM -0300, Fabio Estevam wrote:
> Hi Clemens,
>
> On Sun, Jun 5, 2016 at 8:16 PM, Clemens Gruber
> wrote:
>
> > I looked into this today and discovered the following:
> >
> > With my patch applied, if I reset the board just
Hi Fabio,
On Sun, Jun 05, 2016 at 10:22:55PM -0300, Fabio Estevam wrote:
> Hi Clemens,
>
> On Sun, Jun 5, 2016 at 8:16 PM, Clemens Gruber
> wrote:
>
> > I looked into this today and discovered the following:
> >
> > With my patch applied, if I reset the board just after playback, at the
> >
Hi Clemens,
On Sun, Jun 5, 2016 at 8:16 PM, Clemens Gruber
wrote:
> I looked into this today and discovered the following:
>
> With my patch applied, if I reset the board just after playback, at the
> next boot, the sgtl5000_fill_defaults function does not succeed:
Hi Clemens,
On Sun, Jun 5, 2016 at 8:16 PM, Clemens Gruber
wrote:
> I looked into this today and discovered the following:
>
> With my patch applied, if I reset the board just after playback, at the
> next boot, the sgtl5000_fill_defaults function does not succeed: Writing
> the default value
Hi Eric, Fabio, Mark,
On Sat, Jun 04, 2016 at 07:15:25PM +0200, Clemens Gruber wrote:
> please don't merge the patch yet, I just observed a strange effect when
> resetting the board during playback / just after playback stops.
> At next boot time, sometimes the following error occurs:
>
Hi Eric, Fabio, Mark,
On Sat, Jun 04, 2016 at 07:15:25PM +0200, Clemens Gruber wrote:
> please don't merge the patch yet, I just observed a strange effect when
> resetting the board during playback / just after playback stops.
> At next boot time, sometimes the following error occurs:
>
Hi Eric,
On Sat, Jun 04, 2016 at 07:18:28AM +0200, Eric Nelson wrote:
> AFAIK, the SGTL5000 versions < 0x11 are like Sasquatch: I've seen
> no real proof of their existence. I tried to chase down when this
> code was introduced, but it seems to have been around since
> the dawn of the driver.
>
Hi Eric,
On Sat, Jun 04, 2016 at 07:18:28AM +0200, Eric Nelson wrote:
> AFAIK, the SGTL5000 versions < 0x11 are like Sasquatch: I've seen
> no real proof of their existence. I tried to chase down when this
> code was introduced, but it seems to have been around since
> the dawn of the driver.
>
Hi Fabio and Clemens,
On 06/03/2016 06:23 PM, Eric Nelson wrote:
> Hi Fabio,
>
> On 06/02/2016 05:48 PM, Fabio Estevam wrote:
>> Hi Clemens,
>>
>> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
>> wrote:
>>> Instead of checking the SGTL5000 chip revision, we should
Hi Fabio and Clemens,
On 06/03/2016 06:23 PM, Eric Nelson wrote:
> Hi Fabio,
>
> On 06/02/2016 05:48 PM, Fabio Estevam wrote:
>> Hi Clemens,
>>
>> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
>> wrote:
>>> Instead of checking the SGTL5000 chip revision, we should only check if
>>> the VDDD
Hi Fabio,
On 06/02/2016 05:48 PM, Fabio Estevam wrote:
> Hi Clemens,
>
> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
> wrote:
>> Instead of checking the SGTL5000 chip revision, we should only check if
>> the VDDD regulator exists and only call
Hi Fabio,
On 06/02/2016 05:48 PM, Fabio Estevam wrote:
> Hi Clemens,
>
> On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
> wrote:
>> Instead of checking the SGTL5000 chip revision, we should only check if
>> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
>> if the
On Thu, Jun 02, 2016 at 05:56:51PM +0100, Mark Brown wrote:
> On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
>
> > Sometime ago you were looking at this. What do you think about this patch?
>
> I'm rather concerned that the patches came from people working closely
> with
On Thu, Jun 02, 2016 at 05:56:51PM +0100, Mark Brown wrote:
> On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
>
> > Sometime ago you were looking at this. What do you think about this patch?
>
> I'm rather concerned that the patches came from people working closely
> with
On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
> Sometime ago you were looking at this. What do you think about this patch?
I'm rather concerned that the patches came from people working closely
with Freescale already - are we *sure* that Freescale/NXP's public
errata are
On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
> Sometime ago you were looking at this. What do you think about this patch?
I'm rather concerned that the patches came from people working closely
with Freescale already - are we *sure* that Freescale/NXP's public
errata are
Hi Clemens,
On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
wrote:
> Instead of checking the SGTL5000 chip revision, we should only check if
> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
> if the regulator is missing.
> Otherwise, the user
Hi Clemens,
On Thu, Jun 2, 2016 at 9:47 AM, Clemens Gruber
wrote:
> Instead of checking the SGTL5000 chip revision, we should only check if
> the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
> if the regulator is missing.
> Otherwise, the user reads in the kernel log that
Instead of checking the SGTL5000 chip revision, we should only check if
the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
if the regulator is missing.
Otherwise, the user reads in the kernel log that the internal LDO is
used, even though he did follow the NXP recommendation to
Instead of checking the SGTL5000 chip revision, we should only check if
the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
if the regulator is missing.
Otherwise, the user reads in the kernel log that the internal LDO is
used, even though he did follow the NXP recommendation to
Instead of checking the SGTL5000 chip revision, we should only check if
the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
if the regulator is missing.
Otherwise, the user reads in the kernel log that the internal LDO is
used, even though he did follow the NXP recommendation to
Instead of checking the SGTL5000 chip revision, we should only check if
the VDDD regulator exists and only call sgtl5000_replace_vddd_with_ldo
if the regulator is missing.
Otherwise, the user reads in the kernel log that the internal LDO is
used, even though he did follow the NXP recommendation to
26 matches
Mail list logo