Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Kyungmin Park' <kyungmin.park@samsung.com>
Cc: 'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
	m.szyprowski@samsung.com
Subject: RE: [PATCH 1/4] mach-s5pv210: Add platform definitions for mipi-csis
Date: Fri, 03 Dec 2010 17:19:43 +0900	[thread overview]
Message-ID: <014901cb92c2$d9c9e8b0$8d5dba10$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTi=bARGdX2Y4Ea-YP8qQRcjAXme8NW9Mp-0dTxgZ@mail.gmail.com>

Kyungmin Park wrote:
> 
> On Fri, Dec 3, 2010 at 1:22 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > Sylwester Nawrocki wrote:
> >>
> >> Added resource definitions for mipi-csis interface, naming
> >> changed for consistency with s5pv310 where there are two
> >> instances of the device.
> >>
> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> >> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> >> ---
> >>  arch/arm/mach-s5pv210/include/mach/irqs.h       |    2 +-
> >>  arch/arm/mach-s5pv210/include/mach/map.h        |    4 ++++
> >>  arch/arm/mach-s5pv210/include/mach/regs-clock.h |    5 +----
> >>  3 files changed, 6 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/arch/arm/mach-s5pv210/include/mach/irqs.h b/arch/arm/mach-
> >> s5pv210/include/mach/irqs.h
> >> index 119b95f..8b5994c 100644
> >> --- a/arch/arm/mach-s5pv210/include/mach/irqs.h
> >> +++ b/arch/arm/mach-s5pv210/include/mach/irqs.h
> >> @@ -65,7 +65,7 @@
> >>  #define IRQ_HSMMC0           S5P_IRQ_VIC1(26)
> >>  #define IRQ_HSMMC1           S5P_IRQ_VIC1(27)
> >>  #define IRQ_HSMMC2           S5P_IRQ_VIC1(28)
> >> -#define IRQ_MIPICSI          S5P_IRQ_VIC1(29)
> >> +#define IRQ_MIPICSI0         S5P_IRQ_VIC1(29)
> >
> > Firstly don't use directly IRQ_MIPICSI0 which is used in platform
device.
> > Because it can be confused that there would be another MIPICSI such as
> > MIPICSI1.
> > In that case, just use like following. For example,
> Hi,
> 
> First respect others work.
> my impression is that you forced the developers to work as you want.
> 
> okay who summit this code? If you think name is odd, then you check it
> before you submitted.
> When you commit the code is okay, but other should be considered as yours.
> 

I can't get you :-(

Maybe your talking is to change the name? Why?...
When submitted it, used written name, IRQ_MIPICSI in datasheet.

But now, according to Sylwester's patch, used various name for it like
MIPICSI, MIPICSIS and so on.
So I suggested just one name in previous my comment.

> >
> > ---
> > @@ -132,5 +132,6 @@
> >  #define IRQ_LCD_FIFO           IRQ_LCD0
> >  #define IRQ_LCD_VSYNC          IRQ_LCD1
> >  #define IRQ_LCD_SYSTEM         IRQ_LCD2
> > +#define IRQ_MIPI_CSIS0         IRQ_MIPICSI
> >
> >  #endif /* ASM_ARCH_IRQS_H */
> > ---
> >
> > And I'm confused about the name of MIPI-CSI...
> > Hmm...used MIPICSI or MIPI_CSI, sometimes MIPICSIS or MIPI_CSIS.
> >
> > Maybe the meaning is Camera Serial Interface Slave...
> > So...how about to use just one such as "IRQ_MIPI_CSIS" and
> > "S5PV210_PA_MIPI_CSIS".
> 
> I think it's better use the common word, CSI. I can't find CSIS word
> at googling.
> 
But used it in datasheet. How about FIMC, I think, it depends on usage of
datasheet.

> >
> > ---
> > @@ -65,7 +65,7 @@
> >  #define IRQ_HSMMC0             S5P_IRQ_VIC1(26)
> >  #define IRQ_HSMMC1             S5P_IRQ_VIC1(27)
> >  #define IRQ_HSMMC2             S5P_IRQ_VIC1(28)
> > -#define IRQ_MIPICSI            S5P_IRQ_VIC1(29)
> > +#define IRQ_MIPI_CSIS          S5P_IRQ_VIC1(29)
> >  #define IRQ_MIPIDSI            S5P_IRQ_VIC1(30)
> >  #define IRQ_ONENAND_AUDI       S5P_IRQ_VIC1(31)
> >
> > @@ -132,5 +132,6 @@
> >  #define IRQ_LCD_FIFO           IRQ_LCD0
> >  #define IRQ_LCD_VSYNC          IRQ_LCD1
> >  #define IRQ_LCD_SYSTEM         IRQ_LCD2
> > +#define IRQ_MIPI_CSIS0         IRQ_MIPI_CSIS
> 
> In this case, I can't find any good reason since it's first used.
> as s3c series used the different names compare to s5p series. it's
> okay make these wrapper.
> but it's new one and not used previous time.
> 
I already commented about that.
Shortly, IRQ_MIPI_CSIS0 is used as common name for S5PV210 and S5PV310 in
plat-s5p.
And IRQ_MIPI_CSI is used as specific name on S5PV210. So needed it.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  reply	other threads:[~2010-12-03  8:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 16:37 [PATCH 0/4] ARM: S5P: Add platform support for MIPI-CSI2 devices Sylwester Nawrocki
2010-12-02 16:37 ` [PATCH 1/4] mach-s5pv210: Add platform definitions for mipi-csis Sylwester Nawrocki
2010-12-03  4:22   ` Kukjin Kim
2010-12-03  5:30     ` Kyungmin Park
2010-12-03  8:19       ` Kukjin Kim [this message]
2010-12-03  8:32         ` Kukjin Kim
2010-12-03 15:38       ` Sylwester Nawrocki
2010-12-03 13:23     ` Sylwester Nawrocki
2010-12-02 16:37 ` [PATCH 2/4] mach-s5pv310: Add resource " Sylwester Nawrocki
2010-12-03  4:36   ` Kukjin Kim
2010-12-03  4:59     ` Jassi Brar
2010-12-03  5:34       ` Kyungmin Park
2010-12-03  5:52         ` Jassi Brar
2010-12-03 10:24       ` Sylwester Nawrocki
2010-12-02 16:37 ` [PATCH 3/4] plat-s5p: Add platform support for MIPI-CSI2 devices Sylwester Nawrocki
2010-12-02 17:15   ` Jamie Iles
2010-12-02 17:39     ` Sylwester Nawrocki
2010-12-02 23:14       ` Jamie Iles
2010-12-03  1:37       ` Jassi Brar
2010-12-03  9:18         ` Jamie Iles
2010-12-03  9:59         ` Marek Szyprowski
2010-12-03  4:53   ` Kukjin Kim
2010-12-03 13:48     ` Sylwester Nawrocki
2010-12-03  5:14   ` Jassi Brar
2010-12-03  5:36     ` Kyungmin Park
2010-12-02 16:37 ` [PATCH 4/4] mach-s5pv210: Add MIPI-CSI DPHY clock definition Sylwester Nawrocki
2010-12-03  4:11 ` [PATCH 0/4] ARM: S5P: Add platform support for MIPI-CSI2 devices Kukjin Kim
2010-12-03 10:00   ` Sylwester Nawrocki

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='014901cb92c2$d9c9e8b0$8d5dba10$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=s.nawrocki@samsung.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