All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Frank Mandarino <fmandarino@endrelia.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>
Subject: Re: ALSA:AT91SAM9G20: Add support(DAI) for wolfson8731
Date: Wed, 17 Sep 2008 17:23:20 +0200	[thread overview]
Message-ID: <48D120E8.4060504@atmel.com> (raw)
In-Reply-To: <48D11D0E.90701@endrelia.com>

Hi Frank,
Frank Mandarino a écrit :
> Mark Brown wrote:
> 
>> The only major issue I see with the patch is a documentation one: it's
>> not clear to me reading the code how the atmel_ssc DAI driver relates to
>> the existing at91_ssc driver.  It may be that this is something that's
>> obvious to someone familiar with the at91 hardware but just looking at
>> the code it's not clear to me what the difference is between the two and
>> when each should be used.  
>>
>> Looking at the code they appear to be similar to the point where they
>> should be the same driver but it's entirely possible that I'm missing
>> something here.  I've CCed in Frank Mandarino who did the existing AT91
>> support.  If they should be separate drivers then some comments should
>> be added in the driver and the Kconfig help text explaning the
>> situation.
> 
> I agree that the drivers should be combined.  Unfortunately, at this
> time I am unable to contribute to this effort.
> 
I agree with you as well. I wanted to use the drivers/misc/atmel-ssc in 
the dai because it is a common arch between atmel ARM and AVR core.
I will have a look at the at91-ssc code and at the eti_b1_wm8731.c file 
to see what changes should be done.
> 
>>> +		start_event = channels == 1
>>> +				? 4
>>> +				: 7;
>> This would be much clearer if it were expanded into multiple statements.
> 
> This was a little clearer in at91-ssc.c:
> 
>                 start_event = channels == 1
>                                 ? AT91_SSC_START_FALLING_RF
>                                 : AT91_SSC_START_EDGE_RF;
> 
> Perhaps these constant definitions are no longer available it the latest
> kernel.  Are there updated definitions to use instead of magic numbers?

My mistake, I will use your constant def.
> 
>>> +#ifdef CONFIG_PM
>>> +#define atmel_ssc_suspend	NULL
>>> +#define atmel_ssc_resume	NULL
>>> +#else
>>> +#define atmel_ssc_suspend	NULL
>>> +#define atmel_ssc_resume	NULL
>>> +#endif
>> These may as well be removed - if someone implements suspend/resume
>> support they can add them then then.
> 
> Is there a reason that suspend/resume was removed?  It is really
> important for embedded systems.
I removed resume/suspend because I didn't have the time to write it...
I wanted to add it in a next patch, but maybe I shoul do it now.

Mark, concerning your other comments I am working on it.
I will send another patch as soon as it is finished.

Regards,
Sedji

  parent reply	other threads:[~2008-09-17 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17  9:51 ALSA:AT91SAM9G20: Add support(DAI) for wolfson8731 Sedji Gaouaou
2008-09-17 11:05 ` Mark Brown
2008-09-17 15:06   ` Frank Mandarino
2008-09-17 15:21     ` Mark Brown
2008-09-17 15:23     ` Sedji Gaouaou [this message]
2008-09-17 15:30       ` Mark Brown
2008-09-17 16:30         ` Sedji Gaouaou
2008-09-17 16:35           ` Mark Brown
     [not found]             ` <BAY110-W332FD6EFAA8BBE246EDD7DC94F0@phx.gbl>
2008-09-18  9:21               ` Does LKML accept non-ASOC audio driver? Mark Brown
     [not found]                 ` <BAY110-W448DBD74086F0CC723FA67C94F0@phx.gbl>
2008-09-18 10:17                   ` Mark Brown
     [not found]                     ` <BAY110-W35E0C694DFC04076A4E353C94F0@phx.gbl>
2008-09-18 11:33                       ` Mark Brown

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=48D120E8.4060504@atmel.com \
    --to=sedji.gaouaou@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=fmandarino@endrelia.com \
    /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.