[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTiny00_uryo3UeHQX-vk2CdN9GV45QmoeFKcRotc@mail.gmail.com>
Date: Wed, 23 Mar 2011 15:53:22 +0100
From: Vitaly Wool <vitalywool@...il.com>
To: Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@...ricsson.com>
Cc: Greg Kroah-Hartman <gregkh@...e.de>, devel@...verdev.osuosl.org,
Linus Walleij <linus.walleij@...aro.org>,
linux-kernel@...r.kernel.org, linux-bluetooth@...r.kernel.org,
Pavan Savoy <pavan_savoy@...y.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Marcel Holtmann <marcel@...tmann.org>,
Lukasz Rymanowski <Lukasz.Rymanowski@...to.com>,
Linus Walleij <linus.walleij@...ricsson.com>,
Par-Gunnar Hjalmdahl <pghatwork@...il.com>,
Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH 1/2] staging: Add ST-Ericsson CG2900 driver
On Wed, Mar 23, 2011 at 2:59 PM, Par-Gunnar Hjalmdahl
<par-gunnar.p.hjalmdahl@...ricsson.com> wrote:
> diff --git a/drivers/staging/cg2900/TODO b/drivers/staging/cg2900/TODO
> new file mode 100644
> index 0000000..f6fb76a
> --- /dev/null
> +++ b/drivers/staging/cg2900/TODO
> @@ -0,0 +1,21 @@
> +TODO
> +----
> +
> + - Decide upon architecture. Some people consider architecture in the cg2900
> + driver to be too complex. We consider it to be not more complex than needed.
> +
> + - Currently the cg2900_uart registers as protocol driver against hci_ldisc.c.
> + There is however some common functionality with hci_h4.c and the cg2900 could
> + therefore register it's vendor specific channels to hci_h4.c, but this would
> + require adding a registration functionality in the hci_h4 file.
> +
> + - Some people demand that the cg2900 driver re-use the Bluetooth driver to send
> + and receive BT commands and events. That is however not possible with current
> + BT API and might not be feasible, for example when using FM only in
> + the cg2900 chip.
> +
> + - TI has already delivered a driver for a multi-function chip called ti-st.
> + This driver is currently located in drivers/misc/ti-st/. There has however
> + been criticism raised against design/architecture of the driver. There
> + currently also doesn't seem to be a way to add support for cg2900 in that
> + driver even though some people has raised this as an alternative.
As someone who is definitely the part of these demotivating and
unreasonable "some people" I have to say that even though I'm okay
with this driver going into staging, I see a huge gap between the
desire of its creators to have something generic and the ability to do
so. I am absolutely sure that given the widely advertised
peculiarities of this chip, the authors should stop trying to come up
with a generic solution and just present a simplistic MFD driver for
their particular device.
Thanks,
Vitaly
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists