[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201302161343.43434.arnd@arndb.de>
Date: Sat, 16 Feb 2013 13:43:43 +0000
From: Arnd Bergmann <arnd@...db.de>
To: "Russell King - ARM Linux" <linux@....linux.org.uk>
Cc: Viresh Kumar <viresh.kumar@...aro.org>,
Vinod Koul <vinod.koul@...ux.intel.com>,
Vinod Koul <vinod.koul@...el.com>,
devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Dan Williams <djbw@...com>, Olof Johansson <olof@...om.net>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/4] dmaengine: dw_dmac: move to generic DMA binding
On Saturday 16 February 2013, Russell King - ARM Linux wrote:
> On Sat, Feb 16, 2013 at 10:07:39AM +0000, Arnd Bergmann wrote:
> > On Saturday 16 February 2013, Viresh Kumar wrote:
> > > On 15 February 2013 23:51, Arnd Bergmann <arnd@...db.de> wrote:
> > > > +static bool dw_dma_generic_filter(struct dma_chan *chan, void *param)
> > > > {
> > >
> > > > + dws->cfg_hi = 0xffffffff;
> > > > + dws->cfg_lo = 0xffffffff;
> > >
> > > s/0xffffffff/-1 ?
> >
> > It's an 'unsigned int'. While -1 would work here, I always find it a little
> > odd to rely on that feature of the C language.
>
> However, relying on an 'int' being 32-bits is also rather odd, and
> probably much more dubious too. If you want to set all bits in an
> int, the portable way to do that is ~0.
Right, I can do that, too. All I really need here though is to make sure
I use the same value in this place and when comparing it in dwc_initialize,
and it needs to be something that cannot be a valid register setting.
Thanks,
Arnd
--
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