From: Marek Vasut <marek.vasut@gmail.com>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: alsa-devel@alsa-project.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Mark Brown <broonie@sirena.org.uk>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] General fix for Palm27x aSoC driver
Date: Wed, 15 Apr 2009 07:00:14 +0200 [thread overview]
Message-ID: <200904150700.14772.marek.vasut@gmail.com> (raw)
In-Reply-To: <f17812d70904141923l7f1b5697gbb27e852dfe6dba0@mail.gmail.com>
On Wednesday 15 of April 2009 04:23:49 Eric Miao wrote:
> On Wed, Apr 15, 2009 at 5:42 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > On Tuesday 14 of April 2009 21:50:36 Mark Brown wrote:
> >> On Sun, Apr 12, 2009 at 08:51:19PM +0200, Marek Vasut wrote:
> >> > +static struct pxa2xx_ac97_platform_data palmld_ac97_pdata = {
> >> > + .reset_gpio = 95,
> >> > +};
> >>
> >> The type of this will need changing to reflect the patch that got merged
> >> for this but other than that minor point this approach is fine.
> >
> > OK, shall I change it and resend (ps. to what if you dont mind telling
> > me?) ? Also, do you want to push it through also tree or ARM tree ? I'm
> > for the second option as it's more of a bugfix suitable for that tree.
>
> Sorry, late on this. The changes to the platform part look OK to me,
>
> and some minor things you may have another look:
> > -static int __init palm27x_asoc_init(void)
> > +static int palm27x_asoc_probe(struct platform_device *pdev)
>
> __devinit
Thanks, true, will revise it later today and resend ...
>
> > {
> > int ret;
> >
> > @@ -208,6 +208,10 @@ static int __init palm27x_asoc_init(void)
> > machine_is_palmld()))
> > return -ENODEV;
> >
> > + if (pdev->dev.platform_data)
> > + palm27x_ep_gpio = ((struct palm27x_asoc_info *)
> > + (pdev->dev.platform_data))->jack_gpio;
> > +
>
> This is not so readable, I'd prefer to introduce a variable for the
> 'struct palm27x_asoc_info *' pointer.
Come on, we are not doing the kernel only for ub...u so this should be OK for
everyone who can code in C. :-)
>
> > ret = gpio_request(palm27x_ep_gpio, "Headphone Jack");
> > if (ret)
> > return ret;
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-04-15 5:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 16:58 [PATCH] General fix for Palm27x aSoC driver Marek Vasut
2009-04-12 17:06 ` Mark Brown
2009-04-12 17:20 ` Marek Vasut
2009-04-12 17:24 ` Marek Vasut
2009-04-12 17:30 ` Robert Jarzmik
2009-04-12 18:00 ` Mark Brown
2009-04-12 17:58 ` Mark Brown
2009-04-12 18:51 ` Marek Vasut
2009-04-14 17:51 ` Marek Vasut
2009-04-14 19:50 ` Mark Brown
2009-04-14 21:42 ` Marek Vasut
2009-04-15 2:23 ` Eric Miao
2009-04-15 5:00 ` Marek Vasut [this message]
2009-04-15 5:11 ` Eric Miao
2009-04-15 8:21 ` Mark Brown
2009-04-16 2:43 ` Eric Miao
2009-04-16 4:45 ` Marek Vasut
2009-04-17 9:42 ` Marek Vasut
2009-04-18 17:02 ` Marek Vasut
2009-04-19 13:52 ` Eric Miao
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=200904150700.14772.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox