From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: linux-kernel@vger.kernel.org,
Jonas Fonseca <jonas.fonseca@savoirfairelinux.com>,
platform-driver-x86@vger.kernel.org,
linux-serial@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [RFC 1/5] platform-drivers-x86: add support for Technologic Systems TS-5xxx detection
Date: Sat, 30 Apr 2011 11:07:05 +0100 [thread overview]
Message-ID: <20110430110705.5ca3376b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1304115712-5299-2-git-send-email-vivien.didelot@savoirfairelinux.com>
> + * ts5xxx_sbcinfo_set() - set the SBC info structure with the current SBC's info
> + * @sbcinfo: structure containing SBC info to set.
> + */
> +void ts5xxx_sbcinfo_set(struct ts5xxx_sbcinfo *sbcinfo)
> +{
> + memcpy(sbcinfo, &ts_sbcinfo, sizeof(*sbcinfo));
> +}
> +EXPORT_SYMBOL(ts5xxx_sbcinfo_set);
You export this but it's not clear who for or why - and there is also no
locking, so it seems to be an internal interface ?
> +/**
> + * ts_find_sbc_config() - find a SBC configuration from an id
> + * @id: ID of the board to find.
> + */
> +static inline struct ts_sbc_config *ts_find_sbc_config(u8 id)
> +{
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(ts_sbcs_configs); i++)
> + if (id == ts_sbcs_configs[i].id)
> + return &ts_sbcs_configs[i];
> +
> + return NULL;
> +}
gcc will figure out inlines for you in static stuff and normally very well
> +
> +/**
> + * ts_sbcinfo_detect() - detect the TS board
> + * @sbcinfo: structure where to store the detected board's info.
> + */
> +static int ts_sbcinfo_detect(struct ts5xxx_sbcinfo *sbcinfo)
> +{
> + u8 temp;
> + struct ts_sbc_config *sbc;
> + int ret = 0;
> +
> + memset(sbcinfo, 0, sizeof(*sbcinfo));
> +
> + if (!request_region(IOADDR_SBCID, 4, "TS-SBC"))
> + return -EBUSY;
> +
> + temp = inb(IOADDR_SBCID);
> + /* If it is a 3x00 SBC only match against the first 3 bits */
> + if (temp & 0x07)
> + temp &= 0x07;
So if this is compiled into a kernel we blindly inb this address and some
platform just crashed on boot. Is this board like other embedded ones in
that there is some safe way to check if its such a board first ?
> +
> + sbc = ts_find_sbc_config(temp);
> + if (!sbc) {
> + ret = -ENODEV;
Assuming you've indentified the board properly this case might be worth a
pr_err giving the fact it seemed to be a TS-5xxx, the config number and
that it is unknown - that will help anyone with future boards realise
their config isn't supported.
> +
> +/**
> + * ts_sbcinfo_proc_read() - function called when a read access is done on
> + * /proc/ts-sbcinfo
> + */
> +static int ts_sbcinfo_proc_read(char *page, char **start, off_t off,
> + int count, int *eof, void *data)
> +{
> + int to_copy = (procfs_buffer_size <= count) ?
> + procfs_buffer_size - off : count;
> +
> + if (off + to_copy >= procfs_buffer_size) {
> + to_copy = procfs_buffer_size - off;
> + *eof = 1;
> + }
Suppose off is 0x7FFFFFFF and count = 100
to_copy = 100
off + to_copy >= procfs_buffer_size [off_t may be 32bit]
100 + 0x7FFFFFFF (wraps) < buffer size
> +static int __init ts5xxx_sbcinfo_init(void)
> +{
> + int err;
> +
> + err = ts_sbcinfo_detect(&ts_sbcinfo);
> + if (err < 0) {
> + printk(KERN_ERR KBUILD_MODNAME
> + ": Failed to get SBC information\n");
> + return err;
> + }
Well that will depend why and probably the caller can give the best
information including silence if the board is just not a ts-5xxx
> + proc_entry = create_proc_read_entry(PROCFS_NAME, S_IRUGO, NULL,
> + ts_sbcinfo_proc_read, 0);
> + if (proc_entry == NULL) {
> + printk(KERN_ERR KBUILD_MODNAME
> + ": Failed to create proc entry\n");
pr_err
> + return -ENOMEM;
> + }
> +
> + procfs_buffer_size = ts_sbcinfo_init_buffer(procfs_buffer, &ts_sbcinfo);
> + printk(KBUILD_MODNAME ": TS SBC's info driver loaded.\n");
Printk not needed
Alan
next prev parent reply other threads:[~2011-04-30 10:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:21 [RFC 0/5] Support for Technologic Systems TS-5500 board Vivien Didelot
2011-04-29 22:21 ` [RFC 1/5] platform-drivers-x86: add support for Technologic Systems TS-5xxx detection Vivien Didelot
2011-04-29 23:32 ` Greg KH
2011-05-02 21:07 ` Vivien Didelot
2011-05-02 21:55 ` Greg KH
2011-05-03 9:39 ` Alan Cox
2011-05-03 14:13 ` Greg KH
2011-04-30 10:07 ` Alan Cox [this message]
2011-05-04 15:15 ` Vivien Didelot
2011-05-04 15:29 ` Alan Cox
2011-05-04 20:34 ` Vivien Didelot
2011-05-05 13:38 ` Alan Cox
2011-05-11 22:24 ` Vivien Didelot
2011-05-17 12:37 ` Sean Young
2011-05-18 15:03 ` Vivien Didelot
2011-04-29 22:21 ` [RFC 2/5] gpio: add support for Technologic Systems TS-5500 GPIOs Vivien Didelot
2011-04-30 10:15 ` Alan Cox
2011-05-13 21:33 ` Vivien Didelot
2011-05-13 22:03 ` Alan Cox
2011-05-04 16:29 ` Arnd Bergmann
2011-04-29 22:21 ` [RFC 3/5] serial: add support for Technologic Systems TS-5500 RS-485 serial port Vivien Didelot
2011-04-30 10:17 ` Alan Cox
2011-06-06 20:48 ` Vivien Didelot
2011-04-29 22:21 ` [RFC 4/5] leds: add support for Technologic Systems TS-5500 leds Vivien Didelot
2011-05-03 6:04 ` Govindraj
2011-04-29 22:21 ` [RFC 5/5] hwmon: add support for Technologic Systems TS-5500 A-D converter Vivien Didelot
2011-04-30 3:39 ` [lm-sensors] " Guenter Roeck
2011-04-30 9:56 ` Jonathan Cameron
2011-05-03 15:55 ` Vivien Didelot
2011-05-03 17:33 ` Guenter Roeck
2011-05-04 9:03 ` Jonathan Cameron
2011-04-30 10:20 ` Alan Cox
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=20110430110705.5ca3376b@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jonas.fonseca@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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
all inboxes | Powered by JetHome®