devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@mediatek.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: devicetree@vger.kernel.org, heikki.krogerus@linux.intel.com,
	vigneshr@ti.com, gregkh@linuxfoundation.org, jslaby@suse.com,
	hpeter@gmail.com, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
	linux-serial@vger.kernel.org, jan.kiszka@siemens.com,
	matthias.bgg@gmail.com,
	"arnd.bergmann" <arnd.bergmann@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] serial: 8250: add support for MediaTek BTIF controller
Date: Thu, 3 Aug 2017 11:18:11 +0800	[thread overview]
Message-ID: <1501730291.21633.12.camel@mtkswgap22> (raw)
In-Reply-To: <1501696935.29303.367.camel@linux.intel.com>

On Wed, 2017-08-02 at 21:02 +0300, Andy Shevchenko wrote:
> On Thu, 2017-08-03 at 01:37 +0800, Sean Wang wrote:
> > On Wed, 2017-08-02 at 20:14 +0300, Andy Shevchenko wrote:
> > > On Thu, 2017-08-03 at 01:05 +0800, sean.wang@mediatek.com wrote:
> > > > From: Sean Wang <sean.wang@mediatek.com>
> > > > 
> > > > This patchset introduces the support for MediaTek BTIF controller.
> > > > 
> > > > MediaTek BTIF controller is the serial interface similar to UART
> > > > but
> > > > it
> > > > works only as the digital device which is mainly used to
> > > > communicate
> > > > with
> > > > the connectivity module also called CONNSYS inside the SoC which
> > > > could
> > > > be
> > > > mostly found on those MediaTek SoCs with Bluetooth feature.
> > > > 
> > > > And the controller is made as being compatible with the 8250
> > > > register
> > > > layout so it tends to be integrated with existing 8250 core driver
> > > > and
> > > > have no requirement for the modem configuration additionally such
> > > > as
> > > > the
> > > > baud rate calculation and assignment.
> 
> +Cc: Arnd.
> 
> > > Why it requires a separate driver?
> > > 
> > > 8250_of is for DT enabled drivers.
> > > 
> > 
> > Hi, Andy
> > 
> > thanks for your information
> > 
> > the hardware is not completely identical to 8250 device, 
> > it has extra registers belonged to platform control such as internal
> > loopback, dma disable/enable, sleep/wakeup setup and so on, so I
> > create
> > it as a separate driver.
> 
> Over all 200+ LOCs I didn't see any of the above except loopback, which
> is one property that can be easily added to 8250_of.c.
> 
> Moreover, if you have more code coming I would suggest you to split
> 8250_of to library and driver parts and re-use stuff from there.
> 
> Arnd, what is your opinion about new 8250 OF based drivers?
> 

Hi, Andy

many thanks for the detailed guidance.
I will turn into reusing 8250 OF stuff in the next version and look
forward to any idea from Arnd how to do with 8250 OF driver to add
specific programming/data for those devices using 8250 OF.

	Sean

      reply	other threads:[~2017-08-03  3:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 17:05 [PATCH 0/2] serial: 8250: add support for MediaTek BTIF controller sean.wang
2017-08-02 17:05 ` [PATCH 1/2] dt-bindings: serial: Add MediaTek BTIF controller bindings sean.wang
2017-08-10 16:27   ` Rob Herring
2017-08-11  2:53     ` Sean Wang
2017-08-11 14:31       ` Rob Herring
2017-08-02 17:05 ` [PATCH 2/2] tty: serial: 8250: Add MediaTek BTIF controller on MT7622 and MT7623 SoC sean.wang
2017-08-02 17:14 ` [PATCH 0/2] serial: 8250: add support for MediaTek BTIF controller Andy Shevchenko
     [not found]   ` <1501694063.29303.361.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-08-02 17:37     ` Sean Wang
2017-08-02 18:02       ` Andy Shevchenko
2017-08-03  3:18         ` Sean Wang [this message]

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=1501730291.21633.12.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=hpeter@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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 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).