From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Antonio Ospite <ospite@studenti.unina.it>,
Sascha Hauer <s.hauer@pengutronix.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] V4L/DVB: mx1-camera: compile fix
Date: Fri, 12 Mar 2010 10:41:48 +0100 [thread overview]
Message-ID: <20100312094148.GA15123@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1003121016480.4385@axis700.grange>
Hello,
On Fri, Mar 12, 2010 at 10:22:31AM +0100, Guennadi Liakhovetski wrote:
> On Fri, 5 Mar 2010, Uwe Kleine-König wrote:
> > This is a regression of
> >
> > 7d58289 (mx1: prefix SOC specific defines with MX1_ and deprecate old names)
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > drivers/media/video/mx1_camera.c | 12 +++++++-----
> > 1 files changed, 7 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/media/video/mx1_camera.c b/drivers/media/video/mx1_camera.c
> > index 2ba14fb..29c2833 100644
> > --- a/drivers/media/video/mx1_camera.c
> > +++ b/drivers/media/video/mx1_camera.c
> > @@ -45,11 +45,13 @@
> > #include <mach/hardware.h>
> > #include <mach/mx1_camera.h>
> >
> > +#define __DMAREG(offset) (MX1_IO_ADDRESS(MX1_DMA_BASE_ADDR) + offset)
> > +
>
> Well, I think, Sascha is right, we have to fix
> arch/arm/plat-mxc/include/mach/dma-mx1-mx2.h, because that's what actually
> got broken. The line
>
> #define DMA_BASE IO_ADDRESS(DMA_BASE_ADDR)
>
> in it is no longer valid, right? So, we have to either remove it, or fix
> it, if we think, that other drivers might start using it.
I thought a minimal fix would be a good idea. I have no problem with a
clean one though.
> And even if we
> decide to remove it from the header and implement here, wouldn't it be
> better to choose a name, not beginning with "__"? Something like
> MX1_DMA_REG, perhaps?
Then the register definitions should go into the header, too. I will
prepare a patch later today.
> Or maybe even we shall remap those registers?
Well, they are remapped, don't they? Otherwise IO_ADDRESS wouldn't
work.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-03-12 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 16:54 [PATCH] V4L/DVB: mx1-camera: compile fix Uwe Kleine-König
2010-03-04 17:13 ` Guennadi Liakhovetski
2010-03-04 19:26 ` Uwe Kleine-König
2010-03-04 19:42 ` Sascha Hauer
2010-03-05 10:45 ` [PATCH v2] " Uwe Kleine-König
2010-03-12 9:22 ` Guennadi Liakhovetski
2010-03-12 9:41 ` Uwe Kleine-König [this message]
2010-03-12 9:58 ` Guennadi Liakhovetski
2010-03-16 9:52 ` [PATCH] " Uwe Kleine-König
2010-03-16 11:01 ` Guennadi Liakhovetski
2010-03-27 21:42 ` Uwe Kleine-König
2010-03-28 20:12 ` Guennadi Liakhovetski
2010-03-31 8:40 ` Sascha Hauer
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=20100312094148.GA15123@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=ospite@studenti.unina.it \
--cc=s.hauer@pengutronix.de \
/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