Re: [PATCH 2/4] remoteproc: Supply controller driver for ST's Remote Processors

From: Lee Jones
Date: Thu Aug 27 2015 - 02:45:47 EST


On Wed, 26 Aug 2015, Nathan Lynch wrote:

> On 08/26/2015 08:08 AM, Lee Jones wrote:
> > --- /dev/null
> > +++ b/drivers/remoteproc/st_remoteproc.c
> > @@ -0,0 +1,300 @@
> > +/*
> > + * ST's Remote Processor Control Driver
> > + *
> > + * Copyright (C) 2015 STMicroelectronics - All Rights Reserved
> > + *
> > + * Author: Ludovic Barre <ludovic.barre@xxxxxx>
>
> When submitting code you didn't write, I'd say it's better practice to
> clearly indicate its provenance in the commit message. E.g. something
> like "Driver based on code authored by Ludovic Barre for ST". And
> obtain signoffs etc if possible.
>
>
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License as published by
> > + * the Free Software Foundation; either version 2 of the License.
>
> Please review the wording here. It's unclear whether this is intended
> to be v2-only or v2 or later.
>
>
> > +static int st_rproc_stop(struct rproc *rproc)
> > +{
> > + struct st_rproc *st_rproc = rproc->priv;
> > + int err = 0;
> > +
> > + if (st_rproc->config->sw_reset) {
> > + err = reset_control_assert(st_rproc->sw_reset);
> > + if (err)
> > + dev_warn(&rproc->dev, "Failed to assert S/W Reset\n");
> > + }
> > +
> > + if (st_rproc->config->pwr_reset) {
> > + err = reset_control_assert(st_rproc->pwr_reset);
> > + if (err)
> > + dev_warn(&rproc->dev, "Failed to assert Power Reset\n");
> > + }
> > +
> > + clk_disable(st_rproc->clk);
> > +
> > + return 0;
> > +}
>
> Seems like st_rproc_stop should propagate errors back to its caller
> instead of always returning 0.

Good points, will fix.

--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org â Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/