From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 V3] MXS: Implement DMA support into mxs-i2c
Date: Sun, 22 Jul 2012 10:33:43 +0200 [thread overview]
Message-ID: <20120722083343.GA31508@pengutronix.de> (raw)
In-Reply-To: <201207211754.29372.marex@denx.de>
> > Even if the driver was matched because of an MX23-I2C "compatible"
> > binding, both devicetree and runtime could provide data that it actually
> > runs on MX28. That shouldn't be a problem.
>
> You mean like ... cpu_is_mx28() ? We got rid of that in favor of DT.
Might be. But the information is probably somewhere.
> > IIRC I mentioned that a discussion about the bindings won't make the
> > next merge window.
>
> Yet another merge window, I have to mention. And only because very long pauses
> inbetween reviews and very minor nitpicks. I'm being annoyed by this patch so
> much I'm thinking of giving up on this. I wasted too much of my free time on
> this and the result is as is.
For you it might be a minor nitpick, for me (as a maintainer) it is not.
You have to deal with just one binding, I have to deal with many. And
since they have to be supported forever, this can easily mess up code
and make the subsystem clumsy and whatnot.
> > That's why I proposed either module_parameter
>
> Which I explained is not a way to go.
That's why I called it inbetween solution so the patch could go in.
It's fine if you don't like it, I prefer dropping the binding as well.
> > or
> > dropping the binding entirely as possible inbetween options.
>
> Which is not an option either.
It would enable you to add the binding as an out-of-tree patch.
> And this discussion is only further stalling the
> patch.
> We're adding fsl,something properties all over the DT all the time, yet this one
> is of concern?
Yes. Adding all these properties is IMO not the right way, and I have
the impression they often came in because of time pressure like this. If
I think it is wrong for the kernel, I have to reject a patch unless I am
convinced otherwise. Which did not happen yet; as you found out
discussions on devicetree-discuss are slow. Might be another indication
that devictree things happen too much at the time currently. This is not
specific to your patch, there are more which need discussion or had to
be reworked.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120722/ce0a1af1/attachment.sig>
next prev parent reply other threads:[~2012-07-22 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 16:22 [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-07-09 16:22 ` [PATCH 2/2 V3] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-07-13 8:22 ` Wolfram Sang
2012-07-13 12:10 ` Marek Vasut
2012-07-14 11:29 ` Wolfram Sang
2012-07-14 12:09 ` Marek Vasut
2012-07-16 10:21 ` Wolfram Sang
2012-07-16 13:06 ` Marek Vasut
2012-07-16 13:25 ` Wolfram Sang
2012-07-15 8:17 ` Shawn Guo
2012-07-21 12:44 ` Wolfram Sang
2012-07-21 14:11 ` Marek Vasut
2012-07-21 15:41 ` Wolfram Sang
2012-07-21 15:54 ` Marek Vasut
2012-07-22 8:33 ` Wolfram Sang [this message]
2012-07-28 8:02 ` Shawn Guo
2012-07-13 8:07 ` [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Wolfram Sang
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=20120722083343.GA31508@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).