public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/3] drm/i915: Change Mipi register definitions
Date: Mon, 2 Jun 2014 10:29:34 +0200	[thread overview]
Message-ID: <20140602082934.GK19050@phenom.ffwll.local> (raw)
In-Reply-To: <FF3DDC77922A8A4BB08A3BC48A1EA8CB016BDC48@BGSMSX101.gar.corp.intel.com>

On Sun, Jun 01, 2014 at 05:41:54AM +0000, Sharma, Shashank wrote:
> Hi Damien, 
> Please correct me if I am missing something, but the only reason we are
> seeing those extra formatting changes is, almost all of the old MIPI
> register definitions were beyond 80 char, and was checked in like that
> with warnings (How ?) So when I was checking for checkpatch errors, I
> saw that, and I tried to fix that in the previous patch. 

Checkpatch et al. isn't a hard rule here, and occasionally checkpatch is
just wrong. We have lots more exceptions in i915_reg.h since it makes it
easier to read in general.
-Daniel

> 
> Anyways, I will send another patch, as per your suggestions, which will include only the dev_priv->mmio_offset change, and rebase the other one on top of it.  
> 
> Regards
> Shashank
> -----Original Message-----
> From: Lespiau, Damien 
> Sent: Saturday, May 31, 2014 3:19 PM
> To: Sharma, Shashank
> Cc: Kumar, Shobhit; intel-gfx@lists.freedesktop.org; Vetter, Daniel; ville.syrjala@linux.intel.com
> Subject: Re: [PATCH 2/3] drm/i915: Change Mipi register definitions
> 
> On Sat, May 31, 2014 at 01:32:42PM +0530, Shashank Sharma wrote:
> > Re-define MIPI register definitions in such a way that most of the 
> > existing DSI code can be re-used for future platforms. Register 
> > definitions are re-written using MMIO offset variable, so that without 
> > changing the existing sequence, same code can be generically applied.
> > 
> > V4: Addressing review comments by Ville This patch removes all the 
> > un-necessary formatting changes.
> > V5: Addressing review comments by Damien Changed input variable name 
> > from tc to pipe
> > 
> > Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
> 
> I'm sorry if we haven't been clear enough, but in a patch that changes VLV_DISPLAY_BASE + 0xf00 to dev_priv->mipi_mmio_base + 0xf00, we can't
> have:
> 
> > -#define MIPI_PORT_CTRL(pipe)		_PIPE(pipe, _MIPIA_PORT_CTRL, _MIPIB_PORT_CTRL)
> > +#define MIPI_PORT_CTRL(pipe)			_PIPE(pipe, _MIPIA_PORT_CTRL, \
> > +						_MIPIB_PORT_CTRL)
> 
> That's the un-necessary formatting changes that Ville was talking about, and the "change only one thing per patch" I was talking about. In this case the change is "make VLV_DISPLAY_BASE + 0xfoo" to dev_priv->mipi_mmio_base + 0xf00", so the diff should only show that kind of changes.
> 
> Please bear with me for this one, let's get it "correct" and I'm sure the next ones will be easier.
> 
> --
> Damien
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-06-02  8:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 15:24 [PATCH 0/2] Make DSI code re-usable Shashank Sharma
2014-05-19 15:24 ` [PATCH 1/2] drm/i915: Add MIPI mmio reg base Shashank Sharma
2014-05-19 15:45   ` Damien Lespiau
2014-05-19 15:55     ` Daniel Vetter
2014-05-19 15:57     ` Daniel Vetter
2014-05-19 15:24 ` [PATCH 2/2] drm/i915: Change Mipi register definitions Shashank Sharma
2014-05-19 16:10   ` Damien Lespiau
2014-05-21 15:26     ` Shashank Sharma
2014-05-21 15:35       ` Ville Syrjälä
2014-05-21 15:44         ` Sharma, Shashank
2014-05-21 15:49         ` Damien Lespiau
2014-05-22 11:32         ` Shashank Sharma
2014-05-30  8:05           ` Sharma, Shashank
2014-05-30 10:13             ` Damien Lespiau
2014-05-30 14:42               ` [PATCH 2/3] " Shashank Sharma
2014-05-30 14:42                 ` [PATCH 3/3] drm/i915: Use transcoder as index to MIPI regs Shashank Sharma
2014-05-30 15:10                 ` [PATCH 2/3] drm/i915: Change Mipi register definitions Damien Lespiau
2014-05-31  8:02                   ` Shashank Sharma
2014-05-31  8:02                     ` [PATCH 3/3] drm/i915: Use transcoder as index to MIPI regs Shashank Sharma
2014-05-31  9:49                     ` [PATCH 2/3] drm/i915: Change Mipi register definitions Damien Lespiau
2014-06-01  5:41                       ` Sharma, Shashank
2014-06-02  8:29                         ` Daniel Vetter [this message]
2014-06-02 11:11                         ` Damien Lespiau
2014-06-01 13:54                       ` Shashank Sharma
2014-06-01 13:54                         ` [PATCH 3/3] drm/i915: Use transcoder as index to MIPI regs Shashank Sharma
2014-06-02 11:23                         ` [PATCH 2/3] drm/i915: Change Mipi register definitions Damien Lespiau
2014-06-02 12:37                           ` shashank.sharma
2014-06-02 12:37                             ` [PATCH 3/3] drm/i915: Use transcoder as index to MIPI regs shashank.sharma
2014-06-02 12:51                               ` Damien Lespiau
2014-06-02 12:55                                 ` Sharma, Shashank
2014-06-02 13:26                                   ` Damien Lespiau
2014-06-02 15:08                                     ` Sharma, Shashank
2014-06-02 12:42                             ` [PATCH 2/3] drm/i915: Change Mipi register definitions Damien Lespiau
2014-06-02 15:30                               ` Daniel Vetter

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=20140602082934.GK19050@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shashank.sharma@intel.com \
    /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