Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1377897 > unrolled thread
| Started by | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| First post | 2016-04-13 14:50 +0200 |
| Last post | 2016-04-14 15:00 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH V2 3/5] gpio: of: Return error if gpio hog configuration failed Linus Walleij <linus.walleij@linaro.org> - 2016-04-13 14:50 +0200
Re: [PATCH V2 3/5] gpio: of: Return error if gpio hog configuration failed Laxman Dewangan <ldewangan@nvidia.com> - 2016-04-13 15:10 +0200
Re: [PATCH V2 3/5] gpio: of: Return error if gpio hog configuration failed Linus Walleij <linus.walleij@linaro.org> - 2016-04-14 15:00 +0200
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Date | 2016-04-13 14:50 +0200 |
| Subject | Re: [PATCH V2 3/5] gpio: of: Return error if gpio hog configuration failed |
| Message-ID | <rnsp4-1ia-19@gated-at.bofh.it> |
On Fri, Mar 11, 2016 at 2:43 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote: > If GPIO hog configuration failed while adding OF based > gpiochip() then return the error instead of ignoring it. > > This helps of properly handling the gpio driver dependency. > > When adding the gpio hog nodes for NVIDIA's Tegra210 platforms, > the gpio_hogd() fails with EPROBE_DEFER because pinctrl is not > ready at this time and gpio_request() for Tegra GPIO driver > returns error. The error was not causing the Tegra GPIO driver > to fail as the error was getting ignored. > > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> > Cc: Benoit Parrot <bparrot@ti.com> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Reviewed-by: Thierry Reding <treding@nvidia.com> Rebased and applied this patch FWIW. This is a fair and square bug fix so need to go in no matter what happens with the hog patches. Yours, Linus Walleij
[toc] | [next] | [standalone]
| From | Laxman Dewangan <ldewangan@nvidia.com> |
|---|---|
| Date | 2016-04-13 15:10 +0200 |
| Subject | Re: [PATCH V2 3/5] gpio: of: Return error if gpio hog configuration failed |
| Message-ID | <rnsIq-1Gg-13@gated-at.bofh.it> |
| In reply to | #1377897 |
On Wednesday 13 April 2016 06:13 PM, Linus Walleij wrote: > On Fri, Mar 11, 2016 at 2:43 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote: > >> If GPIO hog configuration failed while adding OF based >> gpiochip() then return the error instead of ignoring it. >> >> This helps of properly handling the gpio driver dependency. >> >> When adding the gpio hog nodes for NVIDIA's Tegra210 platforms, >> the gpio_hogd() fails with EPROBE_DEFER because pinctrl is not >> ready at this time and gpio_request() for Tegra GPIO driver >> returns error. The error was not causing the Tegra GPIO driver >> to fail as the error was getting ignored. >> >> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> >> Cc: Benoit Parrot <bparrot@ti.com> >> Cc: Alexandre Courbot <acourbot@nvidia.com> >> Reviewed-by: Thierry Reding <treding@nvidia.com> > Rebased and applied this patch FWIW. > This is a fair and square bug fix so need to go in > no matter what happens with the hog patches. > Thank you very much for accepting the patch. I think 1/5 and 2/5 is also fine as there is no more comment on this. However, 4/5 and 5/5 needs further discussion. Please let me know if I need to send 1/5 and 2/5 here.
[toc] | [prev] | [next] | [standalone]
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Date | 2016-04-14 15:00 +0200 |
| Message-ID | <rnP2i-1K8-1@gated-at.bofh.it> |
| In reply to | #1377915 |
On Wed, Apr 13, 2016 at 2:54 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote: > On Wednesday 13 April 2016 06:13 PM, Linus Walleij wrote: > Thank you very much for accepting the patch. > I think 1/5 and 2/5 is also fine as there is no more comment on this. I have applied them now. I had a comment on 1/5, I wanted a confirmation that it was done to be able to set status = "disabled" in the device node. I assume this is true so now I added that to the commit blurb. Yours, Linus Walleij
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web