[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1407417714.8334.8.camel@acox1-desk.ger.corp.intel.com>
Date: Thu, 07 Aug 2014 14:21:54 +0100
From: Alan Cox <alan@...ux.intel.com>
To: Matthias Brugger <matthias.bgg@...il.com>
Cc: linux-kernel@...r.kernel.org, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
rdunlap@...radead.org, gregkh@...uxfoundation.org, jslaby@...e.cz,
grant.likely@...aro.org, varkabhadram@...il.com, heiko@...ech.de,
yingjoe.chen@...il.com, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH v2 1/2] tty: serial: 8250: Add Mediatek UART driver
> + * 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
--
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