mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 1/8] ARM: add very initial support for Canon DIGIC chips
Date: Mon, 26 Aug 2013 22:51:48 +0400	[thread overview]
Message-ID: <20130826225148.789cb51a803900ceb21f77ae@gmail.com> (raw)
In-Reply-To: <20130826132018.GF13964@titan.lakedaemon.net>

On Mon, 26 Aug 2013 09:20:18 -0400
Jason Cooper <jason@lakedaemon.net> wrote:

> Hi Antony,
> 
> On Mon, Aug 26, 2013 at 08:57:10AM +0400, Antony Pavlov wrote:
> > TODO: the clocksource driver need improvement!
> > 
> > Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> > ---
> >  arch/arm/Kconfig                            |  9 ++++
> >  arch/arm/Makefile                           |  1 +
> >  arch/arm/dts/digic4.dtsi                    | 24 +++++++++++
> >  arch/arm/mach-digic/Kconfig                 | 11 +++++
> >  arch/arm/mach-digic/Makefile                |  2 +
> >  arch/arm/mach-digic/core.c                  | 24 +++++++++++
> >  arch/arm/mach-digic/csrc-timer.c            | 67 +++++++++++++++++++++++++++++
> >  arch/arm/mach-digic/include/mach/debug_ll.h | 40 +++++++++++++++++
> >  arch/arm/mach-digic/include/mach/digic4.h   | 29 +++++++++++++
> >  arch/arm/mach-digic/include/mach/gpio.h     |  1 +
> >  10 files changed, 208 insertions(+)
> >  create mode 100644 arch/arm/dts/digic4.dtsi
> >  create mode 100644 arch/arm/mach-digic/Kconfig
> >  create mode 100644 arch/arm/mach-digic/Makefile
> >  create mode 100644 arch/arm/mach-digic/core.c
> >  create mode 100644 arch/arm/mach-digic/csrc-timer.c
> >  create mode 100644 arch/arm/mach-digic/include/mach/debug_ll.h
> >  create mode 100644 arch/arm/mach-digic/include/mach/digic4.h
> >  create mode 100644 arch/arm/mach-digic/include/mach/gpio.h
> > 
> ...
> > diff --git a/arch/arm/mach-digic/include/mach/debug_ll.h b/arch/arm/mach-digic/include/mach/debug_ll.h
> > new file mode 100644
> > index 0000000..5f4579e
> > --- /dev/null
> > +++ b/arch/arm/mach-digic/include/mach/debug_ll.h
> > @@ -0,0 +1,40 @@
> > +/*
> > + * Copyright (C) 2013 Antony Pavlov <antonynpavlov@gmail.com>
> > + *
> > + * This file is part of barebox.
> > + * See file CREDITS for list of people who contributed to this project.
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2
> > + * as published by the Free Software Foundation.
> > + *
> > + * This program is distributed in the hope that it will be useful,
> > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> > + * GNU General Public License for more details.
> > + *
> > + */
> > +
> > +#ifndef __MACH_DEBUG_LL_H__
> > +#define __MACH_DEBUG_LL_H__
> > +
> > +#include <io.h>
> > +#include <mach/digic4.h>
> > +
> > +#define DEBUG_LL_UART         DIGIC4_UART
> > +
> > +/* Serial interface registers */
> > +#define DEBUG_LL_UART_TX         (DEBUG_LL_UART + 0x0)
> > +#define DEBUG_LL_UART_ST         (DEBUG_LL_UART + 0x14)
> > + #define UART_ST_TX_RDY	2
> 
> leading whitespace, and perhaps use BIT() here.

The leading whitespace is put here intentionally to distinguish register address macros
and bit fields macros.

> > +
> > +static inline void PUTC_LL(char ch)
> > +{
> > +	while (!(readl(DEBUG_LL_UART_ST) & UART_ST_TX_RDY))
> > +		; /* noop */
> > +
> > +	writel(0x06, DEBUG_LL_UART_ST);
> 
> could you use a macro here for 0x06?

It is not so easy. See comments in serial driver: there is no public documentation
on Canon Digic chips. This driver is result of reverse engineering.
I have no complete information about the bitfield meaning. In this situation
it's very difficult to invent adequate names for the bitfield macros.
E.g. I have given the DEBUG_LL_UART_ST name to the register (I mean STATUS register).
But now I see that It is not just a status register but a control register too.
Just now I prefere to keep the names and constants as-is.

Moreover the situation with digic timers is worse as I don't know meaning of most bitfields :)

> > +	writel(ch, DEBUG_LL_UART_TX);
> > +}
> > +
> > +#endif
> 
> thx,
> 
> Jason.


-- 
-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-08-26 18:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  4:57 [RFC 0/8] barebox on Canon cameras: serial console and dts support Antony Pavlov
2013-08-26  4:57 ` [RFC 1/8] ARM: add very initial support for Canon DIGIC chips Antony Pavlov
2013-08-26 13:20   ` Jason Cooper
2013-08-26 18:51     ` Antony Pavlov [this message]
2013-08-26 19:47       ` Jason Cooper
2013-08-26 23:32         ` Sebastian Hesselbarth
2013-08-27  1:46           ` Jason Cooper
2013-08-27  4:57             ` Antony Pavlov
2013-08-27  7:00           ` Jürgen Beisert
2013-08-26  4:57 ` [RFC 2/8] serial: add driver for Canon DIGIC UART Antony Pavlov
2013-08-26 13:28   ` Jason Cooper
2013-08-26  4:57 ` [RFC 3/8] gpio: add driver for Canon DIGIC Antony Pavlov
2013-08-26  4:57 ` [RFC 4/8] ARM: DIGIC: add Canon PowerShot A1100 IS support Antony Pavlov
2013-08-26  4:57 ` [RFC 5/8] ARM: DIGIC: add canon-a1100_defconfig Antony Pavlov
2013-08-26  4:57 ` [RFC 6/8] ARM: DIGIC: add csrc-dummy Antony Pavlov
2013-08-26  4:57 ` [RFC 7/8] ARM: DIGIC: add Canon EOS 600D support Antony Pavlov
2013-08-26  4:57 ` [RFC 8/8] ARM: DIGIC: add canon-600d_defconfig Antony Pavlov

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=20130826225148.789cb51a803900ceb21f77ae@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jason@lakedaemon.net \
    /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