From: Martin Kaiser <martin@kaiser.cx>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sascha Hauer <kernel@pengutronix.de>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video: imxfb: correct the bitmask for DMACR_HM/_TM
Date: Wed, 23 Nov 2016 09:31:13 +0000 [thread overview]
Message-ID: <20161123093113.GA10071@botnar.kaiser.cx> (raw)
In-Reply-To: <20161122084214.fxn26mfur7wwlgs2@pengutronix.de>
Hello Uwe, all,
Thus wrote Uwe Kleine-König (u.kleine-koenig@pengutronix.de):
> For the MX1 which is also supported by this driver, the definitions are
> right.
ok, understood. I wasn't able to dig up an imx1 specification. Do you
know if it's publicly available?
> So this needs a more sophisticated patch. Also I wonder why the
> register definition is in include/linux/platform_data and not in the
> driver directly.
The DMACR_HM() and _TM() macros are meant to be used when we initialize
imx_fb_platform_data's dmacr component for a platform device. It's not
straightforward to distinguish between imx1 and imx21 at initialization
time.
We could modify imx_fb_platform_data to use different components for
dmacr_burst, dmacr_hm, dmacr_tm and calculate the dmacr register value
in the driver where is_imx1_fb() is available. Device tree is also using
a single dmacr entry, it's probably not a good idea to do this
differently for platform devices...
We could also define DMACR_HM_IMX1(), DMACR_HM_IMX21(), ...
Or we could just remove the macros, they are not used by any boards in
the mainline kernel. If we don't want to break proprietary board
definitions, we could at least add a comment that the macros are
incorrect for imx21.
Thoughts?
Best regards,
Martin
next prev parent reply other threads:[~2016-11-23 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 7:54 [PATCH] video: imxfb: correct the bitmask for DMACR_HM/_TM Martin Kaiser
2016-11-22 8:42 ` Uwe Kleine-König
2016-11-23 9:31 ` Martin Kaiser [this message]
2016-11-23 9:50 ` Uwe Kleine-König
2016-11-25 8:43 ` Martin Kaiser
2016-11-28 22:43 ` [PATCH] video: imxfb: remove the macros for initializing the DMACR Martin Kaiser
2016-11-29 7:49 ` Uwe Kleine-König
2016-11-29 19:50 ` [PATCH v2] " Martin Kaiser
2016-11-29 19:57 ` Uwe Kleine-König
[not found] ` <CGME20170111124006epcas5p138afe03766a09b68eac3f93a9047ee27@epcas5p1.samsung.com>
2017-01-11 12:39 ` Bartlomiej Zolnierkiewicz
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=20161123093113.GA10071@botnar.kaiser.cx \
--to=martin@kaiser.cx \
--cc=kernel@pengutronix.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@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;
as well as URLs for NNTP newsgroup(s).