From: Petr Kulhavy <petr@barix.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>,
nsekhar@ti.com, khilman@kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, devicetree@vger.kernel.org
Cc: mark.rutland@arm.com, alsa-devel@alsa-project.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
robh+dt@kernel.org, galak@codeaurora.org
Subject: Re: [PATCH v2 2/6] ASoC: Davinci: McBSP: add device tree support for McBSP
Date: Mon, 18 Apr 2016 12:24:54 +0200 [thread overview]
Message-ID: <5714B5F6.9@barix.com> (raw)
In-Reply-To: <5714B469.1040408@ti.com>
On 18.04.2016 12:18, Peter Ujfalusi wrote:
> On 04/18/16 12:27, Petr Kulhavy wrote:
>
>> Or what do you think the pdata should carry?
> Good question. Since the driver itself does not care about pdata I would
> remove it. On the other hand if you implement the FIFO handling you will need
> pdata for legacy mode to select the FIFO threshold.
> Currently there is one pdata structure for legacy mode used by the McASP,
> McBSP and the Voice Codec. It contains mixed options applicable for all and
> some which applicable only for one of the drivers...
> I think if we want to make things clean and neat we would aim to have separate
> pdata for each of the drivers.
>
> I would probably drop the current pdata for McBSP and when I see what data I
> need for the driver later I would create one for the McBSP only.
>
Thanks, Peter. I agree with you.
I don't have the time to implement the FIFO now, so it makes sense to
drop the pdata for now and add a dedicated one if needed later.
Shall I remove the pdata also from the EVK legacy board drivers?
I'm going to prepare another patch set.
Cheers
Petr
next prev parent reply other threads:[~2016-04-18 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 11:45 [PATCH v2 0/6] ASoC: davinci-mcbsp: add binding for McBSP Petr Kulhavy
[not found] ` <1460375117-4311-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-11 11:45 ` [PATCH v2 1/6] " Petr Kulhavy
[not found] ` <1460375117-4311-2-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-13 14:30 ` Rob Herring
2016-04-15 8:48 ` Petr Kulhavy
2016-04-15 8:58 ` Sekhar Nori
[not found] ` <5710AACF.9070402-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-21 14:42 ` Rob Herring
2016-04-11 11:45 ` [PATCH v2 2/6] ASoC: Davinci: McBSP: add device tree support " Petr Kulhavy
2016-04-15 9:32 ` Peter Ujfalusi
[not found] ` <5710B516.2000006-l0cyMroinI0@public.gmane.org>
2016-04-18 9:27 ` [alsa-devel] " Petr Kulhavy
2016-04-18 10:18 ` Peter Ujfalusi
2016-04-18 10:24 ` Petr Kulhavy [this message]
2016-04-18 10:35 ` Peter Ujfalusi
2016-04-11 11:45 ` [PATCH v2 3/6] ARM: davinci: da850: add clocks for mcbsp0 and 1 Petr Kulhavy
2016-04-11 11:45 ` [PATCH v2 4/6] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entries for mcbsp0 and mcbsp1 Petr Kulhavy
2016-04-11 11:45 ` [PATCH v2 5/6] ARM: DTS: da850: Fix wrong number of interrupts Petr Kulhavy
2016-04-11 11:45 ` [PATCH v2 6/6] ARM: DTS: da850: Add McBSP0 and McBSP1 Petr Kulhavy
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=5714B5F6.9@barix.com \
--to=petr@barix.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).