From: Alan Cox <alan@linux.intel.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rdunlap@infradead.org, gregkh@linuxfoundation.org,
jslaby@suse.cz, grant.likely@linaro.org, varkabhadram@gmail.com,
heiko@sntech.de, yingjoe.chen@gmail.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 1/2] tty: serial: 8250: Add Mediatek UART driver
Date: Thu, 07 Aug 2014 14:21:54 +0100 [thread overview]
Message-ID: <1407417714.8334.8.camel@acox1-desk.ger.corp.intel.com> (raw)
In-Reply-To: <1407394292-26317-2-git-send-email-matthias.bgg@gmail.com>
> + * Some baudrates are not supported by the chip, so we use the next
> + * lower rate supported and update termios c_flag.
I don't see the termios updating being done now ?
> + data->clk = of_clk_get(np, 0);
> + if (IS_ERR(data->clk)) {
> + pr_warn("Can't get timer clock");
> + return PTR_ERR(data->clk);
> + }
> +
> + err = clk_prepare_enable(data->clk);
> + if (err) {
> + pr_warn("Can't prepare clock");
and these do need a newline on them. They are also not very useful as
they don't indicate what device was involved. If you passed pdev from
mtk8250_probe you'd be able to use dev_warn instead
Otherwise looks great and exactly as 8250_core is intended to be used.
Alan
next prev parent reply other threads:[~2014-08-07 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 6:51 [PATCH v2 0/2] tty: serial: Add mediatek " Matthias Brugger
2014-08-07 6:51 ` [PATCH v2 1/2] tty: serial: 8250: Add Mediatek " Matthias Brugger
2014-08-07 13:21 ` Alan Cox [this message]
2014-08-07 14:07 ` Matthias Brugger
2014-08-07 18:35 ` One Thousand Gnomes
2014-08-07 6:51 ` [PATCH v2 2/2] DTS: serial: Add bindings documention for the Mediatek UARTs Matthias Brugger
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=1407417714.8334.8.camel@acox1-desk.ger.corp.intel.com \
--to=alan@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=varkabhadram@gmail.com \
--cc=yingjoe.chen@gmail.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
all inboxes | Powered by JetHome®