From: Michal Simek <monstr@monstr.eu>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
john.williams@petalogix.com, linux-kernel@vger.kernel.org,
hjk@linutronix.de, gregkh@suse.de
Subject: Re: [PATCH] uio/pdrv_genirq: Add OF support
Date: Thu, 31 Mar 2011 19:57:47 +0200 [thread overview]
Message-ID: <4D94C09B.4070506@monstr.eu> (raw)
In-Reply-To: <20110331170321.GA2734@local>
Hans J. Koch wrote:
> On Thu, Mar 31, 2011 at 03:28:41PM +0200, Michal Simek wrote:
>>>> + uioinfo->name = pdev->dev.of_node->name;
>>>> + /* Use version for storing full IP name for identification */
>>>> + uioinfo->version = pdev->dev.of_node->full_name;
>>> I don't think this is apropriate, but will leave that to Hans.
>> I was thinking what to add and I choose full_name because I can read
>> this value and identify which UIO is this device.
>> I know that there should be version but there is no version string in DTS.
>
> The purpose of uio_info->version is to give the userspace part of the driver
> additional information. Kernel part and userspace part might be developed
> independently, and there should be a chance for the userspace part to find
> out if a certain feature is already supported by the kernel part without
> having to do dirty kernel version checks.
>
> So, uio_info->version is an information about the driver, not the hardware.
>
> Example: You write a UIO driver for a chip you use in a project. You don't
> need all the functionality of that chip. One year later you need additional
> chip functionality, and it turns out that you have to do certain
> initializations in the kernel part. Your new userspace will need the new
> kernel driver, but there are lots of older kernels around in your customers
> devices. In that case, your userspace part can simply check the version
> string in sysfs and require at least your new version.
I understand reasons but this information is not in device tree and it must be
setup.
Grant suggested compatible string but it is not the best option too.
>
>>>> + /* Get IRQ for the device */
>>>> + rc = of_irq_to_resource(pdev->dev.of_node, 0, &r_irq);
>>>> + if (rc == NO_IRQ)
>>>> + dev_err(&pdev->dev, "no IRQ found\n");
>>> No error, I think. Sometimes just mmaping the registers is enough.
>> OK. Let's changed it to dev_info if you like.
>
> The correct thing is to set uio_info->irq to UIO_IRQ_NONE.
ok, done.
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-03-31 17:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 12:29 UIO OF support Michal Simek
2011-03-31 12:30 ` [PATCH] uio/pdrv_genirq: Add " Michal Simek
2011-03-31 12:49 ` Wolfram Sang
2011-03-31 13:11 ` John Williams
2011-03-31 13:25 ` Arnd Bergmann
2011-03-31 13:51 ` Michal Simek
2011-03-31 16:34 ` Grant Likely
[not found] ` <AANLkTi=sG6oVNifwLLi8jjKQXjR6kXZx43NxtFfoPumy@mail.gmail.com>
2011-03-31 13:23 ` Wolfram Sang
2011-03-31 13:37 ` Michal Simek
2011-03-31 13:47 ` John Williams
2011-03-31 16:25 ` Grant Likely
2011-03-31 13:28 ` Michal Simek
2011-03-31 17:03 ` Hans J. Koch
2011-03-31 17:57 ` Michal Simek [this message]
2011-03-31 19:23 ` Hans J. Koch
2011-03-31 19:48 ` Grant Likely
2011-03-31 20:30 ` Hans J. Koch
2011-04-02 10:35 ` Wolfram Sang
2011-04-04 17:04 ` Hans J. Koch
2011-04-04 17:31 ` Wolfram Sang
2011-04-04 18:24 ` Hans J. Koch
2011-04-05 6:25 ` Michal Simek
2011-04-05 11:50 ` Hans J. Koch
2011-03-31 16:43 ` Grant Likely
2011-03-31 17:54 ` Michal Simek
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=4D94C09B.4070506@monstr.eu \
--to=monstr@monstr.eu \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=hjk@hansjkoch.de \
--cc=hjk@linutronix.de \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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