From: "Nobuhiro Iwamatsu" <iwamatsu@nigauri.org>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: linux-pcmcia@lists.infradead.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pcmcia: Add support P2CCLK bit enabler for TI PC1520
Date: Sat, 12 Jan 2008 10:04:11 +0900 [thread overview]
Message-ID: <29ab51dc0801111704i3accfa05v24cece3cdbdf992b@mail.gmail.com> (raw)
In-Reply-To: <20071225140419.9d2d80db.akpm@linux-foundation.org>
2007/12/26, Andrew Morton <akpm@linux-foundation.org>:
> On Tue, 18 Dec 2007 18:57:24 +0900 Nobuhiro Iwamatsu <iwamatsu@nigauri.org> wrote:
>
> > There is a device that doesn't work when P2CCLK's bit of TI PC1520 was disable.
> > This patch supports P2CCLK bit enabler for TI PC1520.
> >
> > ...
> >
> > config YENTA_TOSHIBA
> > default y
> > bool "Special initialization for Toshiba ToPIC bridges" if EMBEDDED
> > diff --git a/drivers/pcmcia/ti113x.h b/drivers/pcmcia/ti113x.h
> > index d29657b..ea749e8 100644
> > --- a/drivers/pcmcia/ti113x.h
> > +++ b/drivers/pcmcia/ti113x.h
> > @@ -59,6 +59,7 @@
> > #define TI122X_SCR_SER_STEP 0xc0000000
> > #define TI122X_SCR_INTRTIE 0x20000000
> > #define TIXX21_SCR_TIEALL 0x10000000
> > +#define TI122X_SCR_P2CCLK 0x08000000
> > #define TI122X_SCR_CBRSVD 0x00400000
> > #define TI122X_SCR_MRBURSTDN 0x00008000
> > #define TI122X_SCR_MRBURSTUP 0x00004000
> > @@ -822,6 +823,13 @@ static int ti12xx_override(struct yenta_socket *socket)
> > printk(KERN_INFO "Yenta: Enabling burst memory read transactions\n");
> > val |= TI122X_SCR_MRBURSTUP;
> > }
> > +
> > +#ifdef CONFIG_YENTA_TI_P2CCLK
> > + if ( !(val & TI122X_SCR_P2CCLK)) {
> > + printk(KERN_INFO "Yenta: Clock generated by internal oscillator\n");
> > + val |= TI122X_SCR_P2CCLK;
> > + }
> > +#endif
> > if (val_orig != val)
> > config_writel(socket, TI113X_SYSTEM_CONTROL, val);
>
> It would be much better if we cold do this without the config option: just
> detect the appropriate device and make it work.
This bit is enable for PC in BIOS.
However, I think that I want to control even by the kernel in
building in because it is a boot loader situation.
I think that this will not be able to be done by automatic.
Please apply this patch.
regards,
Nobuhiro
next prev parent reply other threads:[~2008-01-12 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 9:57 Nobuhiro Iwamatsu
2007-12-25 22:04 ` Andrew Morton
2008-01-12 1:04 ` Nobuhiro Iwamatsu [this message]
2008-01-12 1:33 ` Andrew Morton
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=29ab51dc0801111704i3accfa05v24cece3cdbdf992b@mail.gmail.com \
--to=iwamatsu@nigauri.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-sh@vger.kernel.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
Powered by JetHome