From: garlic.tseng@mediatek.com (Garlic Tseng)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 1/7] ASoC: mediatek: Refine mt8173 driver and change config option
Date: Thu, 5 May 2016 10:45:42 +0800 [thread overview]
Message-ID: <1462416342.25179.36.camel@mtksdaap41> (raw)
In-Reply-To: <20160504164306.GA6292@sirena.org.uk>
On Wed, 2016-05-04 at 17:43 +0100, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 09:00:42PM +0800, Garlic Tseng wrote:
>
> > .../{mtk-afe-pcm.c => mt8173/mt8173-afe-pcm.c} | 488 ++++++++++-----------
>
> So there's going to be no code sharing at all between this and any other
> Mediatek chips? That seems very surprising, it'd suggest that the
> hardware designers were creating a new design completely from scratch
> each time which doesn't seem all that likely. This is an unusual way of
> organizing things and we need a much clearer explanation of what's going
> on here.
MT8173 and MT2701 are from different product lines so the register
control sequences are very different. If another driver for 8173-like
(or 2701-like) chip go upstream it shall share some common code with the
relatively driver indeed. However I think MT8173 and MT2701 can't share
the platform driver or a lot of "if MT8173 else MT2701" will mess up the
code.
However, several (maybe 2 or 3) tiny functions for the two driver code
are very similar indeed. For example, pointer callback functions of
platform driver are very similar. It reads the cursor and return. But
I'm not sure if it is better to share the function. It is too trivial
for me.
next prev parent reply other threads:[~2016-05-05 2:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 13:00 [alsa-devel] [PATCH 0/7] ASoC: Mediatek: Add support for MT2701 SOC Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 1/7] ASoC: mediatek: Refine mt8173 driver and change config option Garlic Tseng
2016-05-04 16:43 ` Mark Brown
2016-05-05 2:45 ` Garlic Tseng [this message]
2016-05-05 8:32 ` Matthias Brugger
2016-05-05 10:39 ` Garlic Tseng
2016-05-06 12:20 ` Mark Brown
2016-05-06 18:33 ` Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 2/7] ASoC: mediatek: add documents for mt2701 Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 3/7] ASoC: mediatek: add clock and irq control for 2701 platform driver Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 4/7] ASoC: mediatek: add mt2701 platform driver implementation Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 5/7] ASoC: bt-sco: extend rate and add a general compatible string Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 6/7] ASoC: mediatek: add BT implementation Garlic Tseng
2016-04-29 13:00 ` [alsa-devel] [PATCH 7/7] ASoC: mediatek: Add mt2701-cs42448 driver and config option Garlic Tseng
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=1462416342.25179.36.camel@mtksdaap41 \
--to=garlic.tseng@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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