[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 11 Nov 2014 14:38:08 +0200
From: Laurentiu Palcu <laurentiu.palcu@...el.com>
To: Mark Brown <broonie@...nel.org>
Cc: Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Johan Havold <johan@...nel.org>,
Octavian Purdila <octavian.purdila@...el.com>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] spi: add support for DLN-2 USB-SPI adapter
Hi Mark,
On Sat, Nov 08, 2014 at 10:46:06AM +0000, Mark Brown wrote:
> On Fri, Nov 07, 2014 at 02:45:13PM +0200, Laurentiu Palcu wrote:
>
> > +static int dln2_spi_transfer_one_message(struct spi_master *master,
> > + struct spi_message *msg)
>
> It's a bit sad not to do transfer_one() but it's reasonable not to
> because of the fun way /CS is being set.
My first attempts were with transfer_one()/set_cs() until I realized,
using an oscilloscope, that DLN2 automatically toggles the /CS during
read/write operations and that DLN2_SPI_SET_SS only instructs device
which CS pins to toggle... :/
>
> > + ret = dln2_spi_get_speed_range(dln2,
> > + &master->min_speed_hz,
> > + &master->max_speed_hz);
>
> Strange indentation here.
I did some last minute function renaming and forgot to re-indent. Will
fix in v2.
>
> > +static int dln2_spi_remove(struct platform_device *pdev)
> > +{
> > + struct spi_master *master = spi_master_get(platform_get_drvdata(pdev));
> > + struct dln2_spi *dln2 = spi_master_get_devdata(master);
> > +
> > + if (dln2_spi_enable(dln2, false) < 0)
> > + dev_err(&pdev->dev, "Failed to disable SPI module\n");
> > +
> > + spi_master_put(master);
>
> You shouldn't need this _put(), it's defeating the purpose of having the
> devm_ registration.
Agreed! I used spi-rockchip.c as a template and I took it for granted.
I'll remove this line in v2. And, if you think it's worth it, I can send
a separate patch for spi-rockchip.c too.
thanks,
laurentiu
--
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